The PLC completion is already high before the connection drops. Reconnect treats it as new and increments our plate count. I want the retained job identity reconciled with processed history, without clearing the signal blindly or resending an inspection just to obtain a fresh-looking result.
Compare the producer's retained attempt reference with the monitor's saved processed record. Does either identity or processed history change when the monitor reopens? A repeated observation is not another completed plate.
Producer retains a session-and-sequence identity. Monitor saves the detail row under it but increments a separate total on every reconnect, even when it finds the existing row. So the stored details and displayed count already disagree.
Yes. Developer reproduced the duplicate total in a replay and changed both screen and export to derive from identified reviewed item dispositions, retaining attempts separately. Repeated reconnect no longer adds the same plate.
Test a producer restart, monitor restart, old completion arriving after a newer attempt, and unknown identity before closing it. The duplicate counter finding is clear; the persistence and reference-lifetime cases still need their own results.
Those cases now pass against the retained identity rules: known repeats leave counts unchanged, old results stay with their attempt, and unknown references enter review. Quality's expected item totals match screen and export after reopen. Maintainer accepted this bookkeeping fix; the replay did not validate physical inspection.