[prathshenoy]

Summary

What:

• Apply a saved issue change and record its history before marking it complete.
• Resume partially completed changes without overwriting newer issue state.

Why:

• Finish partially completed issue changes without repeating them or losing their history. The issue update, history entry, and saved progress are separate writes, so a failure can happen between any of them. A retry checks what already succeeded, writes the missing history when appropriate, and clears the pending change only after both are complete.
• Stop an old worker from changing an issue after another worker has advanced it. Retrying with the original expected version, rather than adopting the latest version, prevents an outdated opening or closing from overwriting newer state. Keep this behavior separate from scanning and message handling so the write-and-retry rules can be tested on their own.

Test Plan

• Add unit tests.

Revert Plan

• Revert dependent controllers first, then this PR. No runtime consumer is enabled; the state and pending-change storage remain available but unused by issue tracking.

Issue Links

• CODEM-607

Stack

1. feat(stovepipe): Retain versioned issue state #942
2. feat(stovepipe): Save pending issue changes #943
3. feat(stovepipe): Apply saved issue changes #932
4. feat(stovepipe): Track issues in bounded passes #940
5. feat(stovepipe): Publish issue-tracking updates #939