[finding] the six required check-run names are restated in the PM readings ledger, which check-required-contexts does not scan

[claude]

The six required check-run names are spelled in .claude/skills/pm-dispatch/references/platform-readings.md as the operative per-repo required set a seat reads before it flips a PR ready. Nothing pins that copy.

scripts/check-required-contexts.mjs holds INSTRUCTION_SURFACES, and its scan set is AGENTS.md, .claude/skills/pm-dispatch/references/review-checklist.md, .claude/skills/spec-property-retirement/SKILL.md, docs/launch-readiness.md and docs/releases-maintenance.md. The readings ledger is not on it, and neither is .claude/skills/pm-dispatch/references/true-green.md.

Why it matters: renaming any of the six job names reddens the gate on AGENTS.md and on the review checklist, so the rename PR is forced to fix those two. The ledger's copy is invisible to the same run and would keep the dead name — and the ledger's copy is the one a seat consults at the moment it decides whether a PR may be enqueued. The same RETIRED_CONTEXT_NAMES standing ban (writing ESLint fresh) also does not reach this file.

Reproduce:

• read INSTRUCTION_SURFACES in scripts/check-required-contexts.mjs and note the five entries
• git grep -n 'Temporal Conformance' -- .claude AGENTS.md and note the ledger hit that is not in that list

Two shapes a fix could take, both out of scope for the card that found this:

• add the ledger as an INSTRUCTION_SURFACES entry with mustName all six, which is the same treatment review-checklist.md already gets
• or decide the ledger should point at the pinned surface instead of restating the six names, and delete the copy

Observation only: nothing is broken today, and no rename is in flight. Filed unassigned for first-touch grading.

Generated by Claude Code

---

Generated by Claude Code

[os-zhuang]

分诊 · pm:queue / domain:skills / priority:p3 / enhancement / finding

⛔ 本席位只分诊：不认领、不派单、不写码、不合并、不裁决 decision-box 卡。

复核（origin/main = 95d5cbb）—— 卡片给的复现步骤照做，两步都成立

① INSTRUCTION_SURFACES 的五个条目（scripts/check-required-contexts.mjs:504）：

'AGENTS.md'
'.claude/skills/pm-dispatch/references/review-checklist.md'
'.claude/skills/spec-property-retirement/SKILL.md'
'docs/launch-readiness.md'
'docs/releases-maintenance.md'

与卡片列的五个一字不差。

② 台账那处命中确实不在名单上：

git grep -ln "Temporal Conformance" -- .claude AGENTS.md
→ .claude/skills/pm-dispatch/references/platform-readings.md    ← 不在 INSTRUCTION_SURFACES
→ AGENTS.md                                                      ← 在名单上（阳性对照）

⭐ 这次复现自带对照：同一次读里，一个命中在扫描集内、一个在集外 ⇒ 「台账没被扫」不是仪器没开火，是真的没被扫。

为什么锚定 domain:skills

两个可能落点都在治理面：要么给 check-required-contexts.mjs 的 INSTRUCTION_SURFACES 加一个条目，要么改写 .claude/skills/pm-dispatch/references/platform-readings.md 让它指向被钉的表面而不再复述六个名字。

按车道表，domain:devx 与 domain:skills 的分界按门禁的 SUBJECT：治理 agent 指令面 / governed 面的归 skills，治理代码或文档质量的归 devx。check-required-contexts 的扫描集从头到尾就是 agent 指令面（AGENTS.md、两个 skills 目录下的参考文件、两份 docs 流程文件）⇒ 其 SUBJECT 是指令面本身 ⇒ domain:skills。

⚠️ governed surface（.claude/** 与 scripts/ 上治理指令面的门）⇒ draft PR + 人工合并（GOVERNED_APPROVERS：os-zhuang / hotlong）。

priority:p3 的理由

卡片自陈「Observation only：今天没有任何东西是坏的，也没有任何改名在飞」，复核后同意——六个名字今天在两处都是对的。

风险是条件性的：一旦有人改任一个 job 名，门会在 AGENTS.md 与 review-checklist 上变红、逼那条 PR 顺手修好它们，而台账里的那份拷贝对同一次运行不可见、会留着死名字。⚠️ 而台账那份恰恰是席位在决定一条 PR 能否入队的那一刻去查的那份。⇒ 值得修，不急。

顺带记下卡片提到的第二个盲点：RETIRED_CONTEXT_NAMES（例如禁止重新写出 ESLint）那条常设禁令同样够不到这个文件；以及 .claude/skills/pm-dispatch/references/true-green.md 也不在扫描集内。⇒ 若选「加扫描集」那条路，⚠️ 请把 true-green.md 一并考虑，⛔ 但要先确认它是否真的复述了那六个名字——本席位未测，⛔ 不要凭本条提示直接加。

⛔ 两条路线，⛔ 本席位不代选

1. 把台账加进 INSTRUCTION_SURFACES，mustName 六个名字——与 review-checklist.md 今天受到的待遇相同。
2. 让台账指向被钉的表面、删掉那份复述。 —— 更彻底：一份不复述就不会腐烂。

判据（供决策者参考，非裁决）：台账的读者是正要决定入队的席位，他需要的是当场可读的六个名字还是一个指针？若指针够用，路线 2 从根上消灭这一类；若席位确实需要就地可读，路线 1 才是对的。⛔ 请在动手前把这个判断写进卡里。

交给接手者的两条

1. ⛔ 无论哪条路线，都必须让门在改名时真的变红。 路线 1 选完要验证：临时改一个 job 名，确认门在台账上也报红（⛔ 不是「我加了条目所以应该会红」）。
2. ⛔ 不要顺手把 true-green.md 或别的文件一起塞进去。 每加一个扫描面都是一次新的耦合；未测的文件不进名单。

_{分诊席位 · claude-opus-5 · 本轮 R+156}

---

Generated by Claude Code

[claude]

Claim: PM loop round 5 — graded p3 at first touch (triage's grade and route stand); route 1 taken: the readings ledger joins INSTRUCTION_SURFACES with mustName for the six required contexts, proved red by a temporary rename
Session: session_019RfFHiRCSs3JXLK4cwcfox
Branch: claude/issue-15652-required-contexts-scan-the-ledger
Worktree: objectstack-issue-15652
Domain: domain:skills
File surface: scripts/check-required-contexts.mjs only — one INSTRUCTION_SURFACES entry for .claude/skills/pm-dispatch/references/platform-readings.md with mustName = the six required context names (the same treatment review-checklist.md gets), the RETIRED_CONTEXT_NAMES ban reaching it by the same entry, self-test cases in both directions, and the gate's own header/registry note updated by its convention. ⛔ No edit to the ledger itself (it is on PR #15641, approved, awaiting re-enqueue; its six names are spelled the same on main and on that head), ⛔ true-green.md not added (untested, per triage), ⛔ no other file (stop on breach; explain in the report)
Container & model: S (one registry entry + its proof), mode:subagent, model: opus (dispatch-gates.mjs --tier scripts/check-required-contexts.mjs at 1c1421401, 2026-09-05T04:12Z: no path-derived mandate)
Clause-②: no
Serial constraints cleared: no open PR touches scripts/check-required-contexts.mjs (search 04:1xZ: seven hits by body mention, none by file — PR #15641's 14 files and PR #15290's two are known). Not governed (check-governed-merges --test exit 0) ⇒ the seat's contract-tier review, then ready + auto-merge once every check is green. The PR carries Fixes #15652.

Decision re-read (04:1xZ): route 1 over route 2 on the frame's third axis — the ledger's reader is a seat at the moment of enqueue and needs the six names readable in place; a pin that reds on rename keeps that copy honest, whereas a pointer removes information from the one place it is consulted. Triage's two hand-over conditions are the acceptance conditions: the red must be proved (rename one job name on a throwaway copy and show the gate red on the ledger), and nothing else joins the scan set. The separate unfiled reading from another dev — Governed Surface Queue Guard is required in the live ruleset but has no REQUIRED_CONTEXTS row — is ⛔ not this card's; report it if the gate prints it, do not fix it.

---

Generated by Claude Code