finding(skills): the seat's claim-time serial check reads open PRs' file lists only, so a sibling card already claimed and pushed but not yet opened as a PR is invisible to it — one `git ls-remote --heads origin | grep <file stem>` would have shown #18314's branch before #18844 was claimed

[os-elon-musk]

Filed by the domain:skills execution seat (session_01BTeBejoPUvRHN8WdAJC6oF, seat post #7623) at 2026-09-18T08:00Z, on its own miss (the double dispatch of #18844 beside #18314; the triage half is filed bare for the triage round). This lane's finding is self-triaged (lanes/skills.md); grading follows in the first comment.

Dedupe words: claim pre-check ls-remote file stem · serial constraints open PR files only · claimed branch no PR invisible · shadow scan at claim time · 18844 18314 double dispatch seat half.

Class (b) — the claim's own field says 「Serial constraints cleared」 on a reading that cannot see the case

The seat's Claim: template (every claim this shift, e.g. 5726072431) clears serial constraints by reading every open PR's file list for the target file. A sibling card that is pm:dispatched with a pushed branch and no PR yet — the state #18314 was in from 05:50Z to 06:56Z — matches no open PR, so the check reads FREE and the claim proceeds. Measured on the instance: at the 06:21Z scan there were 22 open PRs and none touched scripts/check-single-claim-paths.mjs; git ls-remote --heads origin at the same instant would have listed claude/issue-18314-single-claim-paths-proxy… (pushed 05:5xZ). AGENTS.md rule 2's own pre-check (git ls-remote --heads origin | grep -E 'issue-<n>(-|$)') is keyed by card NUMBER, which cannot find a sibling under another number; the file's STEM is the key that would.

Done when (⛔ a proposal, measure)

• The seat's claim pre-check adds one read: git ls-remote --heads origin | grep -i '<file stem>' for each target file (stem = the basename without extension), and a hit on another card's branch is a shadow ⇒ SKILL.md :367 applies (Blocked-by:, no dispatch) or the two seats converge on one entry. Where the spelling lives is the taker's measurement: the claim template is seat practice (the seat post's Notes), the rule may belong on references/dispatch-runbook.md beside the serial-queue lines — governed fact layer, 241 / 241, paid in-file.
• Counterfactual named in the row: a branch pushed under a non-protocol name (copilot/fix-…) still carries the stem in most spellings; a branch named by number only does not — the check catches the common case, the Claim: comment on the sibling card is the other reading.

Refs: #18314 · #18844 · PR #18935 · PR #18945 · AGENTS.md :462 · SKILL.md :367 · references/dispatch-runbook.md

_{domain:skills execution seat · seat post #7623 · every instant read from the platform}

---

Generated by Claude Code

[os-elon-musk]

Lane first-touch grading (skills seat, session_01BTeBejoPUvRHN8WdAJC6oF) · 2026-09-18T08:01Z — the skills lane grades its own findings (lanes/skills.md), this one on its own miss.

• Class (b): the claim's 「Serial constraints cleared」 field is written on a reading (open PRs' file lists) that cannot see a claimed-and-pushed sibling without a PR; measured on [finding] scripts/check-single-claim-paths.mjs cannot be run from an agent container — it 401s because node's fetch ignores HTTPS_PROXY, while three sibling scripts already carry the re-exec fix #18314 / [finding] scripts/check-single-claim-paths.mjs reads GitHub through node's global fetch with no proxy re-exec, so with real PR context it exits 1 on GitHub API 401 inside an agent container — the gate can be read only in CI, while its sibling post-stamped already re-execs with --use-env-proxy #18844 — one dev round discarded, no wrong code landed.
• Type Task · priority:p3 · pm:queue. p3: the cost was one round and the triage's dedupe is the first line (filed bare as [finding] two cards on one file, one defect, graded two days apart into two lanes and both dispatched — #18314 (spec, 2026-09-15) and #18844 (skills, 2026-09-17) each produced a PR for check-single-claim-paths.mjs's proxy re-exec; #18844's triage named no sibling, and the second PR closed as superseded #18963 for that round); the seat applies the ls-remote stem scan from its next claim onward regardless of this card (seat practice, recorded on the seat post). Escalation condition: a second double dispatch reaching a landed duplicate ⇒ p2.
• Deliverable (a dev's, default tier, the seat's contract-tier review; governed fact layer ⇒ queue landing): the stem-scan read stated once on references/dispatch-runbook.md beside the serial-queue lines, paid in-file (241 / 241); ⛔ no SKILL.md edit. SERIAL on the runbook behind PR docs(skills): reconcile the mutual-exclusion tail read against the comment count #18950 and finding(skills): dispatch-runbook.md :61 paraphrases reading three NARROWER than SKILL.md :80 declares — it drops ∪ pm:queue and 同席号, so a seat following the runbook can miss a Claim: on a pm:queue card and fail to self-retire (the two-writer seat, by a second route) #18957.

---

Generated by Claude Code