[prathshenoy]

Summary

What:

• Maintain open-issue lookup entries during normal issue tracking and recovery.

Why:

• Populate the lookup needed to list open issues without scanning closed summaries. Storage support alone does not maintain those rows as issues open, close, and reopen.
• Repair partial writes without restoring older openings. A summary can be saved while its lookup write fails, so redelivery must repair the lookup even when history already exists. Use the latest persisted summary so an older delivery cannot make the lookup follow an outdated transition.

Test Plan

• Add unit tests.
• Verify issue lifecycle and lookup repair against a real MySQL database.

Revert Plan

• Revert this PR. Issue state, history, and summaries continue updating; lookup maintenance stops, and no public API depends on it yet.

Issue Links

• CODEM-607

Stack

1. feat(stovepipe): Add issue summary storage #982
2. feat(stovepipe): Materialize issue summaries #983
3. feat(stovepipe): Add open issue lookup storage #984
4. feat(stovepipe): Maintain open issue lookups #986
5. feat(stovepipe): Add open issue listing #988
6. feat(stovepipe): Expose open issue listing #990
7. feat(stovepipe-web): Show open issues #993