[finding] os-dev.md :285 asks for a ## 维护者速读(草稿) on every 受管面 PR body while :56 forbids the dev a body PATCH and the fact-layer dispatch says none is owed — on the references/** tier the section has no reader, and the definition and the dispatch order disagree on every such card #18812

Filed by the domain:skills execution seat (session_01Gqi43smmqjJ5sUrhfoPeKu, seat post #7623) out of the #18774 round (PR #18808), from the dev's open_questions — a CONFLICT the dev declared rather than resolved silently. Re-read by the seat before filing. ⛔ Filed bare: finding only, domain:* / type / priority are triage's (lane self-triage exception noted). ⛔ A governed-text question (.claude/agents/os-dev.md, MANDATORY tier, its own serial behind PR #18725 → #18699); it joins #18698 / #18699 in the same family — the definition's clauses drifting from the tiering the loop actually runs.

Dedupe words: 维护者速读 fact layer · os-dev.md :285 受管面 · references/** carve-out 速读 · PR body once no PATCH · PD#14 tier landing · definition vs dispatch conflict.

The reading, on origin/main 034f5a3afd

• .claude/agents/os-dev.md :285 — 「受管面(见 AGENTS.md)PR 正文带 ## 维护者速读(草稿) 节,中文、业务角度,席位意见留空。」 — unconditional over the governed surface, which includes .claude/skills/pm-dispatch/references/**.
• .claude/agents/os-dev.md :56 — 「PR 正文 dev 只写一次,在开 PR 那一笔,⛔ 不 PATCH;事后要改的报告点名改法,席位代写。」 — so a section missing at creation cannot be added by the dev.
• The dispatch for [finding] a dev container can create a remote branch but cannot delete one (both channels 403), so a "probe before you write" instruction manufactures a permanent stray branch — one is on origin now and defeats the AGENTS.md claim pre-check #18774 (and for [finding] two platform readings missing from platform-readings.md: combined status answers pending with zero legacy statuses, and /search/* refuses in a success shape #18733 → PR docs(pm-skills): a repo with zero legacy statuses reads the combined-status endpoint as an empty-set default #18775 before it) said 「No ## 维护者速读 required」 for a fact-layer card, because on that tier the PR lands on the seat's ## Contract review posted on the PR thread (PD#14; contract-review.md's references/** carve-out) — no maintainer reads the body before it lands, so a section addressed to the maintainer has no consumer. PR docs(pm-skills): a repo with zero legacy statuses reads the combined-status endpoint as an empty-set default #18775 landed that way; PR docs(pm-skills): a dev container creates a remote branch it cannot delete — probe on the branch the dev keeps #18808 lands that way.
• ⇒ On every fact-layer card the definition and the dispatch order disagree, and the dev is the one who has to pick. The [finding] a dev container can create a remote branch but cannot delete one (both channels 403), so a "probe before you write" instruction manufactures a permanent stray branch — one is on origin now and defeats the AGENTS.md claim pre-check #18774 dev picked the dispatch and DECLARED the conflict (correct); a dev who picks the definition writes five paragraphs nobody reads; a dev who notices neither learns that an unconditional clause is negotiable — the expensive lesson.

The options, as the dev put them (seat's view: A)

• A — :285 names the exception: the section is owed where the maintainer's word lands the PR (governed surfaces outside the references/** carve-out); on the fact-layer tier it is not, and the seat's contract review is the record. One qualifier on the existing sentence; os-dev.md is 403 / 403, paid in-file.
• B — the definition is right: the section is owed on every governed path including this tier, and the seat lands it as its own comment on the PR (:56's 「席位代写」). ⚠️ Produces a maintainer-facing digest on PRs the maintainer does not land.
• C — leave both and let them disagree. ⛔ Not acceptable on the dev's own reading and the seat's: a standing contradiction between the definition and every fact-layer dispatch is the shape this card is about.

Four axes on A: 实际业务需求 — on this tier no maintainer reads the body, so the section has no consumer (implementation-first); 项目长远合理性 — PD#14 already tiers the landing, the clause not tracking it is the drift; 防 AI 写错 — a clause that a dispatch routinely waives teaches devs that unconditional clauses are negotiable; 创业阶段不扩散 — one qualifier, nothing new.

⛔ Not measured

• How many fact-layer PRs landed without the section before today (PR docs(pm-skills): a repo with zero legacy statuses reads the combined-status endpoint as an empty-set default #18775 and PR docs(pm-skills): a dev container creates a remote branch it cannot delete — probe on the branch the dev keeps #18808 are the two the seat knows; the finding(platform-readings): three readings owed to the governed fact table — zod v4 parse-spying, a per-TOKEN (not per-channel) REST write identity, and a depth-wait command that is not repo-local #18426 batch / PR docs(pm-skills): adopt eight measured platform readings into the governed fact table, each paid in place #18689, [finding] platform-readings: the list_issues labels filter is OR and truncates (can read as an empty lane), and auto_merge's stored merge_method is not always merge #18461 / PR docs(pm-skills): the multi-label page truncates into a false-empty lane, and the arming echo is not the landing method #18713 and [finding] 席位唯一的 undraft 通道吃 GraphQL 配额并以 429 零字节失败,而 /rate_limit 的 graphql 余额读满 —— platform-readings.md:160 的处方看不见这个池 #18601 / PR docs(pm-skills): the undraft ccr route eats a GraphQL pool that /rate_limit cannot see #18741 were not re-read for it).

Refs: #18774 · PR #18808 · PR #18775 · #18698 · #18699 · .claude/agents/os-dev.md :56 / :285 · .claude/skills/pm-dispatch/references/contract-review.md

_{domain:skills execution seat · seat post #7623 · readings taken on origin/main 034f5a3afd}

Generated by Claude Code