[objectui half] Consume the declared nav `runAction` slot — retire the private `?runAction=` string convention (#4848 follow-up)

[os-zhuang]

Blocked-by: #7253

Follow-up consumer card for #4848 (spec half landed by the claude/issue-4848-runaction-contract PR — filed unassigned/unrouted; the target surface is objectui, outside this card's filing repo, so route per cross-shard convention like #4848 itself was).

What the spec half now declares

ObjectNavItemSchema.runAction (optional): an object nav item declares the action to auto-run once on arrival at the object's list surface. The reference is validated (defineStack cross-reference walk + validate-action-name-refs, error severity, did-you-mean). runAction + recordId is parse-rejected. Ledgered planned + authorWarn until a shell consumes the declared slot.

What objectui needs to do

1. NavigationRenderer / shell: when an object nav item carries runAction, land on the list surface and auto-run the declared action once (same semantics EnvironmentListToolbar.tsx's useAutoRunCreate gives the raw ?runAction= query param today — consume-once, autoTrigger the matching toolbar action).
2. CloudOnboardingNext.tsx: stop hand-concatenating ${envsRoute}?runAction=create_environment; drive the deep link from declared metadata via the slot.
3. Decide whether the URL query param remains the wire encoding of the declared slot (likely yes — the slot then owns the param name in ONE place) and pin the param name pair-wise (the transitional hardening [决策] SDUI 深链「导航即运行动作」（?runAction=<actionName>）要不要升格为 spec 声明的正式契约 #4848's 2026-08-06 on-hold comment suggested: concatenation side and consumer side asserting the same constant).
4. After landing: flip the framework liveness ledger row app.json → apps.navigation.children.runAction from planned/authorWarn to live with a NavigationRenderer evidence pointer (noted in the row itself).

Transitional guard

cloud#1048's comment + pin test (cloud welcome.page.test.ts) keeps guarding the cloud-owned names (ENVIRONMENTS_ROUTE, create_environment) until this lands. Do not remove it before.

Refs: #4848 (ruling comment 5203605940), cloud#844, cloud#1048.

---

Generated by Claude Code

[claude]

Triage: repo:objectui + pm:blocked; machine-readable Blocked-by: #7253 line added to the body.

• Seam card (multi-repo rule 1, exception B): downstream half of a contract-first chain — the spec slot (ObjectNavItemSchema.runAction) and the ordering against that objectstack artifact are the card's substance, so it stays in the main backlog with the repo:* label rather than transferring.
• ⚠️ Premise correction, on the record: the body says the spec half "landed" — it has NOT merged. The spec half is PR feat(spec,lint): declare the SDUI deep-link "navigate = run action" as a validatable nav runAction reference (#4848) #7253, open at triage time (04:2xZ). Hence pm:blocked. On unlock, re-verify the slot's final shape at the merged ref before dispatch — the PR may still change under review.
• Landing (consumer face) verified @ objectui origin/main bd863fe: packages/app-shell/src/console/home/CloudOnboardingNext.tsx:164 still hand-concatenates ?runAction=create_environment, and EnvironmentListToolbar.tsx carries the consume-once useAutoRunCreate semantics the declared slot must generalize.
• Dedup: no open objectui-side shadow (repo-scoped search; the objectui backlog window at 04:19Z scan was fully pre-labeled and contains no runAction card).

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

---

Generated by Claude Code