chore: refresh the vendored console to 2cb8d78e24ad + fix the refresh bump type (#3528)

[os-zhuang]

Ships the #3528 screen-flow fixes to actual users, and fixes a silent bug in the refresh tooling found while doing it.

Why this is needed

@objectstack/console publishes a prebuilt objectui SPA pinned by .objectui-sha: the release pipeline clones objectui at that commit, builds it, and ships the dist alongside the framework. So a merged objectui fix reaches nobody until the pin moves.

The screen-flow fixes for #3528 landed in objectui (objectui#2830, objectui#2833) and were stranded there. This is not hypothetical — it is the exact trap I hit while investigating the issue: the console source was already correct while the running console at /_console served an older build, which is why the first repro looked like the bug was somewhere else entirely.

Pin: cf2d56e32a11 → 2cb8d78e24ad (objectui main), which carries both screen-flow PRs plus everything else merged frontend-side since the last refresh. The generated changeset lists the full range.

The tooling bug

scripts/bump-objectui.sh picks the changeset bump type — minor if the objectui range contains any feat, else patch. It tested that with:

git -C "$OBJECTUI_ROOT" log --format=%s "${OLD_SHA}..${NEW_SHA}" | grep -qiE '^feat'

Under set -o pipefail (line 32), grep -q exits on the first match, the still-writing git log takes SIGPIPE, and the pipeline returns 141. The test therefore always took the else branch: every refresh has been silently stamped patch, feature ranges included. Demonstrated on this very range:

$ (set -euo pipefail; git log --format=%s cf2d56e..2cb8d78 | grep -qiE '^feat') ; echo $?
141
$ git log --format=%s cf2d56e..2cb8d78 | grep -ciE '^feat'
23

Counting with grep -c drains the input, so there is no signal and the count is truthful. With the fix, the same invocation now writes "@objectstack/console": minor — as the script's own documented rule always intended.

Test plan

• Ran the real tooling, not a hand-edit: OBJECTUI_ROOT=… scripts/bump-objectui.sh 2cb8d78e24ad --no-commit produced both .objectui-sha and .changeset/console-2cb8d78e24ad.md.
• Before the fix that same command wrote patch; after it, minor. Both observed.
• pnpm check:console-sha → passes (no dist in this checkout, so nothing to drift against).
• The pinned commit is objectui main, which its own CI builds (Build & E2E runs the console vite build, Bundle Analysis runs the full tsc && vite build and reported the entry at 28.0 KB / 350 KB budget) on every PR — so the pin is known-buildable without re-running the ~15-minute console build here.

Note the changeset is minor where recent console refreshes read patch; that is the corrected behavior, not a deliberate escalation for this range.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LX9ut3MK3KykE11S9bJmv5

---

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		Jul 27, 2026 5:02am