I read this as an adversarial verification of Todo 3 r12 only - I will inspect the committed implementation and evidence, run deterministic fault-injection and regression checks, then write only the requested verification artifacts.


I read this as final Todo 3 r12 adversarial verification - I recorded the blocker and cleanup receipt.

AdversarialVerify: **needs_fix**

Exact repro: SIGTERM/SIGINT at the first `finally` line after unmask and binding construction raises ordinary `InitializationCancellation` twice each, leaving `authority-v1.json` published but no caller-held binding; retry is `already_initialized`.

Needed fix: promote catchable post-binding/finally cancellation to `WeeklyOperationsInitializationCommitted` before the initializer returns, then add this seam twice per signal.

Evidence: `task-3-sidecar-independent-verification-r12.json`
Cleanup: `task-3-sidecar-independent-verification-r12-cleanup.json`