docs/plans/2026-05-04-slate-issues-gitcrawl-rebuild.md
Rebuild docs/slate-issues from a live gitcrawl mirror instead of the old
pre-v2 frozen snapshot. The output should be better triage, not a prettier copy
of the April ledger.
gitcrawl is the archive-first source for candidate discovery, neighbors,
clusters, and stale/duplicate pressure.682-issue snapshot as the active truth if live data
disagrees.Fixes #... claims limited to issue-level proof in
docs/slate-v2/ledgers/issue-coverage-matrix.md.docs/slate-issues/open-issues-ledger.mddocs/slate-issues/open-issues-dossiers.mddocs/slate-issues/test-candidate-map.mddocs/slate-issues/benchmark-candidate-map.mddocs/slate-issues/issue-clusters.mddocs/slate-issues/package-impact-matrix.mddocs/slate-issues/requirements-from-issues.mddocs/slate-issues/roadmap-from-issues.mddocs/slate-issues/triage-close-queue.md| Phase | Status | Output |
|---|---|---|
| 1. Mirror refresh | complete | Fresh gitcrawl sync for ianstormtaylor/slate open issues and comments. |
| 2. Cluster build | complete | gitcrawl cluster output plus weak-cluster and singleton gap notes. |
| 3. Gap audit | complete | Current docs vs live mirror deltas: closed, new, missing, stale, weak duplicate candidates. |
| 4. Corpus rebuild | complete | Updated docs/slate-issues summary docs and generated/detailed ledgers. |
| 5. V2 claim reconciliation | complete | Issue coverage matrix claims left unchanged; new live rows stay untriaged until issue-level proof. |
| 6. Verification | complete | Formatting, row/count scripts, bun run completion-check. |
2026-04-02 frozen 682-issue snapshot.630 open issues and 29 open PRs:
659 open threads total.1856 comments/reviews, embedded 659 rows, and produced
617 clusters.28 clusters are multi-member; 589 are singletons. Raw gitcrawl
clustering is useful for candidate discovery but too conservative for the
Slate v2 architecture taxonomy.#6051, #6053.54; GitHub confirms all are closed.untriaged-live-new.