Our monitor counts a retained completion again after reconnect. The documented handshake exists, but I need the event tied to its actual bracket attempt without resending work or clearing the evidence.
Does the retained result include an attempt identity that remains unique across producer restart, and can the monitor compare it with durable processed history? The high signal alone cannot establish a new completion.
Producer retains a sequence within its run, but the monitor stores only that sequence, not the run identity. Its processed set also disappears on application restart. Both gaps are now with the interface owner.
Then test both repeats within one run and the same sequence in another run when the design is revised. Preserve uncertain old entries; a new identity scheme cannot retroactively identify them.