Global not-found route

Honest 404 recovery with a command finder

Overview

The global not-found route handles unmatched App Router paths with a clear 404 state and a command finder powered by the shared `taskcenter-command-palette` component.

Entry route

any unmatched app URL resolved by `src/app/not-found.tsx`.

Status

Live.

Data source

no runtime data; the page uses static, real first-party navigation destinations only.

Required permissions

none for the 404 page itself, while destination routes enforce their own authentication and RBAC.

Empty state

There is no data-backed empty state. If a user reaches an unknown URL, the route explains that the page is unavailable and offers direct navigation to home, the workbench, docs, and help.

Failure state

If the command finder cannot match a query, it shows a bounded "No matching destination." result inside the palette. If a selected destination requires sign-in or authorization, that destination's existing auth/RBAC gate handles the next state.