[prathshenoy]

Summary

What:

• Add queue-scoped persistence for accepted analysis sources and pending or completed reconciliation passes.
• Expose point-key reads and version-guarded writes without enabling runtime writers or adding reconciliation logic.

Why:

• Retain the source-order boundary and unfinished work across retries or restarts, including when no issues remain open.
• Keep persistence independent of the controller's ordering and issue-transition decisions.

Test Plan

• Add unit tests.
• Verify durable progress, queue isolation, identifier boundaries, and competing guarded updates against MySQL.

Revert Plan

• Revert this PR. No runtime writer is enabled; the additive progress table can remain unused without affecting existing validation.

Issue Links

• CODEM-607

Stack

1. feat(stovepipe): Store issue-tracking progress #930
2. feat(stovepipe): Add issue-tracking controller #932
3. feat(stovepipe): Publish issue-tracking updates #939