chore: bump objectui to 6314e87f2d49

[huangyiirene]

Fixes #7411

Moves the console pin from 92c0b1f403f7e3323d25d9643c14572b87dab2a8 to objectui main at 6314e87f2d49b1ff3b158c296f1b2a52d14dff68 — 43 objectui commits. The whole regen went through scripts/bump-objectui.sh (pin + the derived @objectstack/console changeset); nothing was hand-edited except the ADR-0087 disposition the generator deliberately leaves unanswered.

Readings, re-derived at work time (2026-08-11 ~04:55Z)

	before	after
.objectui-sha on origin/main	92c0b1f403f7	6314e87f2d49
objectui origin/main	6314e87f2d49 (fix(detail): inline-edit an address as sub-fields… #4222, 2026-08-11T04:17Z)	—
gap	43 commits	0 — check:objectui-pin-fresh reports FRESH

The card's named payload (objectui#4108 / the objectui#4096 row-action permission gate) was already covered by the pin at dispatch time, as the PM's claim comment recorded — so the premise is the staleness half, which held: 43 commits, 27 releasing changesets, one of them breaking.

What is in the range

The generated changeset lists all 27 declared entries plus the 14 commits objectui shipped with no changeset. User-facing highlights: address inline-edit and detail-page rendering (objectui#4222 / #4215), image maxSize enforced before upload (#4217), draft-view rename persistence (#4212), the filter-panel view overlay (#4214), gantt refusal messages and dialog counts (#4210 / #4205), the action-renderer forward-whitelist gate (#4207), requiredWhen at submit time (#4201), and the global_nav designer retirement (#4169).

ADR-0087 disposition

The one declared-breaking entry is objectui#4169 — the Studio designer surfaces for the global_nav action location. The spec-side retirement of that enum value landed here with #7100 / #6888 and is already on the ledger as the conversion action-global-nav-location-removed, so this bump registers nothing new and the changeset carries not-required (already-registered action-global-nav-location-removed).

objectui#4169 was flagged at dispatch as a place where the console build might surface errors. It did not: the console built clean at the new pin and the declaration-parity ratchet found no new divergence.

Verification

All run locally in the worktree, on the pushed commit:

• scripts/build-console.sh (via OBJECTUI_ROOT=…) — console SPA rebuilt at the new pin; bundle canary import/jobs present; dist 51,964 KB. Preceded by pnpm --filter '@objectstack/client^...' build (the client dist the console bundles).
• pnpm check:console-sha — ✓ Console dist matches the objectui pin (objectui@6314e87f2d49); packages/console/dist/.objectui-sha equals .objectui-sha.
• pnpm check:objectui-pin-fresh — ✓ self-test + objectui pin is FRESH — .objectui-sha is objectui main.
• node scripts/check-adr-0087-registration.mjs --base origin/main — ✓ 1 declared-breaking changeset, disposition accepted as not-required (already-registered).
• pnpm check:empty-changeset, node scripts/check-changeset-no-major.mjs --base origin/main, pnpm check:objectui-changeset — ✓ all green.
• pnpm sdui:manifest (ADR-0082 D4 ratchet, the bump script's named next step) — ✓ manifest dumped, no new DECLARATION divergence vs accepted baseline (62 spec-only divergences, all pre-existing baseline stock). Needed the documented chromium_headless_shell-1194 → 1234 symlink shim from docs/releases-maintenance.md; the note is accurate as written and worked unmodified.
• node scripts/check-nul-bytes.mjs — ✓ 7001 files, no control bytes.

Scope

Diff is .objectui-sha + .changeset/console-6314e87f2d49.md — the same two-file shape as the previous bump 24d22f4. packages/console/dist is gitignored and rebuilt locally, so it is verified but not committed; pnpm-lock.yaml was not regenerated because this bump changes no framework dependency. No riders.

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
objectstack	Ignored		Aug 11, 2026 5:09am