Fix recovery deadline under scheduler delay

[r3dbars]

Summary

• start orphaned-recording recovery budget when the single-flight owner task actually begins
• replace the repeated-write wall-clock race with deterministic recovery-phase coordination
• prove delayed owner startup and repeated fresh writes without weakening recovery assertions

Exact-head proof

Head: 794152d
Base: 0465d5d

• build-deps.sh --force: PASS
• build.sh --no-open: PASS (signature, launch smoke, performance budget)
• run-tests.sh: PASS (13,393/13,393)
• run-integration-smoke.sh: PASS
• swift test --jobs 1: PASS (860 executed, 13 skipped, 0 failures)
• TranscriptionTaskManagerRecoveryTests: PASS (23/23)
• repeated-write stress: PASS (30/30)
• full QA bench deterministic software steps: PASS; overall INCOMPLETE only because duplicate app build was skipped after the separate exact-head build and current local artifact validation was warnings-only
• codex review --base origin/main: PASS, no actionable findings
• correctness: PASS
• security/privacy: PASS
• thermonuclear maintainability: PASS
• hosted Swift CI software checks: PASS

The earlier correctness finding that the first test snapshot was still scheduler-sensitive was accepted and repaired in 794152d. Hardware/UI/audio proof remains UNKNOWN.