[prathshenoy]

Summary

What:

• Define queue-scoped notifications for new failure observations and successful final analysis, without enabling publishers or consumers.
• Expose persisted failures for one build in bounded, cursor-based pages with required build and task identities.

Why:

• Prepare ordered issue reconciliation while keeping build polling independent and messages small, without adding tables or serialized failure collections.

Test Plan

• Add unit tests.
• Verify pagination, queue/build isolation, byte-exact ordering, and identifier boundaries against MySQL.

Revert Plan

• Revert this PR. The contracts and reads are not wired into runtime workflows; no schema migration or data removal is required.

Issue Links

• CODEM-607

Stack

1. feat(stovepipe): Add issue lifecycle history #923
2. feat(stovepipe): List open issues in pages #924
3. feat(stovepipe): Define issue-tracking handoff #925