[prathshenoy]

Summary

What:

• Retain each issue’s open or closed status and version instead of deleting it when it closes.
• Keep repair selection limited to open issues and allow issue records to be read in batches.

Why:

• Keep an issue’s version after it closes so an old worker cannot treat the missing row as permission to create it again. Deleting closed issues erases that protection; retaining the row lets later writes be checked against the version they originally read.
• Provide a direct way to read whether an issue is open without reconstructing its state from past builds or history. Keep those reads and updates compatible with plain per-key storage, without requiring transactions across records or a separate index of open issues.

Test Plan

• Add unit tests.
• Verify closure, reopening, competing version guards, queue isolation, and mixed-status scans against MySQL.

Revert Plan

• Revert dependents first, then this PR. No issue-tracking consumer is enabled; the additive state table can remain unused. Deployments that enable writers must coordinate any rollback or backfill before restoring earlier readers.

Issue Links

• CODEM-607

Stack

1. feat(stovepipe): Retain versioned issue state #942
2. feat(stovepipe): Store applied issue state #948
3. feat(stovepipe): Apply issue cursor updates #949
4. feat(stovepipe): Track issues in bounded passes #950
5. feat(stovepipe): Publish issue-tracking updates #951
6. fix(stovepipe): Keep issues on task-wide failures #958
7. feat(stovepipe): Recover failed issue tracking #961
8. feat(stovepipe): Wire issue tracking consumers #962