docs: drop stale renderer-status notes now that the type:'form' contract is shipped (#7245)

Both dated "Current renderer status (2026-08-10)" callouts in
protocol/objectui/actions.mdx and ui/forms.mdx said the pinned console did
not yet implement the in-shell + redirect-to-created-record contract. It
now does: at the current .objectui-sha (665661ab...) FormPage.tsx's
resolveSubmitBehavior returns { kind: 'created-record' } for internal mode
and App.tsx mounts /forms/:name via InternalFormRoute (DefaultHomeLayout),
matching objectui#4109 (merged 2026-08-11). Removing the two notes; the
contract statements above them already state the shipped behavior
accurately and needed no rewrite. The unrelated redirect-token note at
forms.mdx:424 (a different, still-open card, objectui#4190) is untouched.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011RB4waLuNbdruCo6X9oobm

Author: claude

content/docs/protocol/objectui/actions.mdx

@@ -175,17 +175,6 @@ target: customer_quick_edit
 
 The four `submitBehavior` kinds and their options are documented on the [Forms guide](/docs/ui/forms).
 
-<Callout type="warn">
-**Current renderer status (2026-08-10).** The console shipping at the pinned
-`.objectui-sha` does **not** implement this contract yet: it renders
-`/console/forms/:name` as a top-level page outside the shell, and it falls back
-to the `thank-you` panel in both modes. The statement above is the contract —
-the renderer half is tracked in ObjectUI and linked from the
-[#7245 thread](https://github.com/objectstack-ai/objectstack/issues/7245). Until
-it lands, an internal FormView that must land on its new record has to declare
-`submitBehavior` explicitly.
-</Callout>
-
 ### Modal Actions
 
 Open a modal/page by name. `target` is resolved as a **page** first, then as an object (which opens that object's create/edit form); when it names neither, the action falls through to its server-side handler.

content/docs/ui/forms.mdx

@@ -434,8 +434,6 @@ Widening this — an allowlist of absolute origins, say — waits for measured d
 
 An explicit `submitBehavior` overrides the default in either mode, so nothing here removes an option — it only changes what an author gets for declaring nothing.
 
-> **Current renderer status (2026-08-10).** The console shipping at the pinned `.objectui-sha` still applies `thank-you` as the default in **both** modes. The table above is the contract; the renderer half is tracked in ObjectUI and linked from the [#7245 thread](https://github.com/objectstack-ai/objectstack/issues/7245). Until it lands, declare `submitBehavior` explicitly on an internal FormView that must land somewhere specific.
-
 ## 9. `type: 'form'` action — declarative form launchers
 
 App actions can declare `type: 'form'` to open a FormView without resorting to free-form URLs. The `target` is the FormView name; the runtime navigates to `/console/forms/:name` **inside the console shell** — the operator keeps the sidebar, navigation and breadcrumb, and a successful submit lands on the created record per the mode-aware default above. The full contract is stated on the [Action Protocol page](/docs/protocol/objectui/actions#what-type-form-promises).