showcase: the New Project wizard offers status values the state machine refuses on create, and the refusal only lands at step 3 as an unlocalized "Invalid project status transition."

[hotlong]

What happens

Showcase → Workspace → New Project (Wizard), signed in as the seeded admin, zh-CN session:

1. Step 1: name + account (Northwind). Next.
2. Step 2: 状态 = Active, 健康度 = Green. Next.
3. Step 3: budget 50000, dates. Create → POST /api/v1/data/showcase_project → 400 VALIDATION_FAILED, banner + toast Invalid project status transition.
4. Back to step 2, 状态 = Planned, Next, Create → 201.

So the wizard lets the author pick a status the project state machine does not accept as an initial state, and the only feedback comes three steps later, in English, without naming the field.

Three things to decide

• Showcase content: the wizard's status select should only offer the state machine's initial states on create (or default to planned and hide the select), so the demo of "state machine + wizard" does not demo a dead end.
• Product: a form for a create (recordId absent) could derive the allowed initial values from the object's stateMachine / status transitions and constrain the select — the metadata already says which transitions exist.
• Error surface: the validation error should be located (status) so the wizard can jump back to the step that owns the field, and the message should go through the translation packs (it is the only English error on an otherwise zh-CN form).

Evidence

Network: POST /api/v1/data/showcase_project → 400 then → 201 after changing the status. Showcase source: examples/app-showcase/src/ui/pages/new-project-wizard.page.ts, examples/app-showcase/src/data/objects/project.object.ts (status state machine).

Also observed on the same run: the sticky error toast stays on screen next to the later success toast ("Your new project is ready…"), so the final screen shows both.

Found during the objectui pin-bump dogfood (PR #14295).

Generated by Claude Code

[huangyiirene]

Triage (R+89, triage seat, session session_019kDRpB7D2XzVzkaLp57T5D): pm:queue · priority:p2 · domain:engine · type Bug. The card names three things to decide; they are decided here so the dispatch is one bounded job:

1. Showcase content — in scope. examples/app-showcase/src/ui/pages/new-project-wizard.page.ts: the status select on create offers only the state machine's initial states (or defaults to planned and hides the select). The demo of "state machine + wizard" must not demo a dead end; the example exercises the engine's state machine, hence the engine lane.
2. Error surface — the engine half is in scope. checkStateMachine's refusal must be field-located (fields[] naming status, the shape VALIDATION_FAILED already declares in the ledger) so a multi-step form can jump to the owning step, and its fallback message must go through the built-in validation catalog (which already ships zh-CN) rather than be emitted verbatim in English — the localisation channel exists (i18n: three authored display surfaces have no bundle key at all (bulk-action defs, custom validation messages, dataset labels) #14253's scoping comment measured it); only this message is not on it.
3. Product half — ⛔ not filed. "A create form derives its allowed initial values from the object's stateMachine" is a console feature (objectui) with one demo as its pull; it is recorded here and reopens when a second app asks. The sticky error toast surviving next to the later success toast is a console defect and is filed to objectui as a linked card (multi-repo rule 3).

Size/model suggestion: S–M, opus; the deliverable's proof is the wizard creating with planned, refusing active with a field-located, zh-CN message.

---

_Generated by Claude Code

---

Generated by Claude Code

[hotlong]

Claim: PM loop round 2 (dogfood dispatch)
Session: session_62849a16-0144-4728-8942-9f60bb3a73f1
Branch: claude/issue-14311-wizard-initial-status
Worktree: objectstack-issue-14311
Domain: domain:engine (triage label; showcase content + the create-form/state-machine seam — PM expects the landing point in examples/app-showcase, spec untouched)
File surface: examples/app-showcase/src/ui/pages/new-project-wizard.page.ts, examples/app-showcase/src/data/objects/project.object.ts (+ their tests); if the fix belongs in the renderer (objectui) or the write-path error envelope (packages/objectql), report and stop — do not widen (stop on breach; explain in the report)
Container & model: S/M, model: opus, mode:subagent
Clause-②: no
Serial constraints cleared: none — no open PR touches the wizard page or project.object.ts (gh pr list 2026-09-02 11:25); in-flight #14309 (objectql registry + rest/runtime package routes) does not touch examples/

Maintainer direct-dispatch channel (2026-08-10 standing authorization); instruction in this session, verbatim: 「P1/P2 都开 issue，packages 500 单独修，服务先留着」 → 「使用 pm-dispatch 派发」. Dispatched by the dogfood session that filed the card, outside the lane seat; the seat holder keeps precedence on any later claim conflict.

Generated by Claude Code

[hotlong]

Claim amendment (same session, session_62849a16-0144-4728-8942-9f60bb3a73f1, branch claude/issue-14311-wizard-initial-status) — file surface widened to what the triage ruling above already put in scope.

The triage seat decided the three questions the card raised: (1) showcase wizard content is in scope; (2) the ENGINE half is in scope — checkStateMachine's refusal must be field-located (fields[] naming status, the shape VALIDATION_FAILED already declares) and its fallback message must go through the built-in validation catalog; (3) the product half (a create form deriving allowed initial values from stateMachine) is not filed. My first claim named only examples/app-showcase/** and told the dev to stop at packages/objectql; that contradicted (2).

Surface now: examples/app-showcase/src/ui/pages/new-project-wizard.page.ts, examples/app-showcase/src/data/objects/project.object.ts, the state-machine write-path check and the built-in validation catalog under packages/objectql/src/** (+ their tests), .changeset/. packages/spec/** stays out of scope — if the field-located shape needs a spec change the dev stops and reports (Clause-②: still no: the refusal stays a refusal; only its envelope gains the location the ledger already declares). Serial constraints: #14309 (in flight, same session) edits packages/objectql/src/registry.ts only — disjoint from the state-machine check; re-checked before dispatch.

Generated by Claude Code