Programmatic navigation resolves to pages

Programmatic navigation to a non-existent route is worse UX than a static link to a non-existent route: the user clicks a button, takes a deliberate action, and ends up on a 404 with no breadcrumb back to where they were. router.push('/admin/users') when no app/admin/users/page.tsx exists is the exact shape of this failure. It breaks post-signup flows, post-payment redirects, and admin dashboards — all critical journeys the audit fixtures test.

For each unresolved navigation call, either fix the specifier to point at a real route or create the destination file. In Next.js App Router using useRouter:

import { useRouter } from 'next/navigation'
const router = useRouter()
router.push('/admin/team')  // matches app/admin/team/page.tsx

If the destination is genuinely missing, scaffold app/admin/users/page.tsx so the navigation has a target.