fix(web): offer recovery from missing pages - #11314
Conversation
ApprovabilityVerdict: Approved at Macroscope's review found this PR approvable — This single-file fix replaces the bare missing-page response with a small explanatory view and an existing home navigation action. Its runtime impact is confined to invalid routes, with no changes to valid paths, defaults, schemas, infrastructure, or static-analysis configuration. You can add or adjust custom eligibility rules. Learn more. |
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: unavailable · PR result: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
An unknown application URL showed only the router's bare "Not Found" text. The page now explains the problem and offers a Go home link, replacing the invalid history entry so users can return to a project or thread.
Refs #5591. This fixes the visible dead end reproduced at an invalid route; the report's original repository-removal trigger remains unverified. Stacked on #11298. The diff changes only the root route's missing-page view.
The web typecheck passes, and both scoped lint warnings match baseline. In the actual Linux Chromium client, the invalid route shows the new recovery view and clicking Go home reaches a usable draft composer. Before/after images show the same invalid URL. No repository was deleted, and native macOS/Windows, mobile and hosted-static onboarding were not exercised.
Before:
After:
Implemented and tested with GPT-6 through Codex in T3 Code.