[objectstack-fleet]

Requested by Elon · project thread

Fixes #25353
Clause-②: no
Metadata-protocol: none

This PR moves the console pin from 0d12e95361b2 to 5fef032b1ada: objectui main at 5fef032b1ada5b86bad640637e7331e26ee5da6e, its tip when this PR was opened. It is the pin move the maintainer's 18.1.0 ruling puts before the release cut ("卡 5 同意", 5a-B): move the pin first, then cut 18.1.0. With it, the 18.1.0 console carries objectui#13323: a navigation entry's API dataSource and a page element bound to the same read make one request per console open instead of two.

Branch name: the harness assigned claude/project-thread-wyb8o7, not the repo's claude/issue-25353-… convention; the card's Claim: names this branch. No other open PR moves .objectui-sha.

The diff

The same four files as the precedent pin moves #25262 and #25193. The repo's own tooling wrote each one; none was edited by hand.

• .objectui-sha and .changeset/console-5fef032b1ada.md: OBJECTUI_ROOT=/home/claude/objectui OBJECTUI_NO_DEEPEN=1 bash scripts/bump-objectui.sh 5fef032b1ada5b86bad640637e7331e26ee5da6e --no-commit, exit 0. It printed "0d12e95361b2..5fef032b1ada walks completely", "1 releasing changeset(s), 0 breaking", "objectui declared minor, recorded as patch" and "(on origin/main)".
• scripts/sdui-manifest.record.json: pnpm objectui:build, then node scripts/gen-sdui-manifest-node.mjs, exit 0. It reported 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. node scripts/check-sdui-manifest.mjs passes at the new pin.
• packages/sdui-parser/objectui-lockstep.json: OBJECTUI_ROOT=.cache/objectui-5fef032b1ada pnpm gen:sdui-lockstep. It reported "214 region line(s), blob 0131f27cf86d, 25 diagnostic code(s)". Only rev, revDate and recordedAgainstPin changed, and pnpm check:sdui-lockstep passes.

One build note: the first pnpm objectui:build in this container died with JavaScript heap out of memory in @object-ui/app-shell's tsc (node's default heap, 2 GB). It was re-run with NODE_OPTIONS=--max-old-space-size=6144 and finished with "dist ready … from objectui@5fef032b1ada"; the manifest was regenerated from that complete build.

The changeset

scripts/objectui-changeset-digest.mjs derived it from the changesets objectui added over the range. Under ruling A (#25105) a console refresh is patch with Metadata-protocol: none, whatever objectui declared. objectui declared minor here (the new ElementApiOpenScope / useElementApiOpen exports of @object-ui/react), and the digest recorded patch.

The range holds two non-merge objectui commits: objectui#13328 (b911ebb4e, the objectui#13323 fix) and objectui#13329 (5fef032b1, a CI gate fix that carries a release-nothing changeset).

Choosing the pin

5fef032b1ada is objectui origin/main's tip, and 0d12e95361b2 is its ancestor. objectui CI on 5fef032b1ada, read when this PR was opened:

• Push runs Lint 39840220823, Repo Gates 39840220731, Changeset Guard 39840220743 and Changeset Release 39840220678: success.
• Push CI 39840220761: failure, on its Test aggregation job alone. All 16 test shards concluded success; the gate read shard 15/16 (job 120038970141, completed success at 19:35:14Z) as still in_progress from the jobs API for its whole re-read window (19:39–19:45Z) and refused. That stale-read class is exactly what objectui#13329, the commit pinned here, fixes.
• Scheduled CI on the same sha, after that run: 39872395655, 39881943452 and 39885608893, all success.

Spot-check of objectui#13323 on the built console

Verdict: PASS. One GET per console open for a nav entry and a page element bound to the same read, and the element draws that answer.

Setup: this branch at 67d8b675, framework built (pnpm build --concurrency=2, 76/76 tasks), console built at the pin (packages/console/dist/.objectui-sha = 5fef032b1ada5b86bad640637e7331e26ee5da6e). Stock examples/app-showcase booted with pnpm dev -- --fresh -p 38517 and signed in as the seeded admin; headless Chromium (Playwright 1.63) drove it and counted every request to the probe URL. The showcase declares no API-bound nav entry, so a throwaway fixture added two lines to the working tree for the run and was restored afterwards (git status clean, nothing committed):

• nav entry nav_probe_13323, first in showcase_app's navigation: type: 'page', pageName: 'showcase_contact_form', visible: 'data.total >= 0', dataSource: { provider: 'api', read: { url: '/api/v1/data/showcase_inquiry' } };
• on showcase_contact_form, an element:text with the same dataSource and content PROBE total=${data.total}.

step	URL after	GET /api/v1/data/showcase_inquiry	element shows	nav entry
A. open /_console/apps/showcase_app (the landing replaces onto the probe page)	…/page/showcase_contact_form	1	PROBE total=3	drawn
B. fresh load straight onto the probe page	…/page/showcase_contact_form	1	PROBE total=3	drawn
C. PUSH to Capability Map through the nav	…/page/showcase_capability_map	0	n/a	drawn
D. Back to the probe page (POP, a new open)	…/page/showcase_contact_form	1	PROBE total=3	drawn

The nav gate needs the read to draw the entry and the element needs it to draw 3; both drew on one request in A, B and D, so the element took the answer the nav read already held. D reads again, as objectui#13323 specifies for a POP. Not run here: a control at the old pin (the two-request baseline), which objectui#13328's own ablations cover.

Out of scope

• No objectui source changed here, and nothing was written to objectui.
• 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, which the release seat refreshes after this lands.

🤖 Generated with Claude Code

https://claude.ai/code/session_01RVrmCeThcAT38hSxtChLz4

---

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 69913f8ba32d409ec67fe16cc81321dbf2807781 → packageMentionDocs.