Problem
TODO.md contains a "previous public TODO backlog migrated to GitHub Issues on 2026-05-28" section listing issues #118–#130. The file's own preamble says it is only for "short-lived private scratch notes" — but this migration list has become a permanent fixture that references a mix of closed and obsolete issues.
Looking at those issues:
Leaving the migration list in TODO.md suggests these are pending tasks when most are done. Someone reading the file will be confused about what is still open versus what was closed years ago.
Fix
Remove the migration table from TODO.md. The issues are tracked in GitHub Issues where they belong. TODO.md can keep its preamble explaining that public product work goes to GitHub Issues, but the one-time migration record has served its purpose.
Alternatively, replace it with a one-line note: "The original TODO backlog was migrated to GitHub Issues in 2026; see open issues for current work."
Problem
TODO.mdcontains a "previous public TODO backlog migrated to GitHub Issues on 2026-05-28" section listing issues #118–#130. The file's own preamble says it is only for "short-lived private scratch notes" — but this migration list has become a permanent fixture that references a mix of closed and obsolete issues.Looking at those issues:
docs/linux-support.md)docs/basectl-ci.md)docs/check-parallelism.md)Leaving the migration list in
TODO.mdsuggests these are pending tasks when most are done. Someone reading the file will be confused about what is still open versus what was closed years ago.Fix
Remove the migration table from
TODO.md. The issues are tracked in GitHub Issues where they belong.TODO.mdcan keep its preamble explaining that public product work goes to GitHub Issues, but the one-time migration record has served its purpose.Alternatively, replace it with a one-line note: "The original TODO backlog was migrated to GitHub Issues in 2026; see open issues for current work."