Skip to content

Epic 02: Canonical GitHub Stars Automation Hardening #42

Description

@primeinc

Goal

Take primeinc/github-stars from brittle/failing Actions automation to a canonical, evidence-verified, self-validating pipeline.

Scope

  • Inventory canonical repo sources and ../refs if present in the execution environment.
  • Capture latest failed GitHub Actions logs and bind root cause to direct evidence.
  • Reconcile workflow topology between docs and actual .github/workflows/* files.
  • Harden token/secret behavior for star fetching.
  • Replace implicit repo-state handoff with explicit artifact/job handoff.
  • Gate manifest/schema validation.
  • Gate web build validation.
  • Canonicalize generated data flow from GitHub stars to published site output.
  • Repair stale agent/planning docs.
  • Improve workflow summaries and proof artifacts.
  • Define one final acceptance run proving the system works.

Direct Evidence Already Known

  • AGENTS.md describes this as a GitHub Actions-based automation system and says core logic lives in .github/workflows/*.yml.
  • AGENTS.md documents numbered workflows: 01-fetch-stars, 02-sync-stars, and 03-curate-stars.
  • .github/workflows/01-fetch-stars.yml exists and fetches starred repositories, writes .github-stars/data/fetched-stars-graphql.json, uploads an artifact, and commits results.
  • .github/workflows/02-sync-stars.yml exists and fails if .github-stars/data/fetched-stars-graphql.json is absent.
  • web/package.json exposes build/lint scripts.
  • web/vite.config.js builds to ../docs.
  • web/src/App.jsx loads data.json and sorts by user_starred_at.

Known Gaps / Blockers

  • Latest failed Actions run logs must be captured before exact root cause is claimed.
  • ../refs must be inventoried before any claim that it was used canonically.
  • The documented third workflow must be confirmed as present, renamed, deleted, or stale documentation.

Acceptance Criteria

  • All sub-issues are completed with proof artifacts.
  • Every material claim is labeled as Direct evidence, Weak inference, Unsupported, Blocked, or Contradicted.
  • No issue is closed from checklist text alone.
  • Final successful Actions run proves fetch, sync, validation, build, and generated outputs.
  • Docs match actual workflow/source topology.
  • Missing or unavailable sources are explicitly marked instead of guessed.

Child Issues

Child issues will be linked here after creation.

Definition of Done

The repo has a documented, reproducible, validated pipeline with clear failure diagnostics and one final proof-backed acceptance run.

Metadata

Metadata

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions