A `type: 'form'` action leaves the console shell for a bare `/forms/:name` page and ends on a generic "Thanks!" panel instead of the created record (observation)

[os-help]

Found while browser-verifying #6739 / PR #7237 (the ruled type: 'modal' → type: 'form' re-work of showcase_new_task). Filed separately, unfixed: it is pre-existing behavior that #6739's fix newly routes the showcase home page's primary CTA through, and it is not that card's scope.

Observation-class: nothing crashes, nothing is refused, and the record is created correctly. What is off is where the user ends up.

Measured

Real browser (Chromium 141), showcase booted with objectstack dev --ui --seed-admin, console served from packages/console/dist built by scripts/build-console.sh at the pinned .objectui-sha 09987b680d53801c79f67d969b14e9bb732b8a22. Full journey — start on the showcase home page, click the "Create Task" CTA:

home heading: ObjectStack Showcase
url after CTA click: http://localhost:3458/_console/forms/showcase_task.edit
dialogs: 0 | controls: 7
url after submit: http://localhost:3458/_console/forms/showcase_task.edit
RECORD QUERY total: 1
CREATED RECORD: {"id":"FUUCrcN0iO7hM1Dj","title":"#6739 browser-verified …","status":"todo","project":"SLJCKJy1_3RYDiI1"}

The record IS created. Two things about the surface it happens on:

1. The form route sits outside the console shell. In objectui apps/console/src/App.tsx (pinned SHA, line ~233) /forms/:name is a top-level route, a sibling of the app-shell routes rather than a child:

{/* Internal authed form — same renderer, different submit path. */}
Route path="/forms/:name" element={ ProtectedRoute + FormPage mode="internal" }

So the rendered page has no sidebar, no app navigation, no breadcrumb — screenshotted and confirmed visually, not inferred from the DOM. A user who clicks a record-create CTA on an app page is dropped onto an unchromed page with no way back except the browser's Back button.

2. The post-submit panel is the anonymous-form confirmation. FormPage resolves const behavior = loaded?.form?.submitBehavior ?? { kind: 'thank-you' }, so any form view that does not declare submitBehavior — including showcase_task.edit — renders:

Thanks!
Your submission has been received.

That is the right default for the public /f/:slug anonymous path the same component also serves. For an authed internal action it reads as a contact-form receipt: the user just created a Task and is told a submission was received, with no link to the record and no return to where they were.

Why it is worth recording

type: 'form' is the platform's validated, first-class way to open an object's form — the maintainer ruling on #6739 (2026-08-09) makes it the shape for this, retiring the type: 'modal' object fallback. So this is the surface every such action lands on, not a corner. showcase_log_time already ships on it; #6739 adds the home page's primary CTA and PR #6737's button.

The reference corpus therefore now teaches: "the sanctioned way to open a create form navigates out of your app and confirms with a generic receipt." Worth a decision even if the answer is "working as intended".

Shape of the question (not decided here)

• Should ActionRunner.executeForm navigate at all, or render the form view in a dialog the way the modal path does? A route keeps deep-linking; a dialog keeps context.
• If it stays a route, should /forms/:name in mode="internal" be nested inside the console shell layout?
• Should an internal submit default to { kind: 'redirect' } to the created record rather than thank-you, leaving thank-you as the public-mode default? Or should showcase_task.edit simply declare a submitBehavior (a corpus fix rather than a platform one)?

The renderer code is in objectui (packages/core/src/actions/ActionRunner.ts executeForm, apps/console/src/App.tsx, apps/console/src/components/FormPage.tsx); filed here because the question is what the spec's type: 'form' contract should mean, and because #6739's ruling thread lives here. Re-route if the answer is purely a renderer change.

No pm:queue — observation, for triage to grade.

---

Generated by Claude Code

[os-zhuang]

Maintainer ruling (2026-08-10, directed in session session_01BPWqbmEFU8gJepBJTHESXd): the type: 'form' contract means in-shell, and an internal submit lands on the record.

1. /forms/:name in mode="internal" nests inside the console shell (keep the route — deep-linking survives; the missing chrome is the defect, not the navigation).
2. Internal-mode submit defaults to redirect-to-created-record; thank-you stays the default for the public /f/:slug path only.
3. showcase_task.edit may declare a submitBehavior as an interim corpus fix, but the platform default is the ruling above — the corpus must not have to opt out of a wrong default.

The renderer changes land in objectui (App.tsx route nesting, FormPage mode-aware default) — per the file-at-destination ruling (#7167), the objectui half migrates there with this ruling quoted; this card tracks the contract statement.

needs-user-decision → pm:queue.

---

Generated by Claude Code

[os-help]

Claim: PM loop wave 2, card 3
Session: session_01YS2qzDAn3CpWdY7uBX9bFQ (devx seat, #6023)
Branch: claude/issue-7245-form-action-contract-docs
Worktree: cloud session, fresh clone (mode:cloud)
Domain: domain:devx
File surface: hand-written docs stating the type: 'form' action contract — expected content/docs/protocol/objectui/actions.mdx and content/docs/ui/forms.mdx (+ immediately adjacent hand-written pages if the contract is restated there). ⛔ Generated content/docs/references/** and packages/spec/src/** are out of surface: if the measured producer of the contract text is a spec zod describe/JSDoc, that is domain:spec-surface territory — stop and report the flag, do not patch the consumer side.
Container & model: M, mode:cloud, model: opus
Serial constraints cleared: none — no in-flight claim touches these docs pages; wave-mates are file-disjoint (SKILL.md / docs/qa).

Split per the maintainer's ruling above: this card delivers the contract statement in objectstack docs (in-shell for internal mode; internal submit defaults to redirect-to-created-record; thank-you is public-path-only). The renderer half (objectui App.tsx route nesting, FormPage mode-aware default, ActionRunner.executeForm) migrates to an objectui card filed by this seat with the ruling quoted — cloud dev sessions cannot reach the un-attached sibling repo, so the cross-repo card is PM-filed (backlink will follow on this thread).

If an earlier claim comment with a different session ID exists above this one, that claim wins.

---

Generated by Claude Code