[objectstack-fleet]

Refs #24798
Clause-②: no
Metadata-protocol: none

This PR moves the console pin from 56cf4d8e89b7 to cd14d8eeffe1: objectui main at cd14d8eeffe11ae03b6acf82e663c1d293dfdf5f. That commit is the squash merge of objectstack-ai/objectui#13319, the objectui reader that takes a bulk action's confirmText either as a plain string or as a { dialect: 'template', source } envelope. It is also objectui main's tip.

Landing order

This is step 2 of the three-step landing order for #24947:

1. fix(plugin-grid,types): read bulk confirmText as a string or a template envelope objectui#13319 landed on objectui main as cd14d8eef.
2. This PR moves objectstack's objectui pin past it.
3. 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 lands on top of this pin.

#24798 stays open: this PR is only the pin step, and #24947 carries the rest.

This PR is not a release act. It does not touch the Version Packages PR and dispatches no workflow. No objectui source changed, nothing was written to objectui, and no product code, .github/workflows/**, scripts/build-console.sh or content/docs/releases/ is in the diff.

The diff

It follows the precedent pin move 06900c9 and changes the same four files. Each was written by the repo's own tooling; none was edited by hand.

• .objectui-sha and .changeset/console-cd14d8eeffe1.md: OBJECTUI_ROOT=/home/user/objectui OBJECTUI_NO_DEEPEN=1 bash scripts/bump-objectui.sh cd14d8eeffe11ae03b6acf82e663c1d293dfdf5f --no-commit, exit 0. The script printed "56cf4d8e89b7..cd14d8eeffe1 walks completely", "1 releasing changeset(s), 0 breaking", "(on origin/main)" and "wrote changeset console-cd14d8eeffe1.md (@objectstack/console: patch)".
• scripts/sdui-manifest.record.json: pnpm objectui:build (os-verify-lock VERDICT command-exit 0), then node scripts/gen-sdui-manifest-node.mjs, exit 0. It reports 107 components and sha256 d1fde278ffd6…, the same as at the old pin, so the tracked sdui.manifest.json is byte-identical and only its provenance record moves.
• packages/sdui-parser/objectui-lockstep.json: OBJECTUI_ROOT=.cache/objectui-cd14d8eeffe1 pnpm gen:sdui-lockstep, run against the build worktree whose HEAD is the pin. It reports "214 region line(s), blob 0131f27cf86d, 25 diagnostic code(s)". Only rev, revDate and recordedAgainstPin changed.

The changeset

scripts/objectui-changeset-digest.mjs derived it from the one objectui changeset added over the range:

• "@objectstack/console": patch. Under ruling A (changeset levels: minor only when the metadata protocol changes (added / narrowed / semantic), patch otherwise; release notes grouped by what the reader must do (maintainer ruling A, 2026-10-21) #25105, AGENTS.md "Definition of done" item 3), a console refresh is patch with Metadata-protocol: none, whatever level objectui declared. Here objectui itself declared patch, so nothing was downgraded.
• The changeset body carries the generator's line-initial Metadata-protocol: none line.

Choosing the pin

cd14d8eef is on objectui origin/main (git merge-base --is-ancestor exit 0) and is its tip. 56cf4d8e89b7 is its ancestor, and the range is one commit. objectui CI on cd14d8eef, read when this PR was opened:

• Merge-group runs, all success: CI 39746139602, Lint 39746140055, Repo Gates 39746139523, Changeset Presence 39746139710, Governed Surface Guard 39746139976.
• Push runs: Lint 39747613739, Repo Gates 39747613846, Changeset Guard 39747613768, Changeset Release 39747613759 and Bundle Analysis 39747613696 are success. Push CI 39747613641 was still in_progress.

Tier: not governed. node scripts/pm/check-governed-merges.mjs --branch claude/objectui-pin-cd14d8eef: "0 of 4 path(s) hit the register (7 surfaces govern objectstack) ... NOT governed", exit 0. Size: 4 files, +19 / -6.

Local verification at 0006f290fa

node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack derived 73 commands for this file list. I ran every one, and --ran with the exit codes recorded says: "73 derived famil(ies) accounted for — 72 run, 1 NOT-MEASURED (1 DERIVED from a recorded exit 3)". 72 exited 0. Verdict lines from the pin-bump gates:

• check-sdui-manifest: "sdui.manifest.json is present, intact (sha256 d1fde278ffd6…, 107 components) and recorded at the live objectui pin cd14d8eeffe1…".
• check:console-sha: "Console dist matches the objectui pin (objectui@cd14d8eeffe1)."
• check:sdui-lockstep: "OK — this copy is byte-identical to objectui@cd14d8eeffe1 ... over 214 grammar line(s) ... agrees on all 25 diagnostic code(s)".
• check:objectui-changeset, check:console-injection, check:published-files, check-empty-changeset --base origin/main and check-adr-0087-registration --base origin/main: all green ("adds no declared-breaking changeset (1 non-breaking changeset(s) seen)").
• check:nul-bytes: "OK (scanned 11769 text file(s) ... no raw ASCII control bytes)".
• check-changeset-no-major --base origin/main --event with this body as the pull_request payload: exit 0. It reported "This diff introduces no major bump" and "LEVEL AXIS: this PR declares clause-② no and metadata-protocol none, and it introduces no changeset entry graded minor or above".

NOT MEASURED: check:dual-build-cjs-loads, reason: "PREREQUISITE NOT MET — this gate reads built output, and some package has no dist/" (exit 3). It needs a whole-tree pnpm build. This diff touches no package source, so the run is left to CI.

---

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 2069b81c266836fd6d7b52fc5e6679c734bdcd3c → packageMentionDocs.

[objectstack-fleet]

Seat review — PASS · domain:spec seat 3

Head: 0006f290fa85bfa09655f939d920249979c7b621. Step 2 of the landing order for #24947 (card #24798). Dev report 6336780101.

• Contract review: none owed. The diff is the pin-bump shape of precedent 06900c9c23: .objectui-sha, packages/sdui-parser/objectui-lockstep.json, scripts/sdui-manifest.record.json and .changeset/console-cd14d8eeffe1.md. It touches no package source and no governed path (check-governed-merges: NOT governed). It declares Clause-②: no and Metadata-protocol: none.
• Range: 56cf4d8e89b7 → cd14d8eeffe1 is one objectui commit, the squash of objectui#13319 (the bulk confirmText envelope reader). Its patch-id equals that PR's reviewed head.
• Tooling, not hand edits:
  • bump-objectui.sh wrote the pin and the patch console changeset with Metadata-protocol: none;
  • objectui:build plus gen-sdui-manifest-node.mjs rewrote the manifest record, and sdui.manifest.json is byte-identical (107 components);
  • gen:sdui-lockstep rewrote the lockstep, and check:sdui-lockstep is byte-identical to the pin over 214 grammar lines.
• objectui CI on cd14d8eef: merge-group CI is green. The one red is the housekeeping job "Snapshot the board to the archive branch", not a code check. The coverage shards were still running at review time.

Seat re-read of the check-runs at landing: all 41 runs on 0006f290fa have completed: 34 succeeded, the rest were skipped, and none is red.