[prathshenoy]

Summary

What:

• Apply issue updates in request order while builds and analysis continue concurrently.

Why:

• Prevent newer refreshes from discarding an earlier validation’s delayed final results. This can leave old failures open and prevent newly detected failures from being tracked.
• Preserve distinct issue occurrences in history and repair selection. A clean validation must close an earlier opening before the next validation can reopen the same failure and trigger a new repair.

Test Plan

• Add unit tests.
• Verify queue-head blocking and storage updates against MySQL.
• Verify issue-tracking completion and DLQ recovery end-to-end.

Revert Plan

• Pause admission and finish or safely abandon the new tracking jobs before reverting. Keep the additive database column; older code can ignore it.

Issue Links

• CODEM-607

Stack

1. fix(stovepipe): Retain request build associations #1011
2. fix(stovepipe): Track validations in order #1010