[prathshenoy]

Summary

What:

• Apply one issue’s open or closed status and record its transition history with retry-safe conditional writes.

Why:

• Keep partial failures recoverable without a transaction across records. If the issue changes but recording history fails, a retry can use the retained cursor and transition facts to finish the same history entry.
• Reject work from a worker that resumes after another worker has moved on. Check the queue revision after reading the issue and retain closed rows so an old write cannot recreate a missing opening.

Test Plan

• Add unit tests.

Revert Plan

• Revert dependent PRs first, then this PR. Issue-tracking consumption remains disabled, so reverting does not interrupt an active issue-tracking worker.

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