DashboardShell's active-nav-item highlighting uses exact pathname equality, so nested routes never highlight their parent section

[chonilius]

src/components/dashboard/DashboardShell.tsx determines the active sidebar item with:

const active = pathname === item.href;

This is an exact string match. The maintainer/sponsor nav includes items like
{ label: "Bounty pipeline", href: "/issues", icon: GitPullRequest } and
{ label: "Milestones", href: "/milestones", icon: Milestone }. When a maintainer
navigates from the pipeline board into a specific bounty (/issues/abc123, reached via
PipelineBoard.tsx's own links), pathname becomes /issues/abc123, which is not
=== "/issues" — so "Bounty pipeline" loses its active/highlighted state exactly while
the user is drilled into a page that's conceptually still part of that section, with no
other sidebar item taking its place.

The result is a sidebar that appears to have "nothing selected" whenever the user is on
any nested route under a top-level nav destination, which is a common and expected
navigation state (viewing one bounty out of the pipeline) that this exact-match check
doesn't account for.

Suggested fix: use a prefix check for non-root items (pathname === item.href || pathname.startsWith(item.href + "/"))
so nested routes keep their parent section highlighted, while still using exact matching
for /dashboard/* overview links so they don't stay highlighted while browsing unrelated
sections.

[tdlxgpp]

I'd like to work on this.

[Baddo0906]

@Baddo0906 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Interested in working on this. I'll ensure the implementation is clean, tested, and aligned with project standards.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Baddo0906 to this issue.

[koro511]

@koro511 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer, after looking through the issue, I understand the problem and the desired solution. Please consider assigning this task to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @koro511 to this issue.

[miraclesonly]

@miraclesonly has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I will like to work on this issue. please assign.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @miraclesonly to this issue.

[drips-wave]

Congratulations, @miraclesonly! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @miraclesonly: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[tdlxgpp]

Hi maintainers — heads up: I already opened PR #302 for this issue before the Stellar Wave assignment (#302). If you are proceeding with @miraclesonly, I’m happy to coordinate; otherwise I can update PR #302 with any requested changes.