rfc-app

Files

T

Ben Stull 948ee88160 fix(routing): render a 404 page for unmatched routes (v0.52.3)

The top-level catch-all silently redirected unknown paths to "/", and the
nested /admin/*, /p/:projectId/*, and /docs/* route groups had no catch-all
(invalid subpaths rendered a blank pane). Add a shared NotFound component and
wire it into all four route groups so a bad/typo'd URL shows a clear 404 with
a link home. Client-side 404 UI (SPA still serves HTTP 200).

Patch 0.52.2 → 0.52.3; CHANGELOG updated. Caught by the operator on PPE.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-08 20:14:25 -07:00

src

fix(routing): render a 404 page for unmatched routes (v0.52.3)

2026-06-08 20:14:25 -07:00

.env.example

§22 M3 frontend: /p/<project>/ routing, runtime branding, directory, 308s (v0.35.0)

2026-06-04 05:58:59 -07:00

index.html

§22 M3 frontend: /p/<project>/ routing, runtime branding, directory, 308s (v0.35.0)

2026-06-04 05:58:59 -07:00

package-lock.json

§22 M3-backend Plan B (2/2, read path): per-project RFC serving (v0.37.0)