chore: pin the console to objectui main 8aad9fd50b16 (approvals inbox + bell-badge breakdown)

[os-zhuang]

Fixes #7268

Moves the console pin from 09987b680d53 to 8aad9fd50b16 — objectui origin/main HEAD at run time, per the maintainer directive of 2026-08-10 (chat), verbatim: 「直接 pin 到最新」. The target was not narrowed to the two #7213-train PRs the card was filed for.

What the range actually carries

09987b680d53...8aad9fd50b16 — 67 non-merge commits, of which:

releasing changesets objectui declared	61
declared major	0
annotated breaking (shipped as minor per objectui's launch-window ban on major)	1
release-nothing changesets	0
commits carrying no changeset at all	6

Resolved bump level: minor for @objectstack/console. CONSOLE_BUMP was not set — the level is what objectui-changeset-digest.mjs derived from the highest level objectui itself declared over the range (#4731). It did not come out major: the single breaking change is an author annotation in a minor changeset, not a declared major, and that distinction is reported by the generator rather than inferred here.

The one breaking entry, for the release record

objectui 65bb513dc — "fields: remove the docs-demo registration path (registerFields + createFieldRenderer), and host the docs field examples in a real form" (objectui#3910 / #3953, ruling B of objectui#3798). It removes two public TypeScript exports from the @object-ui/fields npm package; the only caller was objectui's own documentation site.

The 6 commits with no changeset are itemized by subject inside the changeset body rather than counted, per objectstack#6174 — they ship inside this pin but appear in no objectui CHANGELOG.

ADR-0087 disposition — answered, not left as the placeholder

The generator emits adr-0087: TODO whenever the range declares a breaking change and refuses to answer it itself (objectstack#6494). It is answered in the changeset as:

not-required (no-migration-prescription)

Reasoning, verified rather than assumed: @objectstack/console publishes a frozen prebuilt SPA — files: ["dist", …] and its sole exports entry is ./package.json, so it forwards no @object-ui/fields module entry point and neither removed export is reachable through this package. No packages/spec schema, authorable metadata key or protocol surface changes in the range, so there is nothing for objectstack migrate meta to prescribe and no ledger entry to write or to name. The retired-key items elsewhere in the list run the other way — objectui ceasing to author keys ObjectStack already retired and registered in its own PRs (rowLevelSecurity[].priority via #7130, the actionUrl widget key, page:card's body slot). This PR adds no ledger entry and claims none.

Why this bump, end to end

• objectui#4071 (28c38567b) registers the approvals:inbox component-registry key and de-hardcodes Home's approvals entry. With the pin forward, the bundled console carries that registration, so [approvals] Point the account app's Approvals nav at the inbox component; contribute a Setup inbox entry; document mounting the inbox in business apps #7234's { type: 'component', componentRef: 'approvals:inbox' } nav metadata (PR feat(approvals): point the account app's Approvals nav at the inbox component (#7234) #7298) resolves instead of rendering the component-not-found empty state. That is the [approvals][console] 「待我审批」有三个并存入口、三套不同 UI —— 其中 sys_approval_request 原生视图是无决策动作的开发者原始表 #7213 epic's end-to-end acceptance.
• objectui#4073 (8c60819a6) adds the bell-badge notifications + approvals breakdown in the inbox popover.

Both were already merged upstream; the pin was the only thing holding their behavior out of the bundled console.

Verification

scripts/bump-objectui.sh 8aad9fd50b16750aebdd294392ff79540f17cd32
  → 61 releasing changeset(s), 1 breaking (0 declared major, 1 annotated),
    0 release-nothing, 6 commit(s) without a changeset
  → wrote changeset console-8aad9fd50b16.md (@objectstack/console: minor)

scripts/build-console.sh
  ✓ Bundle canary 'import/jobs' present — framework client is in the bundle.
  ✓ @objectstack/console dist ready (50544 KB) from objectui@8aad9fd50b16

pnpm sdui:manifest          # ADR-0082 D4 ratchet, the second half of the procedure (#5960)
  ✓ wrote 57 public blocks → packages/console/dist/sdui.manifest.json
  Summary: 62 spec-only divergences, 0 blocks missing from the registry.
  ✓ no new DECLARATION divergence vs accepted baseline

pnpm check:console-sha          ✓ Console dist matches the objectui pin (objectui@8aad9fd50b16).
pnpm check:objectui-pin-fresh   ✓ objectui pin is FRESH — .objectui-sha is objectui `main`.
pnpm check:objectui-changeset   ✓ digest + range self-tests all passed
check-adr-0087-registration     ✓ 1 declared-breaking changeset(s), each carrying a disposition
check-changeset-no-major        ✓ This diff introduces no `major` bump.
check-empty-changeset           ✓ 1 declaring changeset(s) added
check-nul-bytes                 OK (6662 text files)

The declaration-parity ratchet reports no drift — the 62 spec-only divergences are the accepted baseline, unchanged by this pin.

Notes for the reviewer

Three things came out differently from what the card anticipated. All three are reported rather than smoothed over:

1. The no-argument form of the script would have pinned STALE. bump-objectui.sh with no sha defaults to the current HEAD of ../objectui, and in this container that checkout sat at 0a09793f2 — a strict ancestor of origin/main, 11 commits behind, i.e. 56 of the 67 commits in the range. The directive is pin to latest, so the sha was resolved explicitly from origin/main after fetching and passed as an argument. check:objectui-pin-fresh then confirms mechanically that the landed pin is objectui main.
2. No lockfile or hono-override change materialized. The card expected the regen to touch pnpm-lock.yaml plus the hono override; this range produced neither. The diff is exactly two files. origin/main was still merged in before opening this PR anyway, per the lockfile-contention rule.
3. The objectui clone here is shallow, which is the documented trap for this chore: the changeset digest exits 2 on an unwalkable range and degrades loudly. It was deepened (--depth=250) until 09987b68..origin/main walked, and the digest is the derived article, not the degraded tip-subject fallback — the artifact says so in its own accounting footer.

Diff surface

.objectui-sha and .changeset/console-8aad9fd50b16.md. Nothing else — no riders. packages/console/dist/ is gitignored and generated, and is confirmed absent from the diff; the changeset is the one the bump script emitted, not a hand-written second one.

---

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 10, 2026 6:09am