Implement GitHub OSS dashboard pack v1

ID	DASHBOARD_FACTORY-IMPLEMENT_GITHUB_OSS_DASHBOARD_PACK_V1
Status	not_started
Priority	p1
Milestone	m4-v1-0-launch
Owner	data-analysis-evangelist-ai-training
Initiative	github-oss-activity-dashboards

Problem

Implement the interlinked GitHub activity dashboard pack, including contributor drill-through pages and a real example repo or org deployment.

This task is the user-facing proof of the whole initiative.
It depends on:
the topology and metric contract being stable
the extraction pipeline producing the needed static data tables
the GitHub Actions + Pages publisher being usable
dashboard-linking-v1 for the cleanest cross-board navigation model
The dashboard suite should feel like a coherent product for OSS maintainers, not just a technical demo.
A real reference deployment matters: the initiative should prove that an actual repo or organization can publish the site with GitHub-native tooling only.

Build a toy example only - Fastest route to screenshots. - Too weak to validate adoption, workflow ergonomics, or data quality.
Recommended: implement the full v1 pack and prove it on a real OSS repo or organization - Best validation of the dashboard IA, extraction contract, and publishing flow together. - Ensures the contributor drill-through model works in realistic data.
Wait for every optional board before implementation - Could produce a broader launch. - Creates unnecessary delay and increases the chance of scope creep.

Build the five v1 boards from the initiative spec.
Wire all contributor references to the canonical contributor detail board.
Validate the pack against real GitHub activity data, including edge cases like bots and sparse contributors.
Publish a reference deployment through GitHub Pages.
Capture gaps, v1.1 follow-ups, and any changes needed to improve the add-on adoption path.