The application kept a unique request identity before sending, and the receiver retains a result under that identity. Our startup helper ignored both and only checked pending. I've held its automatic resend while we review reconciliation.

Check what the retained result means under the supported interface agreement before treating an identity match as completed verification.

And make the held startup state visible while that lookup is running. Starting reconciliation should not briefly make the bracket appear ready for another request.

Could the same identifier be reused after reinstalling or restoring the application? I've seen a familiar number look much more convincing than its record deserved. Worth checking the identity lifetime before trusting a retained result.

The two software owners checked identity lifetime and the retained response contract. This result belongs to the original request and records completed verification. We can reconcile this case without resending; uncertain or missing identities will remain held.

Has that conclusion been saved durably, or is it only displayed after the lookup?

Saved and linked to the retained response, with no new verification request sent. The developer is now testing failure while saving that reconciliation so a second startup cannot treat it as untouched work.

Keep the original interrupted local record in the audit history; reconciliation explains it rather than making the crash disappear.

Does a failed reconciliation lookup leave a useful reason and escalation route, not just an indefinite spinner? The next shift shouldn't have to work out whether waiting longer is the approved response.

The offline tests now show held with a reason after failed lookup or failed save, and a saved reconciliation survives restart. The original request history is intact. Unknown cases have a named review route rather than a retry shortcut.

That answers my identity concern for this case. Is the normal startup launcher using this version too, or are you still exercising the development copy?

Still the development copy. Normal-launch verification and the covering-maintainer exercise are the remaining tasks. The old bracket result is reconciled, but I'm leaving the general startup change short of release until those checks are done.

Please return with the normal-launch result. A recovered request and a released startup fix are different outcomes.