[prathshenoy]

Summary

What:

• Update issue summaries when normal processing or recovery records an opening or closing.
• Preserve newer summaries when older transitions are replayed.

Why:

• Populate the read model introduced by the preceding storage PR. Recording issue history alone leaves those summaries empty; connecting accepted changes to the summary prepares the user-facing view without adding open-only mappings or an API yet.
• Repair partial writes without letting delayed workers undo newer changes. History can be retained before a summary write fails, so retries must update the summary even when the history already exists. Source request order and conditional writes keep an older opening from replacing a newer close or reopening.

Test Plan

• Add unit tests.

Revert Plan

• Revert this PR before its storage dependency. Operational issue state and history remain intact; summaries stop updating.

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