This issue is staged for the repository's GitHub tracker cutover. Existing task instructions remain authoritative until the verified handoff.
Complete the repository tracker handoff.
What
Move deliverable tracking from the repository's .tasks/ ledger to GitHub Issues and its selected Project, preserving source records and a single active authority.
Why
The contribution guide already supplies the work-item form but leaves the legacy ledger authoritative. Published issues need a verified instruction and writer handoff before contributors can use them as the active queue.
Scope
Publish the reconciled issues visibly staged; prepare the repository instruction and source-map proposal; pause new legacy claims and drain acknowledged writers; have a human merge the reviewed proposal; compare final source variants while writers remain paused; verify issue identities and Project fields; probe discovery from the merged instructions with a fresh read-only session while staged; then record activation, remove staging notices and resume GitHub claims. Preserve historical ledger bytes. This concerns the repository backlog, not Pantheon's internal dispatch journal or runtime task tools.
Done when
Every retained source has an owning issue or explicit disposition; original records remain preserved; the reviewed instruction proposal is human-merged; known writers acknowledge the handoff; final source comparison and staged discovery succeed; activation evidence is recorded; staging notices are removed and subsequent claims use GitHub alone. A merge by itself does not satisfy activation.
Validation
Compare source hashes and published fields; read the exact merged instructions; record the fresh session's read-only discovery result and revision; verify no source write intervened before activation. Recheck ordinary pickup after activation before resuming work. Missing acknowledgements, source drift or failed discovery keep the transition staged.
Dependencies and decisions
Issue publication and proposal preparation are authorized before activation. Human merge and the final evidence checks precede activation. No product feature, runtime change or dual-write period is required.
Links
This issue is staged for the repository's GitHub tracker cutover. Existing task instructions remain authoritative until the verified handoff.
Complete the repository tracker handoff.
What
Move deliverable tracking from the repository's
.tasks/ledger to GitHub Issues and its selected Project, preserving source records and a single active authority.Why
The contribution guide already supplies the work-item form but leaves the legacy ledger authoritative. Published issues need a verified instruction and writer handoff before contributors can use them as the active queue.
Scope
Publish the reconciled issues visibly staged; prepare the repository instruction and source-map proposal; pause new legacy claims and drain acknowledged writers; have a human merge the reviewed proposal; compare final source variants while writers remain paused; verify issue identities and Project fields; probe discovery from the merged instructions with a fresh read-only session while staged; then record activation, remove staging notices and resume GitHub claims. Preserve historical ledger bytes. This concerns the repository backlog, not Pantheon's internal dispatch journal or runtime task tools.
Done when
Every retained source has an owning issue or explicit disposition; original records remain preserved; the reviewed instruction proposal is human-merged; known writers acknowledge the handoff; final source comparison and staged discovery succeed; activation evidence is recorded; staging notices are removed and subsequent claims use GitHub alone. A merge by itself does not satisfy activation.
Validation
Compare source hashes and published fields; read the exact merged instructions; record the fresh session's read-only discovery result and revision; verify no source write intervened before activation. Recheck ordinary pickup after activation before resuming work. Missing acknowledgements, source drift or failed discovery keep the transition staged.
Dependencies and decisions
Issue publication and proposal preparation are authorized before activation. Human merge and the final evidence checks precede activation. No product feature, runtime change or dual-write period is required.
Links