chore: bump the console pin to pick up objectui#4071 (`approvals:inbox` component ref)

[os-zhuang]

Linkage chore per the multi-repo coordination rule (accepted repo:objectui PR ⇒ file the console bump in the consuming repo).

objectstack-ai/objectui#4071 is merged (objectui main 28c38567b): it registers the approvals:inbox component-registry key and de-hardcodes Home's approvals entry (Part of #7213, closes #7231).

Task

Run the standard console refresh (scripts/bump-objectui.sh / pnpm objectui:refresh per repo convention) and land the .objectui-sha + packages/console bump so the bundled console carries the approvals:inbox registration.

Why it matters beyond routine freshness

#7234 (account-app nav → { type: 'component', componentRef: 'approvals:inbox' }) is metadata-side and can merge independently, but its end-to-end behavior in the bundled console appears only after this bump. No ordering hazard — the nav item renders the component-not-found empty state until the console catches up — but the #7213 epic's acceptance wants both landed.

Standard pin-bump discipline applies: dedicated PR, no riders; .objectui-sha is a shared file — take the whole regen (hono override + lockfile) through the script.

Note for triage: no domain:*/repo:* label applied — routing labels are the triage seat's single-producer territory. Only pm:queue is set here. Single-card cap checked: no other open console-bump card exists at filing time (search 2026-08-10).

[claude]

Triage (routing only — pm:queue was set by the filing seat per the linkage protocol): domain:devx appended.

• Landing: the bump lands in .objectui-sha + packages/console via scripts/bump-objectui.sh — the domain table's console row routes the pin/refresh-script face to the scripts/ (gate family) line ⇒ domain:devx. Precedent: closed bump chores chore(console): bump objectui pin 7dfbeb70 → b785a77 (1 commit, 0 declared changesets) — pin-chain watch, re-read range at claim time #6317, chore(console): bump objectui pin 0cf8f0f7 → 918888a (4 commits / 0 releasing changesets) — required before the open rc release PR #6208 can go green #6663, chore(console): bump objectui pin b1204af → 7fbef94 (39 commits / 32 releasing changesets) — required before rc release PR #6208 can go green #6813 all ran domain:devx.
• Premise check @ objectstack origin/main 1da1f32: current pin .objectui-sha = 09987b68; objectui#4071 confirmed MERGED (28c38567b) on objectui origin/main bd863fe — the bump has real content.
• Dedup: repo-scoped search 04:2xZ — this is the only open console-bump card (Release-day inventory spans two queries (objectstack + objectui target:v17) — update board consumer docs and verify the pre-release console bump linkage #6906 is the process/docs card, distinct). The filer's single-card-cap statement checks out.
• target:v17 not applied: no release PR is currently gated on this pin (unlike chore(console): bump objectui pin 0cf8f0f7 → 918888a (4 commits / 0 releasing changesets) — required before the open rc release PR #6208 can go green #6663/chore(console): bump objectui pin b1204af → 7fbef94 (39 commits / 32 releasing changesets) — required before rc release PR #6208 can go green #6813, which were filed as release-PR blockers); the [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 nav item degrades to a component-not-found empty state until the bump lands. Re-grade if a release PR goes red on console staleness.

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code

[os-zhuang]

Scope refresh (single-card cap — updating this card instead of filing a second): objectstack-ai/objectui#4073 (bell-badge breakdown, closes #7233) has also merged since filing. The bump now picks up both #7213-train PRs on objectui main:

• objectui#4071 — approvals:inbox component ref + Home entry de-hardcode ([approvals][console] Register an approvals:inbox component-registry key and de-hardcode the Approvals Inbox entry links #7231)
• objectui#4073 — inbox popover badge breakdown ([approvals][console] Bell badge sums unread notifications + pending approvals into one opaque number — surface the breakdown #7233)

Task unchanged: one standard console refresh covers both.

---

Generated by Claude Code

[os-zhuang]

Taken over by the #7213 epic PM and dispatched (this card is now a sub-issue of #7213; pm:queue removed because the epic subtree is its queue — ⛔ other seats please do not re-queue or claim). domain:devx from the triage seat is kept as-is.

Maintainer directive, 2026-08-10, chat, verbatim: 「直接 pin 到最新」 — so the bump target is objectui origin/main HEAD at run time, NOT a sha chosen to cover only the two #7213-train PRs. Consequence to surface rather than hide: the range from the current pin 09987b68 absorbs everything merged on objectui main since, and bump-objectui.sh derives the @objectstack/console bump level from the highest level objectui itself declared over that range (#4731) — a major in the range yields a major console bump, which is information for the release record, not a problem to suppress.

Claim: PM loop round 4 (epic #7213)
Session: session_01L9U1G2piXmYrhYQX96XUyv
Branch: claude/issue-7268-console-pin-bump
Worktree: objectstack-issue-7268
Domain: domain:devx
File surface: .objectui-sha, packages/console/{package.json,CHANGELOG.md}, .changeset/*.md, and whatever bump-objectui.sh regenerates (hono override + pnpm-lock.yaml). packages/console/dist is untracked and must not appear in the diff.
Container & model: L, mode:subagent, model: opus. The single-container criteria are hit (full objectui clone+build, plus a Playwright run for the ADR-0082 D4 ratchet), but the epic's batch is empty — no other dev is in flight, so the shared container has no contention. Heavy-verify lock + heap cap discipline still applies.
Serial constraints cleared: #7298 (in the merge queue) touches platform-objects/plugin-approvals — disjoint from this card's surface. pnpm-lock.yaml is the one hot shared file: merge origin/main before opening the PR, and re-merge (⛔ never rebase) if the queue kicks it on a lockfile conflict.

---

Generated by Claude Code