Consolidate duplicate web dashboard routes into one canonical product experience

[Purity-Euphemia]

Closes #193 # PR: Consolidate duplicate web dashboard routes into one canonical product experience (#193)

Summary

This PR consolidates duplicate dashboard routes in the Next.js web app by making the alternate dashboard surface redirect to the canonical /dashboard route. The goal is to remove dashboard drift and provide a single, consistent product experience.

Changes

• Replaced the alternate dashboard UI with a client-side redirect to the primary dashboard.

Modified files:

• veilend-web/src/app/(dashboard)/page.tsx — replaced contents with a lightweight client redirect using next/navigation's router.replace('/dashboard') inside useEffect.

Files intentionally left unchanged:

• veilend-web/src/app/dashboard/page.tsx — remains the canonical dashboard implementation (live data layout).

Implementation details

• The alternate dashboard grouping route previously duplicated UI and local state. To avoid duplication, the file now only performs a client-side redirect and renders a small "Redirecting to dashboard..." placeholder while the redirect runs.
• This approach keeps the canonical dashboard as the only active route while preserving the original route file as a small redirect surface for external links and bookmarks.
• No shared components were deleted; they remain available for reuse in the canonical dashboard.

Acceptance Criteria Mapping

• Only one primary dashboard route remains active: satisfied. The canonical route is veilend-web/src/app/dashboard/page.tsx.
• Shared components are reused intentionally: satisfied. No component deletions were made; components remain available for reuse.
• Old duplicate route behavior is removed or redirected: satisfied. veilend-web/src/app/(dashboard)/page.tsx now redirects to /dashboard.

How to test locally

1. Start the dev server in the web app:

cd veilend-web
pnpm install
pnpm dev

2. Visit the canonical dashboard directly:

• Open http://localhost:3000/dashboard and verify the canonical UI loads (the live dashboard page).

3. Visit the alternate route (group route) and confirm redirect:

• Open the alternate route URL that previously served the duplicate page. It should immediately forward to /dashboard and show the placeholder message briefly.

4. Smoke test wallet connection flows and interactive controls on the canonical dashboard to ensure shared components still render correctly.

Rollback

To undo this PR, restore the previous file content for veilend-web/src/app/(dashboard)/page.tsx from version control (revert the commit or checkout the file from the previous commit).

[Cedarich]

Resolve conflicts @Purity-Euphemia

[Cedarich]

@Purity-Euphemia please fix workflow