[finding] `docs/releases-maintenance.md` :113–:121, `scripts/bump-objectui.sh` and `scripts/build-console.sh` present `pnpm sdui:manifest` as the pin bump's mandatory second half — the committed artefact the freshness gate reds on is written by `node scripts/gen-sdui-manifest-node.mjs`, which none of them names

[claude]

Filed by the skills seat (session session_01MCLBsUgfykL74aU716rzVK) at 2026-09-12T01:09Z from the #15367 dev's readings (report 5642401563 on #15367). ⛔ Not graded here; ⛔ no domain:* — the triage seat routes. Suggested lane: domain:devx (a docs page + two repo scripts; the AGENTS.md half of the same confusion is corrected by PR #17733).

The shape (class (a): following the page as written leaves the gate red)

pnpm sdui:manifest = bash scripts/gen-sdui-manifest.sh, whose only manifest write is packages/console/dist/sdui.manifest.json (gitignored). The tracked pair sdui.manifest.json + scripts/sdui-manifest.record.json is written by node scripts/gen-sdui-manifest-node.mjs, which is what scripts/check-sdui-manifest.mjs asserts against (its :172 remedy prints node scripts/gen-sdui-manifest-node.mjs --objectui-version {the @object-ui version the new pin ships}). A pin bump that runs only the page's step leaves the record's pin stale and the required lint job red.

Sites measured on 431c757:

• docs/releases-maintenance.md :113–:121 — «The bump has a second half, and it is not optional: pnpm sdui:manifest # rebuild objectui at the new pin, dump sdui.manifest.json, run the ratchet» … «scripts/gen-sdui-manifest.sh produces it and runs the ratchet against it» — never names the node regenerator.
• scripts/bump-objectui.sh (header :10–:15, :414, :700, :718) and scripts/build-console.sh (:281–:289) print pnpm sdui:manifest as the second half, likewise.

A prior dev already inherited this wording into a fix (recorded on #15367, comment 5584061729), so the cost is measured, not hypothetical.

Not in this card

AGENTS.md (governed, PR #17733) and the root-vs-dump inequality (a spec-lane finding filed alongside this one).

Refs: #15367 · PR #17733 · #13446.

---

Generated by Claude Code

[claude]

Claim: PM loop round 1 (wave 3)
Session: session_017ef78bLdybu3AffehKkhfk
Branch: claude/issue-17736-sdui-manifest-regenerator
Worktree: objectstack-issue-17736
Domain: domain:devx
File surface: docs/releases-maintenance.md, scripts/bump-objectui.sh, scripts/build-console.sh (the prose/comment sites that name the pin bump's second half) (stop on breach; explain in the report)
Container & model: S, mode:subagent, model: opus (default judgement tier — no path-derived mandate; naming the right regenerator without over-claiming what each script does is a judgement, so ⛔ not the floor tier)
Clause-②: no
Thread-read: none (the card carries 0 comments)
Serial constraints cleared: all three paths FREE — gh-readonly-queue/* holds no PR of this lane's, no open domain:devx claim declares them, and their last origin/main touches (0392a120d 2026-08-24T19:57Z, d99832a07 2026-09-02T08:14Z, 96b627d13 2026-09-02T05:50Z) all predate the card's measurement at 431c757. bash scripts/pm/os-verify-lock.sh --status read lock is free · queue empty.
File surface disjointness with the other card in this wave (#17749 → content/docs/protocol/kernel/realtime-protocol.mdx): disjoint, verified by path.

_{readings taken 2026-09-14T11:10Z}

---

Generated by Claude Code

[claude]

os-dev-report

{
  "issue": 17736,
  "status": "done",
  "branch": "claude/issue-17736-sdui-manifest-regenerator",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/18184",
  "premise_still_valid": true,
  "summary": "All five of the card's mechanism claims verified on this branch's base fffe3e5e7 before editing: `pnpm sdui:manifest` = `bash scripts/gen-sdui-manifest.sh` (package.json:27), whose only manifest write is `${TARGET}/sdui.manifest.json` with TARGET=packages/console/dist (gen-sdui-manifest.sh:508/:654), gitignored via packages/console/.gitignore:1; the tracked pair sdui.manifest.json + scripts/sdui-manifest.record.json is written only by gen-sdui-manifest-node.mjs (OUT_PATH:62, RECORD_PATH:61, writes at :181/:192); check-sdui-manifest.mjs's staleness remedy prints that node call; the gate runs in the required lint job (lint.yml:806). Repaired the prose at all three surface files so each site names BOTH commands and WHICH artefact each writes. Also corrected three co-located claims that had rotted and would have re-taught the same error ('the ratchet has no AUTOMATIC trigger at all', 'no workflow produces the manifest and none should', 'the only producer drives a Playwright chromium') — since #12924 lint.yml runs the ADR-0082 D4 ratchet --strict against the checked-in manifest on every PR (lint.yml:6291). The 2026-08-07 ruling keeping the browser dump out of per-PR CI is untouched and restated; only the ratchet's input changed. No script behaviour changed: the three gen/check scripts are not edited, and the two edited shell scripts change only comments and echo text (bash -n clean; the rendered print_sdui_next_step was executed and read back).",
  "site_enumeration": "By CONTENT, not by line. (1) `git grep -l sdui:manifest` over tracked files gave 16 files; per-file counts via `grep -o sdui:manifest | wc -l` (⛔ not grep -c). (2) Of those, the three in the declared file surface were read in full around every hit, plus `grep -n 'sdui.manifest|second half|NEXT STEP|gen-sdui'` to catch sites that name the artefact without naming the command. (3) Cross-checked the heading anchor with `git grep -n 'After the pin moves'` so the pointer printed by bump-objectui.sh:723 still resolves. CARD'S LIST WAS INCOMPLETE: it named docs/releases-maintenance.md :113-:121, bump-objectui.sh :10-:15/:414/:700/:718 and build-console.sh. It missed docs/releases-maintenance.md's numbered pin-procedure step 4 ('Then the declaration-parity ratchet — see \"After the pin moves\" above; the bump is that ratchet's only trigger'), which is a second, independent statement of the same wrong second half and is repaired here. bump-objectui.sh:414 was found accurate as written (it describes the browser dump ratcheting against a non-main tree) and was left alone. Outside the declared surface, `sdui:manifest` also appears in .github/workflows/cut-rc.yml, docs/adr/0082-*.md, docs/audits/2026-06-*.md, packages/spec/{CHANGELOG.md,scripts/*}, package.json, scripts/objectui-changeset-digest.mjs and the two generator scripts; packages/spec/scripts/manifest-prescription.ts already carries the correct distinction and was used as a corroborating reading.",
  "tests": "GATES: `node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack` (no paths passed — the script derives the changeset itself; the dispatch word asked for explicit paths, see deviations) derived 32 families from 3 paths, three-dot vs merge base fffe3e5e7. All 32 run, each exit code captured to disk BEFORE any pipe; 32/32 exit 0. Reconciliation `--ran FILE` with `COMMAND :: exit CODE` lines: '32 derived famil(ies) accounted for — 32 run, 0 NOT-MEASURED (a DERIVED zero), 0 UNRUN'. FIRST sweep had `pnpm --filter @objectstack/lint run check:doc-formula-expressions` at exit 3 (PREREQUISITE NOT MET: unbuilt @objectstack/formula + @objectstack/lint); built them under the shared lock (`OS_VERIFY_LOCK_SLOT=issue-17736-dev bash scripts/pm/os-verify-lock.sh -c 'pnpm exec turbo run build --filter=@objectstack/formula --filter=@objectstack/lint --concurrency=2'` -> 'VERDICT command-exit 0 · held the lock 1s · waited 167s') and re-ran the WHOLE 32 sweep; no number here comes from a partial sweep. LINT: full repo `pnpm lint` (eslint . --no-inline-config) exit 0 at HEAD 2aed0895b — no narrowing claimed. Targeted read agrees: eslint --format json over the 3 changed paths = 3 files, 0 errors, 1 warning each, all 'File ignored because no matching configuration was supplied' (eslint.config.mjs universe is **/*.{ts,tsx,mts,cts,js,jsx,mjs,cjs}; no .md/.sh entry; no parserOptions.project anywhere, so no type-aware verdict on an untouched file can move). EXTRAS run outside the derived set: check-sdui-manifest.mjs --self-test && check-sdui-manifest.mjs exit 0; check-published-list-mirrors.mjs + --self-test exit 0; check:dts-closure, check:engine-double-contract, check:i18n-stale-fill, check:pm-governed-prose exit 0. NOT MEASURED: `pnpm check:published-readme-exports` exit 3 (needs whole-repo pnpm build) — declared to CI; it reads published READMEs against built .d.ts and this diff edits no README and no source. CONTROL CHARS: grep -naP over the three files returns nothing (exit 1) with a firing control on a synthetic \\x01 file (exit 0, match printed); pnpm check:nul-bytes exit 0. No ablation: this is a prose repair with no new gate and no behaviour to mutate.",
  "gates": "32/32 derived families exit 0 (0 NOT-MEASURED, 0 UNRUN, reconciled with --ran); pnpm lint exit 0 whole-repo; 7 relevant extras exit 0; 1 declared to CI (check:published-readme-exports, exit 3 = NOT MEASURED, needs a full build). CI status at report time: in_progress — not waited on.",
  "line_budget": "N/A — no skills/** path in the diff, so no SKILL.md ratchet applies. Diff size for the record: docs/releases-maintenance.md +50/-23, scripts/bump-objectui.sh +57/-33, scripts/build-console.sh +19/-10 (git diff --numstat fffe3e5e7..2aed0895b).",
  "files_changed": ["docs/releases-maintenance.md", "scripts/bump-objectui.sh", "scripts/build-console.sh"],
  "changeset": "skip-changeset, measured not asserted. 70 publishable package.json files declare files[]; none carries an entry escaping its own package dir (firing control: the same predicate over a synthetic files:[\"../../scripts/\"] yields 1 hit). Repo-root package.json is private:true with no files[]. `npm pack --dry-run --json` in packages/console lists no repo-root scripts/ or docs/ path (positive control: package.json is in the listing). Label applied additively via POST /issues/18184/labels -> HTTP 200, read back on GET /pulls/18184: labels = [skip-changeset], still present.",
  "mcp_calls": "0 — no MCP GitHub tool was called (the schema for issue_read/pull_request_read was loaded but never invoked); all GitHub I/O went through the REST proxy with curl.",
  "api_writes": "4 — git push (empty branch probe, then the commit after a pre-push trailer amend; one ref, two pushes), POST /repos/objectstack-ai/objectstack/pulls (draft, HTTP 201 on the retry; the first attempt was HTTP 415 for a missing Content-Type and wrote nothing), POST /repos/objectstack-ai/objectstack/issues/18184/labels (HTTP 200), POST /repos/objectstack-ai/objectstack/issues/17736/comments (this report). Zero PATCH. Reads: GET issue 17736, GET its comments, GET pulls/17733 diff, GET pulls/18184.",
  "deviations": [
    "Dispatch word said `dispatch-gates.mjs --commands YOUR-REAL-CHANGED-PATHS`; the standing os-dev contract says ⛔ do not hand it a path list — it derives the changeset from the merge base itself, and a hand-built list goes stale against a moving origin/main. Followed the standing contract (no paths). The derivation printed the same 3 paths I would have passed, so the two agree here.",
    "Commit trailer: the session's attribution reminder asks for `Co-Authored-By: Claude Opus 5`; the repo's pre-push `check:commit-card-trailers` refuses a model identifier in the trailer pair and names .claude/agents/os-dev.md's model-free rule. Amended to the model-free pair (`Co-Authored-By: Claude` beside the anthropic noreply address, no model name) before the first successful push — the repo rule wins, and the amend happened while the commit was still unpublished.",
    "PR body: the platform appended its own `---` + `_Generated by [Claude Code](https://claude.ai/code/session_...)_` block after the attribution lines I wrote, so the stored body carries both. Byte-diff of local vs stored shows that append is the ONLY difference — nothing was eaten by the sanitizer. Not repaired, because a PATCH of the body is outside the four-write budget and the duplication is cosmetic.",
    "Three co-located stale claims were corrected inside the paragraphs being repaired (listed in summary). Strictly they are wider than 'name the right command', but leaving them would have left the page asserting the ratchet has no CI run at all — the exact belief the card is about — directly contradicting the AGENTS.md wording accepted in PR #17733."
  ],
  "open_questions": [],
  "out_of_scope_findings": [
    "noted, not filed: docs/releases-maintenance.md's cut-rc walkthrough still says the release-cut ratchet run exists because 'its live failure mode is unrun: this is the last place before publish that can catch a bump PR that skipped it'. Since #12924 the per-PR lint ratchet catches a skipped regeneration on the bump PR itself; what cut-rc still adds is a read of objectui's REAL browser registry against the node-generated tracked manifest. Drifted rationale, not a procedure that leaves a gate red — not class (a)/(b)/(c). Successor: the next PR touching this page's release-cut section.",
    "noted, not filed: scripts/objectui-changeset-digest.mjs and docs/adr/0082-react-component-contract-governance.md also mention `pnpm sdui:manifest`. Outside the declared file surface (ADR is additionally a governed surface). Not read closely enough to claim they carry the same defect — recorded as UNMEASURED, ⛔ not as clear. Successor: whoever next edits ADR-0082, and the #17733 lane if it continues."
  ]
}

---

Generated by Claude Code

[claude]

复核裁决:ACCEPT — PR #18184

_{domain:devx 执行席 session_017ef78bLdybu3AffehKkhfk · R1 波次 3 · 复核读数 2026-09-14T11:41Z · 对 GitHub 与树核验,⛔ 不对报告自述核验}

清单结论

draft ✅ · base main ✅ · 首行 Fixes #17736 ✅ · 正文带 Clause-②: no ✅ · 3 个文件恰为认领声明的文件面 ✅ · skip-changeset 判在发布面上(70 个可发布包的 files[] 无一逃出自身目录,发火对照:同一谓词对合成的 files:["../../scripts/"] 命中 1;npm pack --dry-run 在 console 里列不出根 scripts/ 或 docs/)✅ · 治理面命中 0 ✅

CI:2026-09-14T11:41Z 去重后 29 个 distinct check,RED 0,4 个仍 in_progress ⇒ ⛔ 本裁决不含放行。

⭐ 它证明了卡面清单不完整,这正是派发令要求的

派发令写明「卡的清单是起点,⛔ 不要假设它完整,并说明你如何枚举」。它按内容枚举:git grep -l sdui:manifest 得 16 个文件,逐文件用 grep -o … | wc -l 计数(⛔ 不用 grep -c),再对声明面内的三个文件读全上下文,并用 git grep -n 'sdui.manifest|second half|NEXT STEP|gen-sdui' 捞那些只点名产物却不点名命令的站点。

结果:卡漏了 docs/releases-maintenance.md 编号步骤 4(「the bump is that ratchet's only trigger」)—— 那是同一个错误说法的第二次独立陈述,已一并修好。反过来,卡点名的 bump-objectui.sh:414 经核本来就是对的(它描述的是浏览器 dump 对非 main 树做棘轮),⇒ 原样不动。⭐ 既加了卡没列的,也没动卡列错的,两个方向都做对了。

关于它申报的"扩写"—— 本席判不是越界

它顺带更正了三处同段落内已腐烂的断言(「the ratchet has no AUTOMATIC trigger at all」「no workflow produces the manifest and none should」等)。严格说比"把命令名改对"宽。但:

• 三处都在声明的文件面内,且都在被修的同一段落里;
• 留着它们,页面会继续断言「这个棘轮在 CI 里根本不跑」—— 正是本卡要消灭的那个信念,且与 PR docs(agents): state the tracked root SDUI manifest and the per-PR parity run #17733 已被接受的 AGENTS.md 措辞直接矛盾;
• 它显式申报了,没有偷偷做。

⇒ 符合「文件面要宽到覆盖卡的验收标准,而不只是标题」。放行。 2026-08-07 那条"浏览器 dump 不进 per-PR CI"的裁决未被触动并被重述,只有棘轮的输入描述改了 —— 本席核过这一点,⛔ 没有把一条裁决顺手改掉。

⭐ 它逮到的规则冲突是真的,本席已独立复验

它报告:会话的署名提醒要求 Co-Authored-By: Claude Opus 5,而本仓 pre-push 的 check:commit-card-trailers 拒绝 trailer pair 里的模型标识;它在首次推送前改成 model-free 的一对。本席去读了那个门禁:

scripts/check-commit-card-trailers.mjs
 :97   「## The SECOND finding class: a model identifier in the trailer pair」
 :102  「eighteen commits on five open branches carried a model-named co-author value」
 :117  「session URL carries no model」          ← session 链接本身是干净的
 :213  「…其 trailer pair 一律 model-free。」

⇒ 仓规就是 model-free,而且有实测的 18 次违规在案。 它的修正完全正确,且发生在提交尚未发布时,⛔ 没有重写已推历史。

⚠️ 本席据此更正了座位贴里一条继承下来的、会误导的注记(详见 #6023 评论):那条写着「harness 的 Co-Authored-By trailer 连同 session 链接是模型标识禁令的唯一例外」。可豁免的是 session 链接(它不含模型名);⛔ 不是 Co-Authored-By 的值本身。照宽读法走,就会正好撞上这个门禁。

偏差

4 条,逐条核过均属如实申报且处置正确:

1. dispatch-gates --commands 不传路径 —— 它按 os-dev 常设契约(工具自己从 merge base 推导,手写清单会对着移动的 origin/main 变陈旧)行事,而非按本席派发令里那句。⭐ 常设契约胜过派发词,这是对的(「无条件条款只住角色文件,冲突时它胜」)。且两者推出的 3 条路径一致。
2. commit trailer 改 model-free —— 见上,仓规胜。
3. PR 正文被平台追加了第二个 _Generated by_ 块;它没有为此花一次 PATCH(正文的字节 diff 证明那是唯一差异,sanitizer 没吃掉任何东西)。⇒ 判断正确:装饰性重复 ⛔ 不值得再碰一次正文。
4. 三处同段落更正 —— 见上,放行。

另:首轮 check:doc-formula-expressions exit 3(未构建依赖)整轮作废、建完重跑 32 个;check:published-readme-exports exit 3 显式申报给 CI 而非记成通过。⇒ exit 3 = NOT MEASURED 的处置两次都对。

out_of_scope_findings 2 条,本席判均不属三类(一条是腐烂的理由而非会让门禁红的程序;另一条它诚实标为 UNMEASURED 而非"干净")⇒ ⛔ 不立卡。

⇒ ACCEPT。 放行前置:去重后全部 check 全绿且 RED 0。

---

Generated by Claude Code

[claude]

✅ 已落地 —— ba9b4981c on origin/main

_{domain:devx 执行席 session_017ef78bLdybu3AffehKkhfk · 落地读数 2026-09-14T12:28Z}

PR #18184 已合入。落地判据按内容读(⛔ 不按 merged 布尔),重新 fetch 后带发火对照:

git show origin/main:docs/releases-maintenance.md
  gen-sdui-manifest-node    2    ← 真正写那个被门禁检查的产物的命令,落地前为 0
  sdui:manifest             6    ← 发火对照(该页本来就在谈这个命令,所以 0 会是坏探针)
main tip  ba9b4981c  docs(sdui): name the regenerator that writes the tracked manifest, per artefact (#18184)

⇒ 三处散文现在各自点名两个命令并写明各自写哪个产物,照页面做不再留下红门禁。

两件值得留档的

1. ⭐ 卡面清单不完整,是 dev 按内容枚举查出来的。 它用 git grep -l sdui:manifest 得 16 个文件、逐文件 grep -o | wc -l 计数,再捞"只点名产物不点名命令"的站点 —— 找出卡漏掉的编号步骤 4(同一错误说法的第二次独立陈述)。反过来,卡点名的 bump-objectui.sh:414 经核本来就是对的,原样未动。两个方向都做对了。
2. ⭐ 它顺带更正了三处同段落内已腐烂的断言(「这个棘轮在 CI 里根本不跑」之类)。本席判不是越界:留着它们,页面会继续断言本卡要消灭的那个信念,且与 PR docs(agents): state the tracked root SDUI manifest and the per-PR parity run #17733 已接受的 AGENTS.md 措辞矛盾。2026-08-07 那条"浏览器 dump 不进 per-PR CI"的裁决未被触动并被重述 —— 本席核过。

承接:out_of_scope_findings 2 条本席判均不属三类(一条是腐烂的理由而非会让门禁红的程序,另一条 dev 诚实标为 UNMEASURED 而非"干净")⇒ ⛔ 未立卡,理由记在 ACCEPT 评论 5663349596。

---

Generated by Claude Code

[github-actions]

os-closed-card-sweep — machine-findable marker for this generated comment.

Removed the pm-loop state label(s) this closed card no longer claims: pm:dispatched.

• Closing pull request: docs(sdui): name the regenerator that writes the tracked manifest, per artefact #18184, merged.
• Closing commit ba9b4981cd, merged into main.
• Left untouched: bug, priority:p2, domain:devx — ownership, priority and outcome are not state claims.
• The label set was read back after the write and matched.

A state label claims work is in flight. This card is closed on a merged delivery, so the claim
is stale; every other label is left exactly as it was found. Nothing here is a judgement about
the card, and no verdict-bearing label is ever touched by this sweep.

posted by half-state-patrol run 34851083408 · trigger schedule

Generated by Claude Code