[prathshenoy]

Summary

What:

• Publish issue-tracking refresh and finalization notifications after build analysis persists its results.
• Add the publication route without enabling issue-tracking consumption.

Why:

• Give issue tracking a reliable handoff from build analysis. Publishing after persistence ensures it can read the build’s recorded issues, and a failed publish can retry without losing the handoff. Require a complete cumulative terminal result so finalization does not depend on an earlier worker finishing its writes.
• Keep terminal recovery separate from this rollout. Registering only the publication route allows the processing layers to be reviewed without starting a consumer whose recovery policy is not yet wired.

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