Create GitHub repository analytics dashboards

Create single-repo GitHub analytics dashboard with optional live refresh

Open-source project health dashboards where public GitHub data aggregation and optional refresh scheduling are needed.

• · GitHub owner/repo identifier (required)
• · DESIGN.md or Soft Paper Workspace visual defaults
• · public GitHub API data: stargazers_count, forks_count, watchers, open_issues_count
• · top N contributors (pagination via GET /repos/{owner}/{repo}/contributors)
• · recent issues and pull requests (GitHub Search API or paginated GET)
• · growth/delta metrics (estimated or GraphQL if available)

• · single-screen HTML dashboard (self-contained index.html OR live-artifact source set)
• · repository header: name, fullName, url, description, language, license, created, lastUpdated
• · metrics: stars, forks, contributors, issues, pull requests (display-ready totals + small deltas)
• · top 5–8 contributors with login, avatar, contributions count
• · recent activity rows: title, typeText, typeClass, label, labelClass, author, authorAvatar, updated
• · optional: example-data.json, artifact.json, provenance.json (for live-artifact contract)

• · GitHub REST API (public data: /repos/{owner}/{repo}, /repos/{owner}/{repo}/contributors, /repos/{owner}/{repo}/issues, /repos/{owner}/{repo}/pulls)
• · GitHub Search API (for total counts and filtering)
• · GitHub GraphQL (optional, for historical growth metrics)

• · owner/repo identifier resolved (ask one concise question if missing)
• · DESIGN.md active OR Soft Paper defaults fallback
• · Public GitHub repository (no private repos)

• · Missing owner/repo identifier at start (should ask one question)
• · Scope creep to multiple repositories (specify this is single-repo v1)
• · GitHub data not normalized into dashboard structure (raw JSON exposed)
• · Growth deltas marked estimated but not documented in provenance.json
• · Contributors paginated but page 1 only, total estimates not labeled as such
• · Auth tokens or rate-limit headers stored in output
• · Private metadata included in export (violates privacy)
• · Stargazer event snapshots used without provenance documentation

• · Resource map with four files: template.html, example-data.json, artifact.json, provenance.json
• · Explicit GitHub API endpoint list (GET /repos/{owner}/{repo}, /contributors, /issues, /pulls, Search API)
• · Contributor pagination documented with top-N selection
• · Provenance system for synthetic/estimated metrics
• · Soft Paper visual defaults (warm off-white, white rounded panels, fixed left sidebar, compact KPI cards, pastel pills, dense tables, low-contrast hairlines)
• · License and language fields in repository metadata
• · Activity row structure fully specified (title, typeText, typeClass, label, labelClass, author, avatar)