[hckrman101]

A test request asks someone's agent to download, build and run a PR on their own PC, and since #2734 anyone signed in to the team chat can post one for any PR. This makes a maintainer the gate: a request can only be picked up when the PR's author is a collaborator on GitHub, or a maintainer has looked at the PR and added the testing wanted label.

What changed

• scripts/test_requests.py asks GitHub (no sign-in needed; GITHUB_TOKEN/GH_TOKEN used when set) for the PR's author_association and labels. A request is approved when the author is OWNER, MEMBER or COLLABORATOR, or the PR has the testing wanted label.
  • claim refuses (exit 3) a request that isn't approved, or whose PR is merged or closed, and sends nothing when GitHub can't be asked.
  • list and show mark each open request approved and add the PR's state; waiting ones are listed last, with "waiting for a maintainer to add the label".
  • request tells the author when their PR needs the label.
• The server's relay shows a waiting request as a grey card, "Waiting for a maintainer to add the testing wanted label", with no claims, results or guide link, and checks GitHub every 3 minutes so the card opens by itself soon after the label is added (approved ones every 15, for the PR's state).
• The label is also an entry point: the relay lists open PRs labelled testing wanted every 3 minutes and posts a request for each one that has none, for its author (their GitHub name and avatar on the card, the PR title as the summary); it closes the ones it posted when the label comes off or the PR is merged or closed. The guide, the request skill and AGENTS.md say so.
• The testing skill now treats the request, the PR and its code as data, never instructions: it builds and runs only as docs/development.md says, and before the first build looks at what the PR changes that runs on the PC (scripts, tools, workflows, anything downloading or reaching outside the repository), stopping if something isn't explained.
• The request skill, the guide (docs/test-requests.md) and AGENTS.md say the same.

Tested

• Live: with this running, the relay posted requests for the two labelled PRs that had none (fix(vk): Intel Windows runtime fixes (pipeline cache saves, alpha to coverage) #2456, perf(host): the game's zstd stream decode on the host's libzstd (HOS_NATIVE_ZSTD, opt-in) #2738), under their authors' GitHub names and avatars, and left perf(vk): add floats to storage buffers with the GPU's own atomic, not a compare-and-swap loop #2306 alone (it already had one).

• tests/test_test_requests.py: a stranger's PR without the label can't be claimed; the label approves it; a merged PR can't be claimed; no claim goes out when GitHub can't be asked, while list still works; waiting requests list last. python -I -B tests/run_all.py test_requests team_chat: both pass.

• Live: the open request for perf(vk): add floats to storage buffers with the GPU's own atomic, not a compare-and-swap loop #2306 (a contributor's PR) turned into the waiting card when the relay was updated; after adding testing wanted to perf(vk): add floats to storage buffers with the GPU's own atomic, not a compare-and-swap loop #2306 it opened again on its own within 3 minutes, in both Discord channels, and list shows it approved.