fix(console-ui): make sidebar navigation native

[Gajesh2007]

Summary

• Replaces next/link for sidebar shell navigation with native anchors so clicks are no longer captured by the broken client-router path.
• Keeps active-route styling and mobile sidebar close behavior intact.

Before

flowchart LR
  subgraph Behavior_Before[Behavior]
    U1[User clicks Stats in sidebar] --> L1[Next Link delegated click handler]
    L1 --> P1[preventDefault on anchor]
    P1 --> R1[Client router does not push/fetch]
    R1 --> S1[URL stays on current route]
  end
  subgraph Code_Before[Code]
    C1[Sidebar nav item] --> C2[next/link Link]
    C2 --> C3[Next app-router client navigation]
  end

Loading

After

flowchart LR
  subgraph Behavior_After[Behavior]
    U2[User clicks Stats in sidebar] --> A1[Native anchor href=/stats]
    A1 --> B1[Browser performs route load]
    B1 --> S2[/stats renders and Stats is active]
  end
  subgraph Code_After[Code]
    C4[Sidebar nav item] --> C5[plain a href]
    C5 --> C6[closeSidebarOnMobile only]
    C6 --> C7[Browser-native navigation]
  end

Loading

Test plan

• npm run build passed from the fix worktree. Because disk was full, validation used the existing dependency tree with a temporary Turbopack root override that was removed before commit.
• npx eslint src/ passed with 0 errors; existing repo warnings remain.
• Browser proof on http://localhost:3017: clicking the actual Stats sidebar link changed location.pathname to /stats and made Stats active.

Made with Cursor

---

^{Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
d-inference	Ready	Preview	Jun 24, 2026 12:21am
d-inference-console-ui-dev	Ready	Preview	Jun 24, 2026 12:21am
d-inference-landing	Ready	Preview	Jun 24, 2026 12:21am

[github-actions]

No security-relevant changes detected — this PR modifies only console-ui/src/components/Sidebar.tsx, which is a UI layout component not covered by any threat model affected_files pattern.

No trust boundaries are touched by this diff. A sidebar component that handles navigation state, display logic, or styling does not introduce new attack surface unless it meets one of the following conditions (none of which are visible without seeing the actual diff):

• It renders user-controlled content without sanitization (→ T-019 / XSS blast radius)
• It reads from or writes to localStorage in a way that interacts with auth state or chat history (→ T-018, T-001)
• It constructs URLs or makes fetch calls using client-supplied input (→ T-017 / SSRF)
• It conditionally hides/shows privileged UI based on client-side auth state alone (→ T-020)

If the diff does any of the above, re-run this review with the full file content. Otherwise no threat model update is needed.

---

🔐 Threat model: docs/threat-model.yaml · Updates on each push to this PR

[ethenotethan]

Automated Code Review — Layr-Labs/d-inference#

Verdict: REQUEST_CHANGES

Security — ✅ No issues found

Performance — 1 finding(s) (1 blocking)

• 🟡 [MEDIUM] console-ui/src/components/Sidebar.tsx:44-46 — Window width check repeated on every mobile click instead of using media query or cached value
  • Suggestion: Use CSS media queries for responsive behavior or cache window.innerWidth check with resize listener to avoid repeated DOM queries

Type_diligence — ✅ No issues found

Additive_complexity — 1 finding(s)

• 🔵 [INFO] console-ui/src/components/Sidebar.tsx:22 — useRouter import is no longer used after removing Next.js Link components
  • Suggestion: Remove unused useRouter import from next/navigation

2 finding(s) total, 1 blocking. Verdict: REQUEST_CHANGES.

🤖 Automated review by Centaur · DAR-186

[ethenotethan]

🟡 [MEDIUM] ⚡ Window width check repeated on every mobile click instead of using media query or cached value

💡 Suggestion: Use CSS media queries for responsive behavior or cache window.innerWidth check with resize listener to avoid repeated DOM queries

📊 Score: 2×4 = 8 · Category: Repeated work

[ethenotethan]

🔵 [INFO] 🧩 useRouter import is no longer used after removing Next.js Link components

💡 Suggestion: Remove unused useRouter import from next/navigation

📊 Score: 2×3 = 6 · Category: dead code