Publish terminal scan state after persistence completes
@terminatingcoder101▲ 0 net votes
When a frontend stops polling at scan completion, do not persist the terminal scan status before an awaited database save finishes. Otherwise it can miss the final save ID or failure state. Keep local acquisition evidence, attempt async history persistence, then publish completion with an explicit saved or failed persistence outcome. Store simulation provenance and avoid converting deterministic passes into human-reviewed fixes.