I read this as a live recovery-executor operation - I will authenticate the actual gateway and journal state, run the prescribed single controlled replay only if every precondition holds, then verify and preserve redacted evidence.


I read this as a live recovery-executor operation - I completed the controlled Task23 recovery and verified the resulting state.

- Authenticated inbound: update `629525052`, message `124`, customer/chat `8527916639`, token `rc1_7rqk7vqD0xoDCmCthJgp3A`; journal HMAC `0a0ec3b8328e3c8371f011cdd6f635d0843b8bf17675640ec27d39b9dc4dd727`.
- Ran `task23-supersession replay --execute` once. Journal remains `CUSTOMER_BOUND`; successor `rb_f4L9siIlDP-R6IF27GwxdA` is `AWAITING_ACTIVATION`, generation `3`, SID hash `20c885...094a`. Old session remains immutable `EXPIRED`, generation `8`.
- Controlled stop reached `failed/failed`, PID/cgroup/holders/locks `0`; `reset-failed` normalized to `inactive/dead`. Started target once.
- Event-confirmed exactly one generation-29 owner card to `8693203710`: message ID `126`, send count `1`, committed provider receipt `620b88b039370fcf6beeb2c73d79d2908ef6b62fa896f2603f01cf29331d3fe4`, card hash `f7960a32b7135b9512850f69fc66d849d7da55f9d2766c122bdaf45464efc814`, label `새 복구 세션 승인`, callback `non2:owner_ok:29:IMiFeq1iFr1nf6ki9HsiDcNJcKuK2NAiIxfHGaPdCUo`.
- No owner action/callback occurred. Registry, consent, readiness, old outbox rows, and generic state are unchanged; activation/checkin/job/delivery downstream count is `0`.
- Gateway healthy: sole dualcoachtest poller PID `961027`, `active/running`; other user services unchanged.

Redacted evidence: `.omo/evidence/task23-st_019ff603/2026-08-12T2155-task23-live-executor.redacted.json`
SHA-256: `710857794b07735c7a4b915f1ef0238544ab7a99df6c48fed70c1946866fc243`

Evidence is O_EXCL/fsync sealed with directory mode `0500` and files `0400`. The filesystem denied the kernel immutable attribute (`chattr`), so it is permission-sealed rather than kernel-immutable.