pm-dispatch: a Tier H PR opened outside the relay gets no review request and no run row to check; state the per-author request rule and make the seat read requested_reviewers before the handoff #25782

Filing gate ③: a maintainer-direct task; the maintainer's words are quoted verbatim below. Filed by repo:cloud#2 (session session_0123kRqqdpAJWYMgsgdAJX4G, account os-zhuang) through the project coordinator's relay. ⛔ Not a claim. Suggested grade: S, p2. Triage may regrade.

Reader (who acts): the domain:skills seat. One PR on .claude/skills/pm-dispatch/** (Tier S in objectstack), with its contract review at CONTRACT_REVIEW_TIER.

Dedup: search_issues on objectstack, "governed review request PR opened outside fleet-write relay requested_reviewers author approver pm-dispatch": 62 hits. The closest are #25457 (relay-only PR writes; closed), #25046 (a Tier H PR never reaches os-zhuang; closed) and #25199 (objectui .claude/** tier; closed). None covers a Tier H PR that is already open, was opened outside the relay, and has no review request.

The maintainer's words (2026-10-25, Claude Code project "cloud", verbatim)

等我手工合并的，为什么没有按照 pm-dispatch 技能请求审核

我说的需要更新 github 上的项目吗

这个还识别账户的吗？hotlong 开发的会自动请审吗？

What was measured (cloud, 2026-10-25)

• cloud#3255 and cloud#3256 are Tier H PRs (.github/workflows/** and AGENTS.md). Their card threads opened them directly as os-zhuang, not through the relay's pr_create.
  • The relay never saw them, so no request went to GOVERNED_APPROVERS, and no governed review: run row existed for the seat to check (SKILL.md: 「席位只核对 run 摘要 governed review 行,缺口才手补」).
  • Both sat as drafts with requested_reviewers: [] until the seat filled the gap by hand with pr_request_reviewers.
• cloud#3268, opened through the relay's pr_create, got hotlong and os-zhuang requested automatically.
• The relay already distinguishes accounts: governedReviewPlan (scripts/pm/fleet-write/execute.mjs:430) requests every approver who is missing, except the PR author, whom it assigns instead. But that only runs on pr_create / pr_ready sent through the relay. A Tier H PR stays a draft and is never readied by the seat, so a PR opened outside the relay never gets the follow-up.
• The upstream cause on cloud was that the seat's dispatch orders lacked the Writes: line execution-duties.md:129 requires ("PR 只经中继 pr_create"). That is a seat miss, recorded on the cloud side. This card is about the backstop, which the skill text does not spell out.

What to change (text only)

1. SKILL.md, near :198–200. Before the speed-read handoff, the seat reads the PR's requested_reviewers and assignees itself; it does not rely only on the run row. A PR whose user.login is not objectstack-fleet[bot] has no run row by construction. The seat fills any gap with the relay op pr_request_reviewers, and names the off-relay author in the ACCEPT (contract-review.md:29 already says this for contract reviews; extend it to every Tier H handoff).
2. State the per-author rule as a table. It is what governedReviewPlan already does:

3. The speed-read's 「你要做的」 names the approver who can approve. For an approver-authored PR, that is the other approver, so the maintainer is never asked to approve their own PR.

Acceptance

• The two sentences and the table are in SKILL.md (or the reference it points at). The table is derived from governedReviewPlan, with no rule the code does not perform.
• Contract review PASS at CONTRACT_REVIEW_TIER. The skill's own checks are green.

Generated by Claude Code