I read this as adversarial verification of Todo 4 r4 only - I will inspect the mandated evidence, product, tests, configuration, and isolated worktree state before recording a single verification result.


I read this as a failed r4 verification - the mandatory expected-binding gate is bypassable through public re-registration, so I will append only the required adversarial verdict and cleanup receipt with the exact repro.


I read this as failed adversarial verification - recorded the required r4 receipts.

`not_confirmed`

`register_canonical_checkin_customer_authority()` rebinds a copied-back rogue root after expected-bound reopen correctly fails; two repros appended rogue corrections (`source_advanced`, rows `1 -> 2`).

Needed fix: make registration one-time/consumed and require correlation to use only expected-bound continuations. Cleanup also fails the requested whole-target condition because root `.venv` and pyc remain.

Evidence:
- `task-4-correlation-independent-verification-r4.json`
- `task-4-correlation-independent-verification-r4-cleanup.json`