[marchtian]

Requested by 田騏 · project thread

Fixes #25430
Part of #25438
Clause-②: no
Metadata-protocol: none

This PR moves the console pin from 1d178e06ac5e (set by #25437) to 6fb31dcc9954. That is objectui main at 6fb31dcc9954844b2631ecfa96e999c4f73c4881, the merge of objectui#13370.

It does two things on the 18.1.0 path:

• hourly full run: red on main (CI) #25438: Console Pin Gate is red on main.
  • feat(spec,lint): a bulk action's confirmText is a template slot over count and its params, judged at validate, compile and the publish gate #24947 made a bulk action's confirmText a template slot. objectui typed the envelope's source as required, so @object-ui/plugin-view fails its declaration build at ObjectView.tsx:2615 against the current spec. It fails at every objectui commit before objectui#13370, including 1d178e06ac5e.
  • objectui#13370 types source as optional, as the spec's Expression does. At this pin, pnpm objectui:build on this branch builds the console with no local patch.
  • This PR is marked Part of hourly full run: red on main (CI) #25438, not Fixes. hourly full run: red on main (CI) #25438 is closed when Console Pin Gate goes green on main.
• chore(console): move the objectui pin 5fef032b1ada → objectui main, past objectui#13361 (closes objectui#7611), before the 18.1.0 cut; re-run F1 on it #25430. The new pin carries objectui#13361 (f2f4b7dc3, the [Direction · v18] Per-user scope for view personal configuration (parked from #7494) #7611 remainder: Publish from Home no longer reports a defineCapability declaration as unresolved). The epic [epic] ADR-0131 — total organization ownership: no NULL organization_id (v18 line) #15194 gate (c) re-test reads this change.

Branch history. The harness assigned the branch claude/project-thread-nldmem, and the card's Claim: names it. The branch first moved the pin from 5fef032b1ada. After #25437 landed its own move to 1d178e06ac5e, the branch merged main, took main's side of the three conflicted files, and re-ran the bump from there. The net diff against main is the four files below.

The diff

These are the same four files as in the earlier pin moves #25358 and #25262. The repo's own tooling wrote each one; none was edited by hand.

• .objectui-sha and .changeset/console-6fb31dcc9954.md: OBJECTUI_ROOT=/home/claude/objectui OBJECTUI_NO_DEEPEN=1 bash scripts/bump-objectui.sh 6fb31dcc9954844b2631ecfa96e999c4f73c4881 --no-commit exited 0. It printed "1d178e06ac5e..6fb31dcc9954 walks completely", "7 releasing changeset(s), 0 breaking" and "(on origin/main)".
• scripts/sdui-manifest.record.json: NODE_OPTIONS=--max-old-space-size=6144 pnpm objectui:build exited 0 with "dist ready … from objectui@6fb31dcc9954" and "Console bundle carries THIS tree's @objectstack/spec, and only it". Then node scripts/gen-sdui-manifest-node.mjs ran: 107 components, sha256 d1fde278ffd6…. sdui.manifest.json is byte-identical, so only its provenance record moves. node scripts/check-sdui-manifest.mjs passes.
• packages/sdui-parser/objectui-lockstep.json: OBJECTUI_ROOT=.cache/objectui-6fb31dcc9954 pnpm gen:sdui-lockstep recorded 214 region lines, blob 0131f27cf86d, and 25 diagnostic codes. pnpm check:sdui-lockstep passes. pnpm check:console-sha passes.

The changeset

scripts/objectui-changeset-digest.mjs derived it from the 7 changesets objectui added over 1d178e06ac5e..6fb31dcc9954, across 7 non-merge commits. #25437's console-1d178e06ac5e.md already covers the earlier part of the range, so the two do not overlap. Under ruling A (#25105), a console refresh is patch with Metadata-protocol: none.

Choosing the pin

6fb31dcc9954 is objectui origin/main's tip, and 1d178e06ac5e is its ancestor. objectui CI on 6fb31dcc9954:

• Push runs Lint 39968382243, Repo Gates 39968382372, Changeset Guard 39968382262, Changeset Release 39968382314 and Bundle Analysis 39968382271 succeeded.
• objectui#13370's own merge-queue run passed before it merged.

Verification on the built console

I ran the F1 re-test for #15194 gate (c) on this branch's console at this pin, before the merge with main. F1 is absent; the reading is on #15194 (comment 6367439307). The injection stamp carries a real witness (skew: true).

Out of scope

• No objectui source changed here.
• No product code, .github/workflows/**, scripts/build-console.sh or content/docs/releases/ is in the diff.
• This PR is not a release act and does not touch the Version Packages PR chore: version packages #24876.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CBtjEGZifSHGenaRcRBKYb

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

⚠️ 1 changed file(s) yielded no anchor (packages/sdui-parser/objectui-lockstep.json), so the pages documenting them are NOT COVERED by this run — this is not a clean bill of health for those files. Nothing else in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 1 changed package(s)).

What this run could not see

• 1 changed file(s) yielded no anchor (packages/sdui-parser/objectui-lockstep.json) — pages documenting those are invisible to this run
• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 3 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json ea33919f56a9879f95a00d45418385ff7dbb974f → packageMentionDocs.

[marchtian]

CI status on 574070ea:

• "The card this PR closes must claim this branch": the first run failed because the body said Fixes #25438, and that card has no Claim: for this branch. The body now reads Part of #25438, and the re-run passed.
• "No other open PR may claim the same single-writer path": still red, and it is not something this branch can fix. fix(spec): a dataset dimension's nullLabel is live; move the objectui pin past its reader #25437 opened first, claims .objectui-sha, and is armed for auto-merge. This check goes green once fix(spec): a dataset dimension's nullLabel is live; move the objectui pin past its reader #25437 merges. After that I'll merge main into this branch, re-run the bump over 1d178e06ac5e..6fb31dcc9954 so the two console changesets don't overlap, regenerate both records, push, and arm auto-merge once CI is green. No re-run now, because a re-run gives the same answer while fix(spec): a dataset dimension's nullLabel is live; move the objectui pin past its reader #25437 is open.

---

Generated by Claude Code