docs: spell the console form routes with the real /_console mount

[os-project-manager]

Fixes#9050

Documentation only. No route, code or config is changed.

The fork: this was a CORRECTION, not a convention choice

The card framed the canonical spelling as an open decision, and the dispatch split on it: if /console/forms/:name does not resolve, the 14 sites are simply wrong; if both spellings resolve, it is a real convention choice and I must stop rather than pick. It does not resolve, so this is a correction.

What I read to decide — the route mounting, not the URL string:

• packages/cli/src/utils/console.ts:43 — export const CONSOLE_PATH = '/_console'. A hardcoded constant; nothing configurable feeds it.
• Same file :534-541 — the only three registrations: / redirects to /_console/; bare /_console redirects to /_console/; /_console/* serves the SPA. Nothing registers a bare /console, and there is no catch-all that would reach one.
• Same file :516 — the mount injects a base-href tag pinned to /_console/, from which React Router derives its basename.
• objectui apps/console/src/App.tsx:225 — path="/forms/:name" is a route inside that SPA, so it hangs off the basename above ⇒ live URL /_console/forms/:name. This matches the browser measurement recorded during 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) #7245's triage.

The one configurable knob is uiBasePath (default /_console, packages/spec/src/system/auth-config.zod.ts:302). It is not an outer-prefix switch: its only consumers are in plugin-auth, which uses it to build links into the Console's auth pages (auth-manager.ts:3622-3632). It cannot make a bare /console request resolve, so the "both spellings resolve" branch of the fork is closed on evidence rather than assumption.

Checked and explicitly not a spelling ruling: the ruled 2026-08-10 on #7245 line quoted in view.zod.ts:2446 pins the mode-aware submitBehavior default. The paths in that comment are incidental prose, so nothing here contradicts a landed ruling.

Re-derived enumeration

The card's count was measured at filing time, so I re-ran its own command on this branch's base (2cb69c31c) rather than trusting it:

$ grep -rn "console/forms/" content/docs skills | grep -v "_console" | wc -l
14

14 — exactly the card's number. No drift across today's merges (#9033 / #9051 / #9052 / #9056). All 14 are swept here; none legitimately needs the other spelling.

One extension beyond the card's 14, named deliberately

The card measured /console/forms/ only. The sibling public form path is documented as /console/f/:slug — 6 further occurrences in the same two files — and it is the identical defect: same missing underscore, same SPA, pinned by the same route table (apps/console/src/App.tsx:180, path="/f/:slug").

I swept those 6 as well, because leaving them is precisely the failure the card exists to prevent. They are not in some distant file — they are interleaved with the lines being fixed:

• forms.mdx:12 (public) sits directly above :13 (internal), two rows of one table;
• forms.mdx:314 carries both spellings in a single sentence;
• actions.mdx:170 carries both in one table row.

Fixing only the internal path would have left one sentence reading "/console/f/:slug (public) and /_console/forms/:name (internal)", which is strictly more confusing than the state before this PR.

Total: 20 occurrences (14 internal + 6 public) across 3 files.

Verified as a false positive, deliberately untouched

forms.mdx:454 matches a naive /console/ grep, but only as the prose fragment Studio/console/native shells — a list of shell names, not a path. It is unchanged.

Scope boundaries respected

packages/spec/src/ui/view.zod.ts (:2446, :2449) and action.zod.ts (:500) carry the same wrong spelling in JSDoc comments. Those are code and out of scope for this documentation-only card, so they are filed as #9078, not edited here. (They are comments, not .describe() strings, and no generated reference page carries the text today, so nothing published depends on them.)

Verification

Gate families derived from the final diff, not recalled — node scripts/pm/dispatch-gates.mjs content/docs/ui/forms.mdx content/docs/protocol/objectui/actions.mdx skills/objectstack-ui/SKILL.md returned three: check:docs-audit-scope, check:docs-redirects, check:role-word. I added three the derivation did not name but the diff visibly implicates: check:nul-bytes (any edit), check:doc-authoring, and check:doc-anchors — the last because this diff renames a heading, ## 6. Internal forms (...), which changes its anchor slug.

All six run at the final commit c7b75b292, all green:

===== check:nul-bytes ===== [exit 0]
===== check:docs-audit-scope =====
✓ docs-accuracy-audit scope is in sync with content/docs/: 178 hand-written doc(s).
[exit 0]
===== check:docs-redirects =====
check-docs-redirects: OK (apps/docs/redirects.mjs: 92 entries -- 89 page destination(s)
resolved against content/docs, 3 wildcard destination(s) ..., 98 chain probe(s) matched)
[exit 0]
===== check:role-word =====
check-role-word: OK (43 baselined file(s), no new occurrences).
[exit 0]
===== check:doc-authoring =====
✓ doc authoring guard: 376 files clean — no bare metadata literals.
[exit 0]
===== check:doc-anchors =====
✅ check-doc-anchors: 239 internal #fragment link(s) across 396 source file(s)
all resolve to a real heading
[exit 0]

The renamed heading is safe on two independent readings: check:doc-anchors resolves all 239 fragment links, and a direct search for inbound links to that heading (internal-forms) finds none anywhere in content/docs, skills or packages.

Check Documentation Links covers page-path links rather than #fragment anchors, so it does not overlap with the gate above — but it is unaffected here regardless: grep -noE '\]\([^)]*console[^)]*\)' over all three changed files returns nothing, i.e. this diff touches no markdown link target. Every one of the 20 edits sits inside backticks or a fenced code block.

Also scanned beyond the gate for control bytes, since paths and escapes are being edited: grep -naP '[\x00-\x08\x0b\x0c\x0e-\x1f\x7f]' over the three files is clean.

No changeset: this PR changes only content/docs/** and skills/** and publishes no package, so it releases nothing — skip-changeset applied.

Merge posture

⛔ This PR touches skills/objectstack-ui/SKILL.md, an AI-no-merge path (#7623 / #7548). It is deliberately a draft, is not queued, and has no auto-merge. It waits for a human reviewer.

---

Generated by Claude Code