chore(deps): upgrade @objectstack/* to 17.0.0-rc.5 — and surface which version-locked adaptation cards it unlocks

[hotlong]

Maintainer-directed (2026-08-07): upgrade this repo to the framework's 17.0.0-rc.5 (published 09:39Z today via the new human-gated release lane), then report which previously version-locked cards are now unblocked.

Current state (measured on origin/main)

36 dependency entries across the workspace pin ^17.0.0-rc.2: @objectstack/spec ×31, @objectstack/formula ×2, @objectstack/client ×2, @objectstack/lint ×1. The lockfile resolves the old rc.

Ask

1. Bump every @objectstack/* range to ^17.0.0-rc.5 + refresh pnpm-lock.yaml.
2. Restore green: build + typecheck + full tests. rc.3→rc.5 carried real breaking surface — expect fallout from (non-exhaustive; verify against the framework changelogs on npm/main): FieldMapping.transform union retirement (objectstack#6078, first entries in RETIRED_KEYS_BY_MAJOR/RETIRED_DEFS_BY_MAJOR), ctx.user.roles retirement ledger entry (objectstack#6011), the exported HttpServer delegating-wrapper retirement (objectstack#6141), undefined filter comparands now refused with INVALID_FILTER/400 (objectstack#6142 — behavioral, check test fixtures), plus whatever rc.3 carried before them.
3. Rider discipline (binding): the upgrade PR contains ONLY the bumps + the MINIMUM adaptations needed to restore green (compile errors from renames/retirements; parity/pin tests that their own cards pre-declared would go red on dependency refresh, e.g. 适配 spec 退役 NotificationActionSchema / EmbedConfigSchema(objectstack#5015):3 个测试文件引用将随依赖刷新变红 #3362's three test files). Feature-class adaptations stay on their own cards — do NOT implement them here.
4. Unlock survey (the second deliverable): for each of these known version-locked cards, state in your report whether the upstream it waits on is now in rc.5 (and therefore the card is dispatchable): 台账燃尽批次 8/8 · 被 objectstack#4171 阻塞的 any 擦除簇,3 符号——上游解除后处理(objectstack#4115) #3162 (blocked on objectstack#4171), ThemeEngine 停发已退役的 9 组 CSS 变量(objectstack#5021 选项 2 裁决的 objectui 半边) #3361 (objectstack#5021 half), 适配 spec 退役 NotificationActionSchema / EmbedConfigSchema(objectstack#5015):3 个测试文件引用将随依赖刷新变红 #3362 (objectstack#5015 half — expects its 3 test files to go red HERE), 适配 spec 退役五个交互配置模块(objectstack#4988):useOffline 生产耦合 + types 再导出 + 三个 parity 测试(含可解锁的命名回收) #3363 (objectstack#4988 half), record:highlights block 的 inputs 声明 readonly,使其进入 sdui.manifest.json(objectstack#5176 裁定 A 的 objectui 半边) #3407 (objectstack#5176 half), spec 把 5 值 HTTP 方法子集改名(HttpMethodSchema → HttpMethodSubsetSchema、HttpMethodType → HttpMethodSubset),packages/types 两处 import 需跟名 #3499 (HttpMethod subset rename — 2 imports in packages/types must follow, likely a REQUIRED green-restoring rider), useObjectLabel viewSuffixes:去掉带前缀全名第二候选 —— objectstack#5164 裁 A 的 objectui 段 #3502 (objectstack#5164 裁 A objectui 段), parseAiQuotaError 先学会嵌套信封形态(消费端先行)—— cloud 两个 429 生产者随后按 ADR-0112 收敛(cloud#944 移交) #3491 (nested-envelope consumer-first). Also grep open issues for other Blocked-by: lines naming framework versions/PRs and include them.

Repo hazards (read before starting)

• ⛔ Never git stash — the stash stack is shared across worktrees in this repo (CLAUDE.md; objectui#3430 incident).
• ⚠️ objectui#3523 (P0): the merge queue's required set is EMPTY — the queue validates nothing. Your PR's own CI must FULLY converge green before it is marked ready; nothing downstream will catch a red.
• New user-visible strings need locale keys in all ten packs (t() call-site key gate, objectui#3547 landed).
• Changeset per repo convention for a dependency refresh across published packages (read a recent framework-refresh PR for the precedent shape).

Verification

Full workspace build + typecheck + test; the gate list enumerated from this repo's CI workflows (do not pick from memory); confirm the resolved versions in the lockfile are 17.0.0-rc.5 everywhere (no split-brain ranges).

Deliverable: pushed DRAFT PR in objectui (Fixes objectstack-ai/objectui#<this>), body in English listing the bumps, every green-restoring rider with its one-line justification, and the unlock-survey table.

[hotlong]

Claim: PM session (maintainer-directed dispatch in chat, 2026-08-07: 「给 objectui 仓库派一个任务,要求升级到 17.0.0-rc.5,然后有些之前被版本锁定的任务应该可以解锁继续了」)
Session: session_01BickTBKm2JYSNnrtPT8ysa
Branch: claude/issue-3560-upgrade-rc5
Worktree: objectui-issue-3560
Domain: repo-wide dependency refresh (objectui whole-repo seat scope; seat may sequence/veto)
File surface: 36 package.json dependency entries (spec×31, formula×2, client×2, lint×1) + pnpm-lock.yaml + ONLY green-restoring adaptation files (each justified in the PR body); ⛔ no feature-class adaptations
Container judgment: this card meets the heavy criteria (dependency-family upgrade + full regression) which nominally routes to mode:cloud — deliberately kept mode:subagent because in-session-created cloud triggers do not carry the GitHub connector in this deployment (objectstack#5474 lesson: fired session cannot open the PR or post its report). Shared-container resource discipline (flock + heap caps) applies instead.
Serial constraints cleared: no open objectui PR touches the dependency ranges (checked open list); in-flight sibling work (objectstack#4415 dev) is a different repo, file-disjoint.

---

Generated by Claude Code

[hotlong]

Review: ACCEPT → PR #3568, flipping ready and enabling auto-merge.

• Scope check clean: 37 bumps (the dev corrected my count — plugin-grid declares spec twice) + lockfile with zero split-brain, and every one of the ten riders is a compile/runtime break the bump itself lands, individually justified. The ObjectStackDataSource.delete() 读 result.deleted —— 服务端从不返回该键,delete 的 MutationEvent 从未发出、返回值恒 undefined;测试绿是因为 fixture 自己编了这个键 #3412 fix rode legitimately (TS2339-forced; carries the reverse pin that card asked for; Fixes line present).
• Verification independently confirmed: Type Check success 13:49:49Z, Lint success, Test shards 1–4 success, 16 success + 2 by-design skips, zero failures; mergeable_state: clean. Since objectui#3523 leaves the merge queue validating nothing, this PR's own converged run is the load-bearing gate — it converged before ready, per the dispatch instruction.
• Pin dispositions reviewed per file — the two INVERTED pins (page-nav-misc and offline-nav-performance) fired exactly as their own comments designed, and the tautology-avoidance on the retired parity pairs (pin by content, keep the render-loop halves) is the right call. The new negative controls (plugin-calendar README 教的 calendarComponents 手动注册 API 不存在 —— 照抄即抛 #5010 keys refused by name; ThemeEngine stale-theme emits nothing, paired with positive controls) are review-grade.

Post-merge unlock actions — handing to the objectui seat (this issue closes on merge; the survey table in the PR body is the authoritative record):

1. Close with verification: spec 把 5 值 HTTP 方法子集改名(HttpMethodSchema → HttpMethodSubsetSchema、HttpMethodType → HttpMethodSubset),packages/types 两处 import 需跟名 #3499, ThemeEngine 停发已退役的 9 组 CSS 变量(objectstack#5021 选项 2 裁决的 objectui 半边) #3361, 适配 spec 退役 NotificationActionSchema / EmbedConfigSchema(objectstack#5015):3 个测试文件引用将随依赖刷新变红 #3362 (done inside this PR; ThemeEngine 停发已退役的 9 组 CSS 变量(objectstack#5021 选项 2 裁决的 objectui 半边) #3361 wants a quick four-item check against the PR before closing).
2. Dispatchable now: 适配 spec 退役五个交互配置模块(objectstack#4988):useOffline 生产耦合 + types 再导出 + 三个 parity 测试(含可解锁的命名回收) #3363 (re-scoped to the name-reclaim rename — carries a premise correction), record:highlights block 的 inputs 声明 readonly,使其进入 sdui.manifest.json(objectstack#5176 裁定 A 的 objectui 半边) #3407, parseAiQuotaError 先学会嵌套信封形态(消费端先行)—— cloud 两个 429 生产者随后按 ADR-0112 收敛(cloud#944 移交) #3491 (never version-locked — it is the blocker for cloud#1168).
3. 台账燃尽批次 8/8 · 被 objectstack#4171 阻塞的 any 擦除簇,3 符号——上游解除后处理(objectstack#4115) #3162 needs re-triage, not dispatch — its stated blocker is resolved but its real blockers are the objectui#3177 structural pins, still green.
4. useObjectLabel viewSuffixes:去掉带前缀全名第二候选 —— objectstack#5164 裁 A 的 objectui 段 #3502: confirm the objectstack#5164 cli segment shipped before dispatching.
5. New card FilterConditionField 无法生成 spec 新增的 $icontains(大小写不敏感 contains)—— 服务端已接受,筛选 UI 到不了 #3567 ($icontains unreachable from the builder UI) awaits routing; the exclusion is ratcheted in-test so it cannot outlive its reason.

---

Generated by Claude Code