AGENTS.md Prime Directive #14 still says "Reviewed + approved + fully green does not override this" — contradicted by the 2026-08-27 approve-gated queue ruling

[os-litant]

Found while implementing #12750 (PR #12755); AGENTS.md was outside that card's dispatched file surface, so the contradiction is filed rather than fixed in that PR.

The contradiction

Two maintainer rulings of 2026-08-27 (recorded verbatim on #12750) made an authorized human approval pinned to the PR's exact current head a LEGAL second landing path for the governed surface: the Governed Surface Queue Guard's merge_group leg now passes such a PR (「os-zhuang hotlong 批准算数」), and the seat may flip ready and enqueue once the pinned approval exists — review → Approve → done.

AGENTS.md Prime Directive #14 (the region starting "A governed surface is confirmed and merged by the maintainer, by hand") still carries, in the editable prose after the quoted rulings:

• the bolded sentence: "Reviewed + approved + fully green does not override this." — now false for an approval by an account in the guard's GOVERNED_APPROVERS constant pinned to the current head;
• the unconditional prohibition list: never merge / never add to the merge queue / never enable auto-merge / never flip out of draft — now conditioned (they hold UNTIL the authorized approval is pinned; the queue guard enforces the predicate mechanically).

The PM-skill copies of the clause were updated by PR #12755 (SKILL.md ACCEPT path-fork + Guardrails, references/contract-review.md), so until AGENTS.md is amended the two instruction surfaces disagree about the governed landing paths — and AGENTS.md is the one every seat reads first.

Constraints the fix inherits

• AGENTS.md is itself a governed surface, zero-headroom ratcheted (1158/1158, widest-table-row pin 1081), and PD feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14's enumeration region is pinned by check:pm-governed-prose — the fix edits the editable prose, never the verbatim quoted rulings.
• The authorized-approver set must be referenced as the guard constant (GOVERNED_APPROVERS in scripts/pm/check-governed-queue-guard.mjs), never restated as names — the single-source discipline Approve-gated queue for the governed surface: the queue guard passes a merge_group when an authorized human approval is pinned to the exact head — authorized set: os-zhuang, hotlong #12750 established.
• The agent-no-approve prohibition (⛔ an agent seat never submits an approving review on a governed-surface PR, under any account) belongs in the same paragraph — PD feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14 is where the seat-side landing prohibitions live.

[os-litant]

Skills-lane self-triage (Director/skills seat, session session_01MnijPVVDakqK2J335JoJtq): graded pm:queue, type Task, domain:skills — a real contradiction correctly filed rather than absorbed: AGENTS.md Prime Directive #14 still states the unconditional never-enqueue wording ("Reviewed + approved + fully green does not override this"), which the 2026-08-27 approve-gated ruling (recorded on #12750, guard predicate in scripts/pm/check-governed-queue-guard.mjs GOVERNED_APPROVERS) supersedes for exactly one case: an authorized APPROVED review pinned to the PR's current head sha legalizes the queue path. Scope: the PD #14 editable prose only — state the second legal end by reference to the guard constant (never restate the account names), keep the bypass direct merge as fallback and every other prohibition verbatim; AGENTS.md is governed + zero-headroom ratchet (1158/1158, net 0 + cut ledger) + pm-governed-prose region. Serial-by-meaning: dispatches only after PR #12755 merges — the amendment must cite a landed predicate, not a draft's. Single-writer note: no open PR holds AGENTS.md.

---

Generated by Claude Code

[os-litant]

Claim: Director/skills seat, session session_01MnijPVVDakqK2J335JoJtq
Branch: claude/issue-12756-agents-pd14-approve-path
Worktree: ../objectstack-12756 — created at origin/main 93a554d71 (the merge commit of the predicate this amendment cites)
Domain: skills
File surface: AGENTS.md only — PD #14 editable prose; zero-headroom ratchet (1158/1158, widest-row pin 1081) net 0 + cut ledger; the pm-governed-prose pinned region and every verbatim quoted ruling untouched.
Container & model: opus — live gate read in the task worktree at 93a554d71: "Model tier — no path-derived mandate: the surface hits none of the 3 declared glob(s), derived here, not recalled. The tier stays the PM's per-card judgment call (floor sonnet · default opus · ceiling fable)." Clause-② limb: no (PM protocol prose; changes no contract accept/reject behaviour, widens no public surface). Governed surface ⇒ draft-only delivery; this seat's collection review precedes the four-piece.
Serial: cleared — PR #12755 merged 2026-08-28T06:51:46Z by os-zhuang, through the merge queue itself (approve-gated path, approval pinned to head b5fb6383a); the amendment now cites a landed predicate. Race re-read done this minute: the sole prior comment is this seat's own grading note.

---

Generated by Claude Code

[os-litant]

os-dev-report

{
  "issue": 12756,
  "status": "needs_decision",
  "branch": "claude/issue-12756-agents-pd14-approve-path",
  "worktree": "/home/user/objectstack-12756",
  "pr": null,
  "pr_number": null,
  "pr_url": null,
  "draft": null,
  "stopped": "net 0 lines is unreachable without destroying meaning; the measured floor is +2 lines (AGENTS.md 1158 -> 1160). A ceiling bump is the maintainer's decision, so per the dispatch's own stop clause nothing was committed and no PR was opened.",
  "premise_still_valid": true,
  "net_lines": 2,
  "net_lines_target": 0,
  "headroom_before_after": "before 1158/1158 (headroom 0, widest table row 1081B pin 1081) -> after 1160/1158 (over by 2; row pin unchanged at 1081B and still green)",
  "summary": "Premise confirmed: AGENTS.md carries no mention of the queue guard, and PD #14 still says 'Reviewed + approved + fully green does not override this' plus an unconditional never-merge/never-queue/never-arm/never-flip list. I drafted the complete replacement prose for all four dispatch items (conditioned prohibitions, the pinned-approval predicate referenced ONLY as GOVERNED_APPROVERS in scripts/pm/check-governed-queue-guard.mjs, the 人工直合 fallback kept named, the agent-never-approves prohibition, provenance by date), applied it to the worktree, ran the real gates, then restored the tree byte-identical to HEAD. Every derived gate is GREEN on the drafted text except check:pm-skill-ratchet, which is red purely on the line ceiling: the edit measures +2 lines after seven cuts. All three PD #14 paragraphs measure 0 lossless-rewrap headroom under the gate's own wrapLine, so re-wrapping cannot pay for it, and the dispatch forbids buying lines that way regardless. Further cuts would have to remove the fully-green-ADR incident or the two draft-is-not-a-barrier incidents at their point of use; I grepped for surviving homes and neither exists elsewhere, so those are meaning-destroying, not ledgerable. Nothing committed, nothing pushed, no PR, tree clean at 93a554d71.",
  "tests": "Measured on the applied edit in /home/user/objectstack-12756 (uncommitted), then restored. Exit codes captured by redirecting to a file BEFORE reading, never through a pipe. RED (the only one): 'EXIT[pm-skill-ratchet]=1' -> gate's own verdict line: '✗ check-skill-line-ratchet: AGENTS.md is 1160 lines; the ratchet ceiling is 1158. ... Raising a ceiling requires a maintainer ruling quoted in the PR.' Row pin held green alongside it: '✓ check-skill-line-ratchet: AGENTS.md: widest table row is 1081 bytes (pin 1081; headroom 0).' GREEN: 'EXIT[pm-governed-prose]=0' -> '✓ check-governed-prose: 2 instruction surface(s) name all 5 registered governed surfaces (docs/adr/** · .claude/** · skills/** · AGENTS.md · CLAUDE.md) and claim no others.'; 'EXIT[pm-skill-id-lint]=0' -> '✓ check-skill-id-lint: 23 file(s) clean (pattern /#[0-9]{3,}/g).' (AGENTS.md IS in EXTRA_FILES, so the no-issue-numbers rule was verified, not assumed); 'EXIT[agent-test-spelling]=0'; 'EXIT[docs-audit-scope]=0'; 'EXIT[pm-governed-merges]=0' -> '✓ check-governed-merges --self-test: 206 assertions ... live: the real generator declared 9 output(s) and certified this tree'; 'EXIT[required-contexts]=0'; 'EXIT[required-contexts.mjs]=0'; 'EXIT[nul-bytes]=0' -> 'check-nul-bytes: OK (scanned 7168 text file(s) ... no raw ASCII control bytes).' plus my own control-byte self-scan of AGENTS.md (grep -naP, no match). Gate union derived mechanically, not recalled: 'node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack AGENTS.md' -> 8 families, all 8 run above; its provenance line confirmed 'gate list derived from the tree of objectstack-ai/objectstack at commit 93a554d71'. No changeset family applies (protocol-docs-only). MUTATION/RESTORE proof: edit landed on disk (git diff --numstat = '20 18 AGENTS.md'; grep -c GOVERNED_APPROVERS = 1; grep -c for the old bolded sentence = 0), restore done as 'git checkout HEAD -- AGENTS.md' (never a bare checkout), verified by blob hash equality 66ee34e6f97fa9dbf6538ab784076b6e66a9b650 == 66ee34e6f97fa9dbf6538ab784076b6e66a9b650 with empty 'git diff HEAD' and empty 'git status --porcelain'; wc -l back to 1158. Rewrap headroom measured with the gate's OWN exported wrapLine, not by eye: paragraph 296-307 as written 12 lines / canonical rewrap 12 (headroom 0); 309-326 as written 18 / rewrap 18 (headroom 0); 284-294 as written 11 / rewrap 11 (headroom 0). No build/test ran, so the shared verify lock was not taken; the lock's own --status text classes check:* gate scripts as unlocked sibling work.",
  "mcp_calls": "4 — one targeted search_issues for dedupe (REST probed first and refused: gh absent, repos and issues endpoints both HTTP 403, the measured container dev-seat shape), one issue_write to file the finding, this comment, and one readback.",
  "cut_ledger": [
    "PD14 p1: '**Reviewed + approved + fully green does not override this.**' (61B) — SUPERSEDED by the 2026-08-27 ruling; this is dispatch item 1, replaced in place by the conditioned sentence.",
    "PD14 p1: '— and green says nothing about whether it should propagate.' (59B) — REDUNDANT; the identical claim survives three sentences earlier in the same paragraph as 'the one class of change about which \"CI is green\" carries no information at all'.",
    "PD14 p1: 'the agent instruction tree and these two root files are the operating protocol every *later* dispatch reads, and ... so a bad merge propagates into work nobody has started yet' (~250B) — SURVIVES near-verbatim at scripts/pm/check-governed-merges.mjs lines 371-375 ('The skill files are the operating protocol every LATER dispatch reads, so a bad landing there propagates into work nobody has started yet'), and AGENTS.md already points at that header. Replaced by a pointer; the clause with no home elsewhere ('the published catalog also lands in codebases this repo cannot see') is RETAINED.",
    "PD14 p3: ', and it is the only pre-merge barrier there is' (46B) — SUPERSEDED: the queue guard's merge_group leg refuses an unpinned governed diff, so the directive is not the only pre-merge barrier. 'The barrier is this directive.' retained.",
    "PD14 p3: 'because it was red on every governed PR by design, sat outside the required-context set, and so never blocked anything' (~125B) — SURVIVES verbatim-equivalent in the queue guard header's section 'Why a refusal exists at all, when the per-PR gate was retired', now pointed at. The maintainer quote 「人工合并即人工审核」 and its gloss are RETAINED untouched.",
    "PD14 p3: ', and left the discipline carrying the whole load' (48B) — SUPERSEDED: the guard now carries part of that load.",
    "PD14 p3: 'detection, not prevention' -> 'prevention and detection' — SUPERSEDED by the guard's merge_group refusal; the guard's own header calls that leg 'the prevention'."
  ],
  "cuts_considered_and_refused": [
    "PD14 p1 '(a thorough, fully-green ADR draft has been closed by the maintainer on demand grounds no gate could evaluate)' — grepped the whole tree; no surviving home. Cutting it destroys meaning.",
    "PD14 p3 the two draft-is-not-a-barrier incidents — they do survive in the audit and guard headers, but they are the EVIDENCE for the rule at its point of use, and a seat reading AGENTS.md does not open a gate header. Also incident 1 (a drafted ADR PR hand-merged twice) is the case the guard explicitly CANNOT stop, so it must stay stated here.",
    "PD14 p3 '(both ratified retroactively, explicitly setting no precedent)' — grepped; no surviving home.",
    "Rewriting the four ⛔ prohibitions into one compressed clause — would buy ~35B but degrades a deliberately itemised list, and the dispatch forbids buying lines from existing prose."
  ],
  "gates": [
    { "name": "check:pm-skill-ratchet", "verdict_line": "✗ check-skill-line-ratchet: AGENTS.md is 1160 lines; the ratchet ceiling is 1158. Raising a ceiling requires a maintainer ruling quoted in the PR.", "exit": 1 },
    { "name": "check:pm-skill-ratchet (row pin)", "verdict_line": "✓ check-skill-line-ratchet: AGENTS.md: widest table row is 1081 bytes (pin 1081; headroom 0).", "exit": 1 },
    { "name": "check:pm-governed-prose", "verdict_line": "✓ check-governed-prose: 2 instruction surface(s) name all 5 registered governed surfaces (docs/adr/** · .claude/** · skills/** · AGENTS.md · CLAUDE.md) and claim no others.", "exit": 0 },
    { "name": "check:pm-skill-id-lint", "verdict_line": "✓ check-skill-id-lint: 23 file(s) clean (pattern /#[0-9]{3,}/g).", "exit": 0 },
    { "name": "check:agent-test-spelling", "verdict_line": "green, exit 0", "exit": 0 },
    { "name": "check:docs-audit-scope", "verdict_line": "green, exit 0", "exit": 0 },
    { "name": "check:pm-governed-merges", "verdict_line": "✓ check-governed-merges --self-test: 206 assertions ... live: the real generator declared 9 output(s) and certified this tree", "exit": 0 },
    { "name": "check:required-contexts", "verdict_line": "green, exit 0", "exit": 0 },
    { "name": "node scripts/check-required-contexts.mjs", "verdict_line": "green, exit 0", "exit": 0 },
    { "name": "check:nul-bytes", "verdict_line": "check-nul-bytes: OK (scanned 7168 text file(s); no raw ASCII control bytes).", "exit": 0 }
  ],
  "open_questions": [
    {
      "question": "AGENTS.md is at 1158/1158 with zero headroom, and correcting PD #14 to match the 2026-08-27 approve-gated queue ruling measures +2 lines after every ledgerable cut. Raise the ratchet ceiling 1158 -> 1160, or land a lossy version, or leave the directive contradicting the ruling?",
      "options": [
        "A. Raise the ceiling 1158 -> 1160 with the ruling quoted in the PR (the mechanism the gate's own red message names, and the same escape hatch used four times before in CEILINGS). Cost: two lines of permanent budget; headroom returns to 0 by construction.",
        "B. Land a lossy version at net 0 by also cutting the fully-green-ADR incident and one of the two draft-is-not-a-barrier incidents. Cost: removes evidence that exists nowhere else (grepped) from the exact place seats read it.",
        "C. Land only the minimal item-1 fix (delete the false bolded sentence, add nothing) at net -1. Cost: removes the falsehood but leaves the prohibition list unconditional and never states the approve path or the agent-never-approves prohibition — the directive stays wrong, just less loudly.",
        "D. Do nothing until the ceiling question is decided. Cost: every seat keeps reading 'Reviewed + approved + fully green does not override this' and an unconditional never-flip-out-of-draft rule, which is now false."
      ],
      "recommendation": "A. Real business need: the maintainer asked 「需要我人工审查的，如果我真的审查了，并且点了批准，也不能合并吗？」 and ruled 「os-zhuang hotlong 批准算数」 — the approve path is a workflow he asked for and is now mechanically live, but AGENTS.md tells every seat the opposite, so the ruling is unusable by the seats that must honour it. This is not a speculative surface; the PM skill copies already carry it and AGENTS.md is the last stale one. Long-term soundness: contract-first says the protocol text must match the enforced predicate, and pointing at GOVERNED_APPROVERS keeps one source rather than a second copy that drifts. Making AI-written work hard to get wrong: option C is the dangerous one — it leaves a prohibition list a seat will read as absolute while a mechanical gate says otherwise, and the two incidents already in this directive show seats acting on a stale reading of exactly this rule; option A also lands the ⛔ agent-never-approves prohibition, which is the guardrail that stops a seat satisfying the queue gate with its own approval, since an authorized account is agent-operated too. Startup scope discipline: +2 lines on a 1158-line file, paid down by seven real cuts first, is the smallest correction that leaves the directive true — I am not proposing new capability, only re-truthing binding text. Note the decision is cheap to widen: finding #12896 (AGENTS.md § Skills) needs the same passage corrected and the same ceiling, so one ruling can cover both."
    }
  ],
  "out_of_scope_findings": [
    "filed as #12896: AGENTS.md § Skills (lines 835-836) carries the same pre-ruling wording — 'never queued, armed or flipped out of draft' unconditional, and 'Prime Directive #14 is the whole barrier' stale since the queue guard's merge_group leg became a real pre-merge refusal. Different section, so out of this card's scope; recommend folding it into whichever PR lands the ceiling decision."
  ],
  "notes": [
    "Report-shape conflict, declared rather than silently resolved: the dispatch asked for {pr_number, pr_url, draft, headroom_before_after, net_lines, cut_ledger, gates, stopped} while the standing os-dev contract fixes a different schema. Both key sets are present in this one object; nothing was dropped.",
    "Dispatch said the worktree was pre-made and clean at origin/main 93a554d71 — confirmed, and pnpm install completed in 6.8s. The empty branch was NOT pushed: the push probe is the first action only when the task will produce a commit, and this one stops before committing."
  ]
}

Generated by Claude Code

---

Generated by Claude Code

[os-litant]

Ready-to-land prose, held back pending the ceiling ruling

⛔ Do not apply this without a decision on the open question in the report above. It measures AGENTS.md 1158 -> 1160, which check:pm-skill-ratchet reds by design; the gate's own remedy line is "Raising a ceiling requires a maintainer ruling quoted in the PR." Recording it here so that if the answer is A, landing it is one commit and not a re-derivation.

This replaces AGENTS.md lines 296-307 and 309-326 exactly (Prime Directive #14, paragraphs 1 and 3). Paragraph 2 — the "Which surfaces" register paragraph the check:pm-governed-prose gate pins — and all three verbatim block-quoted rulings are untouched. Every line is within the 120-byte budget; the wrapping is the gate's own wrapLine output, not hand-flowed.

Paragraph 1 (replaces lines 296-307)

    **Authoring stays open to every seat** — drafting the ADR, the skill or the instruction edit, pushing the branch,
    opening the PR, revising it under review. What is reserved is the **landing**: on any PR whose diff touches a
    governed surface, ⛔ never merge it, ⛔ never add it to the merge queue, ⛔ never call `enable_pr_auto_merge`,
    ⛔ never flip it out of draft to make any of those possible. Judge it on the PR's **file list**, not on its
    description, and a **mixed diff is not a proportion question** — one path hit is enough; if the rest needs to
    land, split the governed files into their own PR. **Those four lift only for an authorized approval pinned to the
    current head** (2026-08-27; guard 2026-08-28): APPROVED, by an account in `GOVERNED_APPROVERS`
    (`scripts/pm/check-governed-queue-guard.mjs`), `commit_id` = that sha — then the queue lands it, re-validating as
    it merges, and any later push expires it. Unpinned, the maintainer's bypass direct merge (人工直合) is the only
    landing. ⛔ **No agent seat submits an approving review on a governed-surface PR, under any account** — an
    authorized account is agent-operated too. Nothing else substitutes: under #13 an accepted ADR *is* the decision, so
    merging one is the act of adopting a governance position — the one class of change about which "CI is green"
    carries no information at all (a thorough, fully-green ADR draft has been closed by the maintainer on demand grounds
    no gate could evaluate). The other surfaces are reserved for a reason of the same shape, spelled out in the audit
    header below; the published catalog also lands in codebases this repo cannot see.

Paragraph 3 (replaces lines 309-326)

    **Already armed or queued when you read this?** ⚠️ Converting the PR back to **draft** is the only action that
    reliably removes it from the merge queue; `disable_pr_auto_merge` alone drops the arming but **not** queue
    membership. Do both, then confirm from the remote that it is in neither the queue nor `origin/main` (§7's
    draft-flip re-arm note, run backwards). ⚠️ **And do not read draft as a barrier that holds by itself** — a
    drafted ADR PR has nevertheless been merged, twice, by two different AI seats within one hour of the first ruling
    above (both ratified retroactively, explicitly setting no precedent), and a skill PR whose own body said it was
    awaiting a human merge was flipped ready by an unidentified seat and landed by the merge queue with zero reviews of
    any kind. **The barrier is this directive.** The per-PR approval check beside it retired under 2026-08-18's ruling
    that a human merge IS the review record — 「人工合并即人工审核」; why, and why its successor is the
    queue guard rather than a per-PR gate, is in that guard's header. ⛔ Not a relaxation. Behind the directive sit
    prevention and detection: that guard refuses an unpinned governed diff in the queue, `docs/adr/` in CODEOWNERS
    routes review requests — and it is the *only* governed surface routed there, so on the other four nothing summons
    the maintainer automatically — while the report-only post-merge audit (`scripts/pm/check-governed-merges.mjs`,
    whose header carries this rule's incident history) lists every governed-surface merge for the PM round report. Every
    entry should be a merge the maintainer performed or ordered in person, and the audit reads the approver as well as
    the merger; one he does not recognise, or any agent approval, is a seat violation, filed and rolled back. A seat
    that has read this far is not thereby licensed to judge an exception; the rule has no exception to judge.

What each dispatch item became

1. "Reviewed + approved + fully green does not override this." — removed. Its true residue survives as "Nothing else substitutes: ... 'CI is green' carries no information at all", which still says green alone authorizes nothing.
2. Prohibitions conditioned — the four ⛔ items are left verbatim, and the next sentence conditions them: "Those four lift only for an authorized approval pinned to the current head". The bypass direct merge stays named as the fallback ("Unpinned, the maintainer's bypass direct merge (人工直合) is the only landing"), and expiry-on-push is stated.
3. Agent-approval prohibition — added in the same paragraph, immediately after the landing rule, with its reason ("an authorized account is agent-operated too"). The audit half moved into paragraph 3 where the audit already is: "the audit reads the approver as well as the merger; one he does not recognise, or any agent approval, is a seat violation".
4. Provenance by date — "(2026-08-27; guard 2026-08-28)", and the predicate/set referenced only as GOVERNED_APPROVERS in scripts/pm/check-governed-queue-guard.mjs. The account names are not restated.

Two corrections in paragraph 3 are not optional extras: "it is the only pre-merge barrier there is" and "detection, not prevention" both became false when the queue guard's merge_group leg started refusing, and naming the guard in paragraph 1 while leaving those standing would author a fresh contradiction. Both are in the cut ledger.

Generated by Claude Code

---

Generated by Claude Code

[os-litant]

决策卡 (Director/skills seat, session session_01MnijPVVDakqK2J335JoJtq) — marker, literal spelling for the scanner: os-decision-facets

问题:执行本卡实测撞死天花板。AGENTS.md 在 1158/1158(零余量),PD #14 修正在七刀可记账裁减全部用尽后仍 +2 行;三个段落在门禁自己的 wrapLine 下重排余量为 0,再砍只能砍别处无家的证据(全绿 ADR 被关事件、draft-非屏障事件——已 grep,无幸存去处)。门禁红文自己指明出路:「Raising a ceiling requires a maintainer ruling quoted in the PR.」

选项:

• A(荐):裁决抬天花板,裁决引文入 PR body。顺带把 AGENTS.md § Skills carries the same pre-approve-path wording as PD #14: "never queued, armed or flipped out of draft" is unconditional, and "Prime Directive #14 is the whole barrier" is stale since the queue guard #12896(同文件 § Skills 段同类过时句,「never queued…」无条件式 + 「PD feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14 is the whole barrier」)折叠进同一 PR——一次裁决覆盖两段;最终行数以交付 PR 实测为准(仅 PD feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14 为 1158→1160,折叠后交付时报精确数)。落地稿已在卡上(dev 评论,标 do-not-apply-without-ruling),一个 commit 即成。
• B:硬凑净 0——代价是砍掉两件别处无家的事件证据,从席位正好要读它的位置删除。
• C:只删假句不加新文(净 −1)——假话没了,但禁止清单仍无条件、批准通道与 ⛔ agent-永不批准 都不落,文件继续与已生效裁决相悖,只是声音小些。
• D:挂起等裁——每个席位继续读到「Reviewed + approved + fully green does not override this」这句已经为假的话。

荐 A 理由:批准通道是您问出来、裁出来、且机械上已生效的工作流(今晨 #12755 自举落地),PM skill 侧文本已同步,AGENTS.md 是最后一块过时面——而它是每个席位最先读的。C 最危险:禁止清单读作绝对而机器门另说,本指令自己就记录过两起席位按过时读法行事的事件。+2 行是七刀真裁减后的地板,不是初稿。

回复一个字母即可。State: needs-user-decision。

---

Generated by Claude Code