Remove Web Tanstackstart Page Frame

Archived: 2026-11-07 · roadmap-id: web-tanstackstart-template

Why

Builder ruling (2026-10-15): in domain package Web apps, secondary pages must never be wrapped in a Card (no rounded + bordered + card-background surface around page content).

templates/web-tanstackstart currently does the opposite by default. PageShell defaults isFramed = true and draws a frame (border + --radius-container + --color-background-card) around every second-level page body, and DESIGN.md ("Skeleton") prescribes "one content frame (--radius-container + card surface)". The in-flight change web-tanstackstart-ui-contract-adoption (task 2.3, design D3, spec "Card restraint" scenario) explicitly approved that "one framed content region". Packages generated from the template (my-career, agent-eval) inherited the frame. Because an approved spec mandates the frame, removing it is a spec change and needs its own approved proposal before any template code is touched.

Capabilities

New Capabilities

Modified Capabilities

• web-tanstackstart-ui-language: adds a "No page-level card frame" requirement and replaces the framed-region scenario of "Card restraint". (The base spec still lives inside the unarchived change web-tanstackstart-ui-contract-adoption; this delta is expressed as ADDED and must be reconciled at archive time.)

Non-goals

• Fixing already-generated packages (my-career, agent-eval); handled in another repo.
• Removing Card/ClickableCard components themselves or the first-level landing module entries (independent, actionable units remain a legitimate use).
• Redesigning the one-screen skeleton (fixed 2rem gap, non-scrolling page, inner scroll) beyond removing the frame.
• Publishing, pushing, or versioning anything.