Roadmap stores stale issue state after index retirement
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 423
- Forks
- 53
- Avg merge
- 20h 26m
- Merged PRs (30d)
- 310
Description
Row: ENG-RECORD-CONFLICT-SURFACES
.agents/roadmap_v1.md still stores a 98-row ## Open issues table after the tracked issue index was retired. GitHub is the live issue authority, and scripts/agent-issue-index.py --refresh already renders an untracked snapshot for offline gates.
The stored table is stale on current origin/main: only 8 of its 98 issue numbers remain open, and none of the 29 portfolio rows directly references a current open issue. The table also describes the retired append-only merge=union design as current behavior.
This row must remove the stored issue projection, point readers to the existing generated snapshot, and preserve the ordered portfolio table. It must also reconcile stale lifecycle projections and close issues whose described code or record no longer exists.
The campaign includes record gates discovered by the audit. .github/workflows/ci.yml still invokes the deleted append-only-index test. Issue #2372 combines two independent compile defects and must split by owning row before repair.
Acceptance:
.agents/roadmap_v1.mdstores no issue rows.- The roadmap names GitHub as the live issue authority and gives the refresh command.
- The generated snapshot stays untracked and offline-first.
- Ownership checks stay diff-scoped. No global unowned-issue count gate is added.
- Duplicate claimable IDs and vague
PARTIALrows are reconciled without converting landed-but-open work toDONE. - Obsolete issues close with exact code, commit, or falsifying evidence.
- The issue-index renderer tests, record gates, live-row audit, focused compile gates, and full preflight pass.
One pull request carries the committed spec first and implementation commits after it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .agents/roadmap_v1.md and scripts/agent-issue-index.py --refresh, then inspect .github/workflows/ci.yml and the issue-index renderer and record-gate tests. Trace the live-row audit and focused compile gates before changing the roadmap or lifecycle records. Done means the stored projection is removed, the generated snapshot remains untracked and offline-first, stale records are reconciled with evidence, and the stated preflight checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, github-actions, python
- Domain
- ci-cd, devtools, documentation, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100