How do I reconcile our UR5e retained completion without counting it twice?

A job counter is retained beside it. We weren't reading it. I'm asking controls how that counter behaves over a restart before relying on it.

And what is your total supposed to count, Ben, physical accepted housings or completed attempts at checking them?

Toby, worth separating those. Even if every completion is matched correctly, a legitimate recheck mustn't quietly turn one housing into two finished pieces.

Toby, accepted housings. The report already links rechecks to the same housing, but this reconnect path adds a raw count outside that logic. It needs to use the reconciled result history too.

Test reconnect after a result was already saved, and after it arrived but saving failed. Same-looking retained signal, different work left for the application.

Ben, where will a result go if its counter and saved history cannot be matched? I would rather see an unresolved housing than an extra accepted one

Unmatched cases now go to review in the offline version. Known saved completion adds nothing on reconnect. Failed-save recovery and controller-counter restart behaviour remain under test. Thanks Toby for checking what the total means.

Try reopening that review case too. The reason and housing identity need to survive, not just a generic warning that sends the next shift back to asking you.