Revise Test Team Rep duties and qualifications

[Successfulsebunya]

Updated Test Team Rep duties and qualifications for clarity and consistency.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Successfulsebunya <mosescursor@git.wordpress.org>
Co-authored-by: nikunj8866 <nikunj8866@git.wordpress.org>
Co-authored-by: ironprogrammer <ironprogrammer@git.wordpress.org>
Co-authored-by: SirLouen <sirlouen@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates the Test Team Rep duty list to reflect current cadence, activities, and guidance links.

Changes:

• Adjusts content cadence (bi-weekly updates, monthly recap) and replaces/updates links to examples.
• Updates session responsibilities (Patch Testing naming, adds Voice Chat cadence).
• Clarifies shared responsibility language for the two reps.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[ironprogrammer]

Don't need to use Copilot's wording here, but I do agree that maintaining links to these guide pages is helpful.

[ironprogrammer]

If the header used at the start of each session in Slack has changed, then use whatever the current convention is. It does look inconsistent.

[nikunj8866]

LGTM!

[ironprogrammer]

Thanks for these updates, @Successfulsebunya! I've left a little feedback below. Feel free to accept or discard, whatever the current temperature is in team rep world.

[ironprogrammer]

Don't need to use Copilot's wording here, but I do agree that maintaining links to these guide pages is helpful.

[ironprogrammer]

If the header used at the start of each session in Slack has changed, then use whatever the current convention is. It does look inconsistent.

[ironprogrammer]

Suggested change

	- Run Voice Chat sessions in [#core-test](https://wordpress.slack.com/archives/C03B0H5J0) every **1st Thursday of the month**.
	- Run Voice Chat sessions in [#core-test](https://wordpress.slack.com/archives/C03B0H5J0) on the first Thursday of every month.

Just a nitpick. Use of strong text here isn't consistent with other guide conventions.

[ironprogrammer]

Suggested change

	These duties are shared between the two Reps (see **Rep Responsibilities** on [the Team Rep page](https://make.wordpress.org/updates/team-reps/#team-rep-orientation)).
	These duties are shared between all team Reps (see **Rep Responsibilities** on [the Team Rep page](https://make.wordpress.org/updates/team-reps/#team-rep-orientation)).

There wasn't always two reps, and afaik there isn't anything requiring exactly two, so this small change should accommodate future team shapes ("all" is optional).

[SirLouen]

Great protocol @Successfulsebunya