docs: align dashboard page with Issue #3 — Vite + react-ts decision

[KoxyG]

Updates the PG Atlas Dashboard doc to match the decision from Issue #3.

Changes:

• Replaced the previous "Implementation Options" section (Streamlit, Dash, React/Next.js) with a "Technology Decision" section that records the chosen approach.
• Decision: Option C — React/Next.js (or Vite) for the dashboard. No Panel prototype in the chosen path.
• Rationale: TypeScript SDK dogfooding, contributor accessibility (React/TS ecosystem), and a scoped v0 (leaderboard + basic PG detail pages; graph explorer deferred to v1).
• Ownership: KoxyG — Next.js or Vite, coordinating with the team to finalize features.
• Trimmed "Open Questions" to items still open (graph lib, hosting, analytics, mockups).

Resolves the doc drift noted in #3 (dashboard page now consistent with the Build submission and issue resolution).

[aolieman]

Very clear decision, thanks. It's okay to leave Panel out of this page since it's only part of our dev team process, and not a component that is intended to go into production. This way, we have a clearer separation of concerns, and the Dashboard page matches the component repo boundaries.

There is only one disagreement to flag: whether we need the sub-graph explorer on Project detail pages as an interactive validation instrument of the criticality score, for voters and PG maintainers.

Most of the feedback I left, I also intend to address in an upcoming commit to this PR.

[aolieman]

Looks good to me! If you're also happy @KoxyG, please squash merge this PR.

[KoxyG]

Looks good to me! If you're also happy @KoxyG, please squash merge this PR.

Merging is blocked from my end

[aolieman]

Merging is blocked from my end

Sorry, that was my bad. I didn't see one of the comments was marked as unresolved, nor did I know this would block the merge. Please go ahead and approve & squash merge.

[KoxyG]

good to go