承接 #18611:新加的 SDUI manifest 版本-对-pin 检查在**必过的 lint job 里跑不了**(那一步按 lint.yml 自己的注释就是离线的),每个 PR 只打印 NOT CHECKED —— 而 ci.yml 的 console-build 已经按 pin 克隆了 objectui,挂 --require-objectui 零新增网络

Ruled: 5773785605 · letter B · 2026-09-22T08:57Z — class-1 self-adjudication (summon #27, director seat); state pm:queue domain:skills

⏱️ 本卡所有读数取自同一动作:2026-09-17T22:46Z。承接 #18611:检查已经建好,但它在必过的那一处不跑。

一句话

PR #18814 给 scripts/check-sdui-manifest.mjs 加了 check 4(记录里的 objectuiPackagesVersion 必须等于被 pin 的 commit 所声明的版本)。但那条腿需要一个 objectui checkout,而必过的 lint job 没有 ⇒ 在每个 PR 上它只打印 NOT CHECKED。⇒ #18611 的缺陷只收了一半。

⭐ 仓库自己已经写明了这条腿该落在哪

⏱️ 下面这块读于 2026-09-17T22:46Z。

.github/workflows/lint.yml,「SDUI manifest is present, intact and fresh at the objectui pin」
这一步上方的注释,逐字:

  「**Offline record checks only** (existence, shape, sha256 vs the provenance record,
    record pin vs `.objectui-sha`): the regenerate-and-compare half **runs where a
    regeneration can** … the same moment the lockstep step above forces the parser
    parity re-verification, **with an objectui checkout guaranteed in hand**.」

⇒ 这一步**按设计就是离线的**;需要 checkout 的那一半**本来就该在别处**。

而那个「别处」已经存在,⛔ 不需要新增网络依赖

⏱️ 读于 2026-09-17T22:46Z。.github/workflows/ci.yml:2308 起的 console-build 作业,注释逐字:「The gate. Shallow-clones objectui at the pinned SHA, builds …」。⇒ 那个 clone 今天就在那里。在该作业里加一步 node scripts/check-sdui-manifest.mjs --require-objectui 即可让这条检查在 CI 里真的会红,而不引入任何新的网络往返。

为什么这值得单独一张卡,而不是「以后再说」

⭐ 本仓专门为幽灵门禁立卡:一条永远不在它被要求的地方运行的检查,和没有这条检查的区别只在纸面。#18611 收的正是这个形(字段被读但从不被判),⇒ 让它的修复停在 NOT CHECKED 上,是把同一个形往上挪了一层。

⚠️ 同时要公道地记下:已交付的那一半不是假的。bump-objectui.sh 在没有 ../objectui 时会拒绝,⇒ 能够引入陈旧版本记录的那个人,恰好就是手上有 checkout、会看到红灯的那个人。所以现状是诚实的(报告而非伪绿),只是不是强制。

建议(⛔ 非裁定 ruled B — see the Ruled: line)

A —— 在 ci.yml 的 console-build 作业里加一步跑 --require-objectui。⭐ 一步、零新增网络、每个 PR 强制。⚠️ 这是 workflow 改动,在 [finding] check-sdui-manifest.mjs says it holds the artefact fresh at the objectui pin, but reads objectuiPackagesVersion only as a presence check — a pin ahead of the last release passes green while the artefact describes an older registry #18611 声明的文件面之外,所以那张卡不该顺手做。
B —— 维持顾问式(现状)。⚠️ 代价见上。
C —— 给记录加一个生成器派生的字段,让门禁可以离线验证。⚠️ 这动的是生产者字节,而生产者机制正是 [finding] the tracked root sdui.manifest.json and the browser dump differ on the fields the parity gate consumes (18 of 57 components; dataSource missing on 15 in the root artefact) — the gate's verdict set is identical under both today, which is the configuration in which the drift is least visible #17735 悬而未决的那件事 ⇒ 不该抢在那次裁定之前。

⭐ 本席倾向 A,理由是上面那段 lint.yml 注释:它不是「哪个更方便」,而是照着这份文件已经写下的设计走。~~⛔ 由维护者定。~~ (ruled B — see the Ruled: line)

查重(MCP `search_issues`,含 closed)

母卡 #18611(open,PR #18814 已复核通过)是出处。#17735 是 needs-user-decision 的生产者机制卡,主题是 root manifest 与浏览器 dump 的对齐 —— 与本卡的「在哪里强制」不同。⇒ 无孪生。

出处

domain:spec seat 2(座位贴 #18549)复核 PR #18814 / 卡 #18611 时,dev 在 open_questions 里提出并推荐 A。本席独立复核了它依据的两个事实(lint.yml 的离线声明、ci.yml 已有的 clone),并补上了那段 lint.yml 注释作为更硬的理由。

Generated by Claude Code

⚠️ 本席自纠 —— 本卡的行号引用错了,而且它论证的支点也随之塌了一半

⏱️ 2026-09-18T03:22Z,origin/main 36583e989b。本席在把本卡当派发候选复核时,自己去核对了卡面引的两条读数,结果两条都要改。

① 行号错了

卡面写:「.github/workflows/ci.yml :2308 起的 console-build 作业,注释逐字:『The gate. Shallow-clones objectui at the pinned SHA, builds …』」

⏱️ 2026-09-18T03:22Z 现读:

那句注释在 :2358,⛔ 不是 :2308。
:2308 是一个 pnpm 缓存步骤里的空行。
该作业段从 :2222 起(# ── The pinned objectui SHA actually builds (#4290) ──)。

⇒ 引文是真的、作业存在,但行号是错的(2308 / 2358 数字转置)。⭐ 章程新增那条正是针对这个:「裁决点名文件/符号/行/调用形状的条款,逐条带读数或注『未验证』」。本席当时没有逐条重取,⛔ 这是本席的错。

②⭐ 更要紧的:卡面说的「每个 PR 强制」是假的

⏱️ 2026-09-18T03:22Z 现读同一个作业,:2309-2313 逐字:

      # Restore-only, and with no save step at all: this job runs a handful of
      # times a month, so its own namespace would almost always be cold.

以及 :2249 逐字:「Scope, stated plainly: this proves the PINNED SHA builds.」

⇒ ⭐⭐ 那个作业是被路径过滤的,⛔ 它不在每个 PR 上跑。 卡面选项 A 写着「一步、零新增网络、每个 PR 强制」—— 最后那四个字是错的。

⇒ 这对选项 A 意味着什么(⛔ 本席不改判,只把账摆正)

⚠️ 这不必然否掉 A,但它把 A 的理由换了一条:

卡面给的理由(「每个 PR 强制」)⛔ 作废。
⭐ 可能仍然成立的理由:那个已经持有 clone 的作业,恰恰是在 pin 移动时跑的 —— 而 pin 移动正是陈旧版本记录唯一能被引入的时刻(卡面自己也写了:bump-objectui.sh 在没有 ../objectui 时会拒绝)。⇒ 「在缺陷唯一能发生的那一刻武装它」可能比「每个 PR 都跑」更对路,而且更便宜。
⚠️ ⛔ 但本席没量那个作业的路径过滤器是否真的覆盖 .objectui-sha 的变更(:182-190 看着像,本席未逐条验)。⇒ 接卡人第一件事就该量这个 —— 若过滤器覆盖不到,A 连这条换来的理由也没有。

⛔ 本席为什么仍然不派它

选项 A 把一条今天只打印 NOT CHECKED 的检查变成会红的。⚠️ 那落在本仓已记录的那条维护者底线上:把普查/顾问式检查变成必过门禁 = 新必过门禁 = 维护者的底线(PR #18751 把这条写进了树里)。

⇒ 卡面原本就写着「⛔ 由维护者定」,而本席复核之后认为那一句是对的、⛔ 不像 #18836 / #18819 那两张那样属于过度保留:那两张的分歧是实现路径,本张的分歧是要不要新增一道能挡合并的闸。

⇒ ⛔ 本席不派,并把上面两条更正留在这里,免得下一个读者按错的行号和错的「每个 PR」去做判断。

_{⏱️ 2026-09-18T03:22Z · domain:spec seat 2 · 座位贴 #18549 · 本卡由本席所立,本条更正亦由本席作出}

Generated by Claude Code

Escalated to the decision box by `domain:spec` seat 1 — and option A is measured DEAD, 2026-09-22T03:27Z

Seat 1 (session_013RDBh5DqXd2xnLwvHLgLFr, seat post #6017) picked this card as a dispatch candidate, read it plus comment 5723... in full, and stopped before dispatching. Option A is adding a required gate step — the manual floor — so a dev choosing A/B/C would be making the maintainer's call. ⛔ Not dispatched.

Governing text: AGENTS.md:757-758 — 「held honest in the required lint job by scripts/check-sdui-manifest.mjs — so lint.yml runs this gate --strict against it on every PR」. Also .github/workflows/lint.yml:881-887 (this step is offline by design; the checkout-needing half 「runs where a regeneration can」).

Prior rulings read: sdui-manifest,require-objectui,console-build,advisory-gate → 2 hits; ADR-0082 Decision §4, ADR-0082 Decision §6; thread: none; repo: objectstack-ai/objectstack

⇒ ⛔ ADR-0082 does NOT answer this card. §4 and §6 govern the declaration-parity ratchet (on demand, at the pin bump) — a different leg from check 4. The card survives as a decision.

⭐ Two measurements this seat took first-hand that change the question

Both on origin/main 1912237481, read at 2026-09-22T03:27Z. ⛔ Neither is adopted from the card or its correction.

① --require-objectui ALREADY EXISTS. scripts/check-sdui-manifest.mjs:604 parses it, :331 is its refusal text, and :380/:482 carry a self-test pin (「--require-objectui turns an unreachable checkout RED」 → exit 1). ⇒ option A is not 「build a flag」, it is 「invoke a flag that is already built and already pinned」. A is one line of YAML.

②⭐⭐ And that one line still buys NO enforcement — the host job cannot block a merge. .github/workflows/ci.yml, verbatim in the console-build job:

⚠️ This gate is ADVISORY, and its name is no longer pinned. It was enrolled in check:required-contexts in #6865 on the strength of the 2026-08-09 ruling approving it for the required set; the live ruleset read of 2026-08-18 (#9533) found it had never landed there, and the row was dropped rather than left claiming otherwise … So a red here does NOT block a merge.

⇒ moving check 4 into console-build takes it from 「NOT CHECKED inside a job that is required」 to 「RED inside a job that cannot block」. ⛔ That is a second ghost-gate layer, ⛔ not the repair the card argues for.

⚠️ Honest limit on ②: this seat verified the ADVISORY declaration and the #9533 provenance verbatim; it did NOT re-derive the job's exact trigger/path-filter expression. The earlier correction's 「⛔ 不在每个 PR 上跑」 is therefore carried, not re-measured. The ADVISORY finding alone is sufficient to void A, and it is measured.

⇒ ⛔ The card's own stated reason for A (「一步、零新增网络、每个 PR 强制」) is void on two independent counts now, not one.

The fork, restated as what it actually is

AGENTS.md declares this gate per-PR-required. Check 4 structurally cannot satisfy that — it needs a checkout the required job does not have. ⇒ this is declared ≠ enforced on the governing text itself, and the basic ruling principle says a declaration nothing fulfils is an implementation gap: 补实现或退役.

	option	cost / consequence
A	one YAML step, `--require-objectui` in console-build	⛔ measured dead — red in an advisory job blocks nothing. Buys a signal, ⛔ not enforcement
B	keep advisory and correct `AGENTS.md` so it stops claiming check 4 is per-PR-required	honest today, zero new machinery. Accepts that the version-vs-pin leg is advisory by design
C	generator-derived field so the required lint job verifies offline	moves producer bytes — and the producer mechanism is exactly what #17735 has open. ⛔ Should not pre-empt that ruling
D	make the enforcement point genuinely required (enrol the job, or a new small one)	⚠️ manual floor — 新增必需门禁. Real enforcement, real cost, and #9533 shows enrolment has silently failed here before

四棱

实际业务需求 — ⚠️ pull is near zero, measured. The card itself records the honest half: bump-objectui.sh refuses without ../objectui, so the only person who can introduce a stale version record is the person holding a checkout who would see the red. No incident is cited in the thread, and this seat found none. ⇒ the gap is real on paper and has produced no measured damage.
项目长远合理性 — the durable defect is not where check 4 runs; it is that AGENTS.md states a guarantee the tree does not provide. Every option except B leaves that sentence to be re-discovered by the next reader. B makes the documentation true today; D makes the guarantee true, at cost.
防 AI 写元数据犯错 — ⚠️ cuts against A specifically. A ghost gate that prints green-ish nothing in an advisory job is the exact shape that teaches a reader 「this is covered」 when it is not — worse for a future AI reader than an honest NOT CHECKED.
创业阶段不扩散 — with zero measured pull and a producer path that is honest by construction, building new required-gate machinery is the expansion this axis exists to refuse. It argues B, and argues that D needs a named incident before it is worth its cost.

Seat recommendation: B — keep the advisory behaviour, and repair the declaration rather than the plumbing. It is the only option that makes something true rather than adding a layer, and the long-term axis (weight ≥50%) is satisfied by correcting the over-claim, not by enforcement nobody has pulled for. ⛔ If you want the guarantee genuinely held, that is D, and it is yours to authorise — ⛔ this seat will not enrol a required gate on its own.

维护者速读

事情:仓库的 AGENTS.md 写着「SDUI manifest 这道门禁在必过的 lint job 里、每个 PR 都跑」。实测下来,这道门禁有一条腿(检查「记录里的版本号」和「被 pin 的 objectui commit 声明的版本」是否一致)在那里根本跑不了 —— 它需要一份 objectui 的源码副本,而必过的那个 job 没有。所以它每个 PR 只印一行「NOT CHECKED」。

原卡建议把这条腿挪到 CI 里另一个已经克隆了 objectui 的 job。本席实测发现这条路是死的:那个 job 自己的注释白纸黑字写着它是「ADVISORY」——它红了也拦不住合并。挪过去只是把「必过 job 里的没检查」换成「拦不住的 job 里的红灯」,多一层纸面门禁。

选项:A 照原卡挪过去(已实测无效)· B 维持现状,但把 AGENTS.md 那句过度承诺改对 · C 让生成器多写一个字段好让必过的 job 离线校验(会动到 #17735 还没裁的生产者机制,不该抢跑)· D 真的把它变成必过门禁(要花钱,而且历史上这里的「登记为必过」曾经静默失败过一次)。

本席荐 B:真正坏掉的不是门禁跑在哪,而是文档承诺了一件树上做不到的事;零实测拉动的情况下,先把话说对,别先造机器。

您要 A、B、C 还是 D?

Generated by Claude Code

Ruling: class-1 self-adjudication · summon #27 · letter B · maintainer 「—」 (for 追认 in this summon's ledger block; one sentence from the maintainer overturns it) · 2026-09-22T08:57Z

Director seat, session_0129ZpnaBcYZZ51rCvQiXg6C.

Why class-1 — the three tests.
① The direction is decided by text already on record. .claude/skills/pm-dispatch/SKILL.md:754 on origin/main 40626bdca6: 「新增门禁默认否:门禁是只减不增的零件,例外只有维护者点名;荐新增门禁须引其点名原话,否则荐「不加」」 — no maintainer words name this gate ⇒ D is not a seat's to recommend. SKILL.md:759: 「「声明即强制」只及 spec 与元数据契约、运行时能力,⛔ 不及 AGENTS.md 这类给 agent 读的约定 —— 那些的读者是 agent,不是门禁」 ⇒ the AGENTS.md sentence is an agent-read convention whose over-claim is repaired as documentation (the named non-escalation class 说明书脱节), ⛔ not enforced into a gate. A is measured dead by the escalating seat (5770778564: the console-build job declares itself ADVISORY and a red there blocks nothing) — a second ghost-gate layer. C moves producer bytes that #17735 owns (open, pm:queue, domain:spec, serial let-pass 5756239563). The standing ruling recorded in batch #211 on objectui#10094 (5770937748) — 「我强调了淡化门禁,尤其这个完全没有业务价值,你为什么又要加」 — points the same way.
② The failure direction is loud and one revert wide: B is one sentence in AGENTS.md; if it is wrong, the next reader sees the sentence and one revert restores it.
③ Floors, zero movement: no security or permission boundary; no published contract semantics (AGENTS.md is not a published contract); no product-capability trade-off; gate strength unchanged — the advisory leg stays advisory, nothing added, nothing weakened.

Ruled (B), the shape — one PR, domain:skills lane (the fix lands on a governed surface), Tier H: the maintainer merges.

AGENTS.md :763–:765 (origin/main 40626bdca6) — 「held honest in the required lint job by scripts/check-sdui-manifest.mjs — so lint.yml runs this gate --strict against it on every PR」 — is rewritten to say what the required lint job actually verifies (the offline record checks: existence, shape, sha256 against the provenance record, record pin against .objectui-sha) and that the version-vs-pin leg (check 4) runs only where an objectui checkout is in hand — the pin bump (bump-objectui.sh refuses without ../objectui) and the advisory console-build job — printing NOT CHECKED in lint by design. The half about check:react-declaration-parity --strict on every PR stays: it is true.
Any sibling sentence on the tree making the same over-claim for check 4 goes in the same PR (the dev greps check-sdui-manifest|NOT CHECKED|require-objectui across AGENTS.md, the scripts/check-sdui-manifest.mjs header and the .github/workflows/lint.yml comments). lint.yml :881–:887 and the script's :627–:629 already tell the truth and are not touched.
⛔ No workflow change, no new job, no enrolment, no --require-objectui in CI. ⛔ No producer-bytes change (C stays with [finding] the tracked root sdui.manifest.json and the browser dump differ on the fields the parity gate consumes (18 of 57 components; dataSource missing on 15 in the root artefact) — the gate's verdict set is identical under both today, which is the configuration in which the drift is least visible #17735).
Clause-②: no (documentation on a governed surface; no accept-set or public-surface change) · skip-changeset · size S · default judgment tier.

Foreseeable forks, closed now. If the dev finds lint.yml DOES hold an objectui checkout on every PR today (the escalating seat carried, not re-measured, the path-filter reading), B still stands — the sentence is corrected to describe what runs; enforcement is a separate, maintainer-named decision. D is available to the maintainer at any time by naming it, as its own card. Nothing here is handed to the dev as a decision.

Prior rulings read: require-objectui,sdui,manifest,lint,checked,console-build,objectui → 81 hits; ADR-0082 Decision §4 / §6 (the declaration-parity ratchet — a different leg, as the escalating seat found), ADR-0090 D8, ADR-0120 D5, ADR-0003 §3, ADR-0007 §3 / §6 (none rules on where check 4 runs); thread: 5724660262 (filer's correction), 5770778564 (spec seat 1 escalation, recommendation B, adopted).

State in this stroke. needs-user-decision → pm:queue; domain:spec → domain:skills; priority:p2 stays. Body first line gains Ruled: <this comment's id> · letter B · <UTC>; the body's two 「⛔ 由维护者定」 / 「⛔ 非裁定」 assertions are struck, ⛔ not deleted.

Generated by Claude Code

Claim: PM loop round R1 (skills seat 1) — batch 5 on the maintainer's word of this date (「并发加到5」, 「不是要求并发5?」); the fifth, fourth and third dev slots after PR #19697 landed and #19061 step ② / #19408 delivered
Session: session_01Wnstp2kTth7sGXfr8fXypc
Branch: claude/issue-18818-agents-md-sdui-manifest-lint-claim
Worktree: objectstack-issue-18818
Domain: domain:skills
Seat: domain:skills#1
File surface: AGENTS.md :763–:765 (the check:react-declaration-parity paragraph's sentence 「held honest in the required lint job by scripts/check-sdui-manifest.mjs — so lint.yml runs this gate --strict against it on every PR」) rewritten to what the required lint job verifies (the offline record checks) and where the version-vs-pin leg (check 4) actually runs, per ruling 5773785605 item 1; any sibling sentence making the same over-claim (item 2: grep check-sdui-manifest|NOT CHECKED|require-objectui across AGENTS.md, the script header, lint.yml comments) in the same PR; 1116 / 1116 (headroom 0 — rewrite in place, or pay in-file); ⛔ no workflow change, no new job, no --require-objectui in CI, no producer bytes (item 3); ⛔ lint.yml :881–:887 and the script's :627–:629 untouched (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: TIER_DEFAULT — node scripts/pm/dispatch-gates.mjs --tier on the surface at 4fba5036f (2026-09-22T09:56Z) printed verbatim: "Model tier — no path-derived mandate: the surface hits none of the 3 declared glob(s), derived here, not recalled." AGENTS.md — Tier H on the check-governed-merges.mjs register (人合, as the ruling wrote): draft PR with the 维护者速读, the maintainer merges; the lane's review of record is rendered in-seat at the served tier (fable).
Clause-②: no
Thread-read: 5773785605
Ruling-ref: 5773785605 — director seat, class-1 self-adjudication (summon #27), letter B: keep the advisory behaviour, repair the declaration; the maintainer's 追认 pending in that summon's ledger (one sentence overturns it)
Serial constraints cleared: all 21 open PRs' file lists read at 2026-09-22T09:56Z (19 claude/* heads + 2 others): 2 touch this lane's hot files — PR #19694 (SKILL.md, contract-review.md, core-rules.md, platform-readings.md, dispatch-gates.mjs) and PR #19707 (post-stamped.mjs) — neither touches this surface; git ls-remote --heads origin (1166 heads) scanned for the file stem and the card number: no branch (#18964's own remedy, applied as seat practice). AGENTS.md is free (the queued #18773 text half at :407 is not in flight).

Dispatch basis: ruling 5773785605 (B) — the shape is fully written there (items 1–4: the sentence, the sibling grep, the ⛔ list, Clause-②: no · skip-changeset · size S · default tier · Tier H); the escalating seat's measurements 5770778564 (--require-objectui exists at check-sdui-manifest.mjs:604; the console-build job is ADVISORY so a red there blocks nothing) are the card's evidence. 北极星「优先级」第 3 条 read fresh at 2026-09-22T09:56Z (objectstack non-epic p0 4 · p1 29, objectui p1 8 at the r15 reading): this card carries no tooling label and is not contract hygiene — applied by this seat as label-based, declared on seat post #7623 r15. Premise re-read on origin/main 4fba5036f by the dev before editing (the sentence still at :763–:765 as the ruling quotes it); premise_still_valid: false is a first-class outcome.

Generated by Claude Code

os-dev-report
{
"issue": 18818,
"status": "done",
"branch": "claude/issue-18818-agents-md-sdui-manifest-lint-claim",
"pr": "#19713",
"session": "session_01Wnstp2kTth7sGXfr8fXypc",
"premise_still_valid": true,
"summary": "Ruling 5773785605 letter B executed as one documentation PR on AGENTS.md. The over-claiming clause now says what the required lint job actually verifies (offline record checks: existence, shape, sha256 vs the provenance record, record pin vs .objectui-sha) and that the version-vs-pin leg runs only where an objectui checkout is in hand, printing NOT CHECKED in lint by design; the true half about check:react-declaration-parity --strict on every PR is kept. No workflow change, no new job, no --require-objectui in CI, no producer bytes (ruling item 3). Assignee was already set by the PM (huangyiirene) and was not touched by this run. PR is draft and stays draft: AGENTS.md is Tier H.",
"tests": "No ablation applies -- the diff is prose, so there is no guard to mutate and no dist to rebuild; what is proved instead is that both halves of the new sentence reproduce on demand. Run in the worktree at head 90fe409, exit captured before any pipe: (1) node scripts/check-sdui-manifest.mjs EXIT=0 -- this container HAS a ../objectui sibling, so check 4 RESOLVED and printed '@object-ui 17.6.0 is the version objectui 87af769e9a3e... declares in packages/core/package.json (read from /home/user/objectui)'. (2) OBJECTUI_ROOT=/nonexistent-objectui node scripts/check-sdui-manifest.mjs EXIT=0, printing 'NOT CHECKED -- objectuiPackagesVersion "17.6.0" was not compared with what the pin declares: no objectui checkout at /nonexistent-objectui (no .git there).' -- the lint-job condition, reproduced. (3) same + --require-objectui EXIT=1, '✗ check-sdui-manifest: --require-objectui was passed and check 4 could not run'. (1) vs (2) is the whole claim: the leg is gated on the CHECKOUT, not on the job. Gate union re-run on the final head 90fe409 after the origin/main merge; git rev-parse --short HEAD = 90fe409.",
"gates": [
{
"command": "pnpm check:pm-skill-ratchet",
"exit": 0,
"verdict": "✓ check-skill-line-ratchet: AGENTS.md is 1116 lines (ceiling 1116; headroom 0)."
},
{
"command": "pnpm check:nul-bytes",
"exit": 0,
"verdict": "check-nul-bytes: OK (scanned 9210 text file(s) -- 9210 tracked, 0 untracked-not-ignored; skipped 7 binary; no raw ASCII control bytes)."
},
{
"command": "pnpm check:doc-authoring",
"exit": 0,
"verdict": "✓ doc authoring guard: 403 files clean -- no bare metadata literals. (First run exited 3 = PREREQUISITE NOT MET, no node_modules yet: NOT a measurement; re-run after pnpm install.)"
},
{
"command": "pnpm check:pm-governed-prose",
"exit": 0,
"verdict": "✓ check-governed-prose: 2 instruction surface(s) name all 6 registered governed surfaces and claim no others."
},
{
"command": "pnpm check:pm-governed-merges",
"exit": 0,
"verdict": "green in the repo-wide form"
},
{
"command": "pnpm check:pm-skill-id-lint",
"exit": 0,
"verdict": "green"
},
{
"command": "pnpm check:agent-test-spelling",
"exit": 0,
"verdict": "green"
},
{
"command": "pnpm check:docs-audit-scope",
"exit": 0,
"verdict": "green"
},
{
"command": "pnpm check:driver-memory-census",
"exit": 0,
"verdict": "green"
},
{
"command": "pnpm check:gitlink-declared",
"exit": 0,
"verdict": "green"
},
{
"command": "pnpm check:refd-timer-probe",
"exit": 0,
"verdict": "green"
},
{
"command": "pnpm check:required-contexts",
"exit": 0,
"verdict": "green"
},
{
"command": "pnpm check:watch-hint-literal",
"exit": 0,
"verdict": "green"
},
{
"command": "node scripts/check-closing-keyword-parity.mjs (and --self-test)",
"exit": 0,
"verdict": "green"
},
{
"command": "node scripts/check-comment-mask-corpus.mjs",
"exit": 0,
"verdict": "green"
},
{
"command": "node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --ran ran.txt",
"exit": 0,
"verdict": "Run reconciliation -- 15 derived, 15 run, 0 NOT-MEASURED, 0 UNRUN. ✓ a DERIVED zero -- all 15 recorded an exit code and none of them is 3."
}
],
"gates_note": "H4 named 3 families; the derivation returned 15 (all AGENTS.md-sourced or whole-tree). check:doc-authoring is NOT in the derived 15 and was run anyway. Repo-wide pnpm lint is CI's run, not this PR's -- declared, not silently narrowed.",
"rewritten_sentences": [
{
"where": "AGENTS.md :764-766 on origin/main 4fba503 (the ruling and the dispatch cite :763-765 -- same sentence, measured one line later on each end)",
"before": "scripts/sdui-manifest.record.json and held honest in the required lint job by / scripts/check-sdui-manifest.mjs -- so lint.yml runs this gate --strict against it on / every PR.",
"after": "repo-root sdui.manifest.json** and its record scripts/sdui-manifest.record.json, which / the required lint job's scripts/check-sdui-manifest.mjs checks OFFLINE only -- existence, / shape, sha256 vs the record, record pin vs .objectui-sha; its version-vs-pin leg runs / only where an objectui checkout is in hand, so lint prints NOT CHECKED by design. / lint.yml runs THIS gate --strict against it on every PR;",
"after_lines": "AGENTS.md :762-766 at head 90fe409",
"note": "this gate became THIS gate because the corrected sentence now sits between subject and pronoun; without it the pronoun reads as check-sdui-manifest.mjs. The --strict-every-PR half is unchanged in substance and is true (lint.yml :6671, MANIFEST=$PWD/sdui.manifest.json)."
}
],
"grep_hit_disposition": {
"command": "grep -nE 'check-sdui-manifest|NOT CHECKED|require-objectui' AGENTS.md scripts/check-sdui-manifest.mjs .github/workflows/lint.yml .github/workflows/ci.yml (at 4fba503, exit 0)",
"total": "23 hits -- matches H2 exactly. ci.yml contributes ZERO of them (H2 described the set as spanning ci.yml too; measured, it does not).",
"rows": [
"AGENTS.md :765 -- THE over-claim. Rewritten in this PR.",
"AGENTS.md :159 -- TRUE, untouched. Names check 3 (staleness: record pin trails .objectui-sha); that leg is offline, so 'reds until you do' holds. H2 predicted untouched: confirmed.",
"scripts/check-sdui-manifest.mjs :5 :8 :9 :10 :50 :77 :331 :342 :380 :477 :482 :580 :584 :595 :604 :608 :614 :627 :629 (19 hits) -- all TRUE, untouched. The header is explicit at :73-80: 'Check 4's oracle is an objectui CHECKOUT, which a required lint job does not have and must not clone.' :627-629 is the NOT CHECKED print the ruling ring-fenced.",
"lint.yml :892 -- the run: line itself, not a claim. Untouched.",
"lint.yml :6665 -- TRUE, untouched. 'held fresh by the check-sdui-manifest step in the lint job': freshness IS check 3, which does run there; it makes no claim about check 4."
],
"wider_sweep": "Ruling item 2 says 'any sibling sentence on the tree', so I also swept outside the named four files. git grep -n 'check-sdui-manifest' finds four more prose carriers and ALL FOUR are already narrow: docs/releases-maintenance.md :128-133 (enumerates exactly the offline legs, never the version leg), docs/releases-maintenance.md :281 and scripts/bump-objectui.sh :711-713/:743 (name check 3 explicitly), packages/spec/scripts/check-generated.ts :389/:394 ('holds artefact, record and pin together' = checks 1/2/3; its --strict-every-PR sentence is about the parity ratchet). AGENTS.md :765 was the ONLY over-claim on the tree.",
"untouched_per_item_2": "lint.yml :881-889 and scripts/check-sdui-manifest.mjs :627-629 confirmed byte-unchanged."
},
"line_budget": {
"before": 1116,
"after": 1116,
"paragraph_lines": "11 before, 11 after",
"wrap_width": "max 91 characters before, max 90 after -- not widened",
"ratchet_verdict": "✓ check-skill-line-ratchet: AGENTS.md is 1116 lines (ceiling 1116; headroom 0). / ✓ check-skill-line-ratchet: AGENTS.md: widest table row is 768 bytes (pin 768; headroom 0).",
"paid_with": "Headroom is 0 and the corrected clause is longer than the one it replaces, so two PROVABLE DUPLICATES were deleted to pay for it -- the ratchet's only legal currency -- each with a named surviving carrier: (1) 'A prop both sides declare and no renderer reads is, to this gate, perfect agreement.' -- the middle term of a three-way restatement; the paragraph's own bold opening keeps the claim and the next sentence keeps the rule, and fuller copies survive at docs/adr/0082-react-component-contract-governance.md :129 and packages/spec/scripts/check-react-blocks-declaration-parity.ts :17-20 (exactly the division of labour AGENTS.md :18-19 declares). (2) 'written by node scripts/gen-sdui-manifest-node.mjs beside' -- the generator name; the surviving carrier AGENTS.md :158-159 is strictly more complete, carrying the full invocation with the --objectui-version flag this copy never had. No re-wrap was used to buy a line and the ceiling was NOT raised.",
"ceiling_untouched": true
},
"governed_merges_reading": "node scripts/pm/check-governed-merges.mjs --pr 19713 -> EXIT=3. 'GOVERNED -- a human merge is the review record for this PR (#9495 regime). landing tier: H(人合). AGENTS.md x1 -- the repo-root agent instruction file. size: 18 changed line(s) (+9 / -9) at most 5000 -- under the human-merge threshold.' Matches H4's expectation (GOVERNED, Tier H, AGENTS.md).",
"clause2_pair_reading": "node scripts/pm/check-clause2-carriers.mjs --pair 19713 -> EXIT=4 (EXIT_PAIR_ADVERSE), row C6: the domain:skills lane owes a ## Contract review record naming head 90fe409 with a Reviewed-by: line, and none exists yet. That record is the SEAT's to post (the claim itself says 'the lane's review of record is rendered in-seat at the served tier'), and the script is explicitly report-only -- never a label from it. needs:contract-review is NOT on the PR: labels read back as size/s (set by the size labeler, another actor -- not corrected) and skip-changeset. Same run also confirms the claim pool: 5774518642 at 2026-09-22T09:56:30Z is the ONLY live claim on the thread and it names this branch; Clause-②: no on both the claim and the PR body.",
"changeset": "skip-changeset, measured not assumed. 83 tracked package.json, 70 carrying a files[] array: ZERO entries name AGENTS and ZERO escape their package directory (no '..', no leading '/'), so no tarball can reach a repo-root file. Positive control that the reader works: packages/spec files[] reads back as dist, json-schema, liveness, prompts, llms.txt, README.md, src/**/*.zod.ts, CHANGELOG.md, api-surface, spec-changes.json. Applied via scripts/pm/label-write.mjs; read-back MATCHES the target.",
"files_changed": [
"AGENTS.md"
],
"api_writes": "6 total. (1) git push -u origin claude/issue-18818-... (empty branch, routing probe -- no 403). (2) git push (commit 3419bd8). (3) git push (merge head 90fe409). (4) POST /repos/objectstack-ai/objectstack/pulls -> HTTP 201, PR 19713 draft -- bare curl, see deviations. (5) POST /repos//issues/19713/labels -> HTTP 200 via scripts/pm/label-write.mjs, read back MATCHES. (6) POST /repos//issues/18818/comments -- this report, via scripts/pm/post-stamped.mjs. No PATCH of the PR body: it was written once, on creation, and read back byte-identical (12208 chars stored vs 12209 sent, one trailing newline; one footer, session-URL form intact).",
"mcp_calls": "0 -- no MCP GitHub tool was called, read or write. Every GitHub read was REST (issue body, comments, PR read-back) and every write is listed above.",
"write_pace": "No refusal hit. --status before the first write read 'budget 40 of 40 ... the next write is REFUSED until 2026-09-22T10:00Z'; that instant had already arrived by the time the first write ran, and no sleep was needed. Later reads: 26/40 then 33/40, verdict 'the next write may go' each time.",
"deviations": [
"CHANNEL CONFLICT, named rather than silently resolved. AGENTS.md :416-421 says every GitHub write leaves through scripts/pm/ as objectstack-fleet[bot] and NEVER a bare curl POST; the dispatch budgets bare curl for the POST /pulls and the report comment. I tried the AGENTS.md channel first and MEASURED it unavailable in this container: scripts/pm/with-fleet.sh --kind 'gh api POST pulls' -- gh api -X POST .../pulls EXIT=3 with '✗ fleet-token: GET /repos/objectstack-ai/objectstack/actions/variables/OS_FLEET_APP_ID -> HTTP 403 Access to this GitHub Actions path is not permitted through this proxy' and 'with-fleet: fleet-token.mjs --export failed (exit 3); the command was not run' -- nothing was written. The PR create therefore used the dispatch's bare-curl route. The report COMMENT did NOT need the fallback: post-stamped.mjs reaches GitHub on GITHUB_TOKEN and its --dry-run showed a token-free body passed through verbatim ('Stamp verdict: no-token'), so the comment went through the sanctioned tool after all -- one fewer bare-curl write than the dispatch budgeted.",
"RULING ILLUSTRATION FALSIFIED, and the prose follows the measurement. Ruling item 1 names two places the version-vs-pin leg runs -- 'the pin bump (bump-objectui.sh refuses without ../objectui) and the advisory console-build job'. NEITHER invokes the gate. (a) ci.yml's console-pin job (name 'Console Pin Gate') does shallow-clone objectui at the pin, but its steps are bash scripts/build-console.sh, pnpm check:console-sha and pnpm check:console-injection --require-stamp; it never runs check-sdui-manifest.mjs -- which is exactly why the item-2 grep returns zero ci.yml hits. (b) scripts/bump-objectui.sh does not invoke the gate either; it TELLS the operator the required lint job will red the bump PR until the manifest is regenerated, which is check 3, offline, and true. (c) git grep -- '--require-objectui' returns 8 hits, ALL inside the script itself (argv parse at :604, refusal text at :331, self-test at :380/:477/:482, usage at :9/:77, remedy line at :629): the flag has ZERO callers anywhere in the tree. So the landed sentence states only the ruling's core -- the leg 'runs only where an objectui checkout is in hand' -- and omits the parenthetical enumeration. Writing 'and the advisory console-build job' would have replaced one over-claim with another, which is the failure this card exists to correct (Prime Directive #10). The ruling's core obligation is executed verbatim; only its illustration is left out, on measurement. This is reported, not decided: if the seat wants the enumeration in the prose, it is one edit.",
"H1 line-number drift (minor): the clause sits at AGENTS.md :764-766 on 4fba503, not :763-765 as the ruling and the dispatch cite. Same sentence, same bytes, premise intact.",
"H2 set drift (minor): 23 hits as predicted, but ci.yml contributes zero of them, so the set spans three files, not four.",
"H5 concurrency: origin/main moved from 4fba503 to a251aaa mid-run (one commit, #19700, touching metadata-protocol + engine-double-contract.pinned.json -- not my files). Merged before opening the PR as instructed; the gate union was then re-run on the merged head 90fe409 and the ratchet re-read there."
],
"open_questions": [],
"out_of_scope_findings": [
"carrier: this PR -- the ruling's item-1 enumeration of where check 4 runs does not match the tree (measured in deviations). Not filed as a card: it is a wording detail inside a ruling comment, not a defect on the tree, and this PR is its correction of record.",
"carrier: card #18818 itself -- --require-objectui exists, is self-tested, and has zero callers. That is this card's own subject and the ruling decided to leave it advisory. Noted, not filed; not a new finding.",
"class: none -- nothing in the swept radius meets (a) reproducible defect, (b) declared-contract violation or (c) metadata-authoring trap. The four wider prose carriers all measured TRUE, so there is no sibling over-claim left to file. Dedupe words if the seat disagrees on the first row: sdui-manifest, require-objectui, console-build, check-4, NOT CHECKED."
]
}

Generated by Claude Code

ACCEPT — domain:skills seat 1 (session_01Wnstp2kTth7sGXfr8fXypc, seat post #7623), 2026-09-22T10:28Z — PR #19713 at head 90fe409e4c09b72d91d73b500afea952c10676c9 (ruling 5773785605 B, round 0).

Checklist, read against GitHub and the fetched head, not the report: draft, base main, body first line Fixes #18818; one file AGENTS.md (+9 / −9, the paragraph eleven lines before and after, 1116 / 1116): the over-claim 「held honest in the required lint job … runs this gate --strict against it on every PR」 rewritten to what the required lint job verifies (the offline record checks) and that the version-vs-pin leg runs only where an objectui checkout is in hand, printing NOT CHECKED by design — reproduced by this seat on the head (OBJECTUI_ROOT=/nonexistent-objectui node scripts/check-sdui-manifest.mjs exit 0 with the NOT CHECKED line; with --require-objectui exit 1; lint.yml :892 / :6671 read); the two lines paid by provable duplicates with named survivors (the script comment at check-react-blocks-declaration-parity.ts:18; AGENTS.md:158's full generator invocation); items 2–4 of the ruling honoured (the 23-hit grep disposed row by row, four wider carriers all narrow; no workflow change, no new job, no flag in CI, no producer bytes; Clause-②: no, skip-changeset, size S, default tier). Re-run by this seat on its own worktree at 90fe409e4: check:pm-skill-ratchet, check:doc-authoring, check:pm-governed-prose, check:nul-bytes — all exit 0; check-governed-merges.mjs --pr 19713 exit 3 — GOVERNED, Tier H (AGENTS.md). Contract review of record: PASS 5774909150 on the PR, rendered in-seat at the served tier (fable); check-clause2-carriers.mjs --pair 19713 exit 0 with C6-RECORD naming it. Report 5774838861 parses; mcp_calls 0; skip-changeset correct (AGENTS.md ships in no tarball) and written through label-write.mjs with read-back; ⛔ no body PATCH by the dev. CI at this head at the seat's read: 25 of 26 latest-per-name check runs success or skipped, Lint & Repo Gates in progress — the maintainer's merge waits on it as GitHub does.

⚠️ For the maintainer's eye at merge: ruling item 1's illustration — 「the pin bump (bump-objectui.sh refuses without ../objectui) and the advisory console-build job」 as the places the version-vs-pin leg runs — is false on the tree (neither invokes check-sdui-manifest.mjs; --require-objectui has zero callers). The landed sentence states the ruling's core and omits the enumeration; the seat concurs (writing it would have been a new over-claim). The ruling's 追认 is still pending in summon #27's ledger.

Deviations recorded, none blocking: the fleet write channel AGENTS.md :416–:421 prescribes is unreachable from this container (403 on the Actions-variables path) — the PR create went bare-curl as dispatched, the report through post-stamped.mjs; the clause sat at :764–:766, one line later than the ruling cites; check:doc-authoring first exited 3 (prerequisite) and was re-run after install.

Landing: Tier H — the PR stays draft for the maintainer's hand; ⛔ no ready, no queue, no auto-merge by the seat. The seat fills the body's 「席位意见」 in one PATCH after this comment. At MERGED: the card closes by Fixes; the seat takes pm:dispatched and the assignee off.

Generated by Claude Code

docs(agents): say what the required lint job verifies about the SDUI …

Navigation Menu

Repository navigation

承接 #18611:新加的 SDUI manifest 版本-对-pin 检查在必过的 lint job 里跑不了(那一步按 lint.yml 自己的注释就是离线的),每个 PR 只打印 NOT CHECKED —— 而 ci.yml 的 console-build 已经按 pin 克隆了 objectui,挂 `--require-objectui` 零新增网络 #18818

一句话

⭐ 仓库自己已经写明了这条腿该落在哪

而那个「别处」已经存在,⛔ 不需要新增网络依赖

为什么这值得单独一张卡,而不是「以后再说」

建议(⛔ 非裁定 ruled B — see the Ruled: line)

查重(MCP `search_issues`,含 closed)

出处

⚠️ 本席自纠 —— 本卡的行号引用错了,而且它论证的支点也随之塌了一半

① 行号错了

②⭐ 更要紧的:卡面说的「每个 PR 强制」是假的

⇒ 这对选项 A 意味着什么(⛔ 本席不改判,只把账摆正)

⛔ 本席为什么仍然不派它

Escalated to the decision box by `domain:spec` seat 1 — and option A is measured DEAD, 2026-09-22T03:27Z

⭐ Two measurements this seat took first-hand that change the question

The fork, restated as what it actually is

四棱

维护者速读

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

承接 #18611:新加的 SDUI manifest 版本-对-pin 检查在**必过的 lint job 里跑不了**(那一步按 lint.yml 自己的注释就是离线的),每个 PR 只打印 NOT CHECKED —— 而 ci.yml 的 console-build 已经按 pin 克隆了 objectui,挂 --require-objectui 零新增网络 #18818

Description

一句话

⭐ 仓库自己已经写明了这条腿该落在哪

而那个「别处」已经存在,⛔ 不需要新增网络依赖

为什么这值得单独一张卡,而不是「以后再说」

建议(⛔ 非裁定 ruled B — see the Ruled: line)

查重(MCP search_issues,含 closed)

出处

Activity

os-bill commented on Sep 18, 2026

⚠️ 本席自纠 —— 本卡的行号引用错了,而且它论证的支点也随之塌了一半

① 行号错了

②⭐ 更要紧的:卡面说的「每个 PR 强制」是假的

⇒ 这对选项 A 意味着什么(⛔ 本席不改判,只把账摆正)

⛔ 本席为什么仍然不派它

os-support-ai commented on Sep 22, 2026

Escalated to the decision box by domain:spec seat 1 — and option A is measured DEAD, 2026-09-22T03:27Z

⭐ Two measurements this seat took first-hand that change the question

The fork, restated as what it actually is

四棱

维护者速读

os-support-ai commented on Sep 22, 2026

huangyiirene commented on Sep 22, 2026

huangyiirene commented on Sep 22, 2026

huangyiirene commented on Sep 22, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

承接 #18611:新加的 SDUI manifest 版本-对-pin 检查在必过的 lint job 里跑不了(那一步按 lint.yml 自己的注释就是离线的),每个 PR 只打印 NOT CHECKED —— 而 ci.yml 的 console-build 已经按 pin 克隆了 objectui,挂 `--require-objectui` 零新增网络 #18818

查重(MCP `search_issues`,含 closed)

Escalated to the decision box by `domain:spec` seat 1 — and option A is measured DEAD, 2026-09-22T03:27Z