I read this as an authorized production recovery and immutable r71 live-upgrade execution - I’ll enforce the KST/event-driven gates, stop on any mismatch, and amend the production evidence with either a DoneClaim or exact no-replay blocker.


The preferred window is open and the immutable r71 roots are identified. I’m entering the fail-closed production gate now; any snapshot, verifier, or tombstone mismatch ends the run before restart.


The preferred gate expired at 00:05 before a valid snapshot completed. Per the hard window/no-replay rule, I’m stopping before restart, observer, or launcher and recording the exact fallback-boundary blocker.


I read this as production execution with strict no-replay gates - I stopped at the expired preferred window and finalized blocker evidence.

**Result:** `EXACT_BLOCKER_NO_REPLAY`

- Corrected gate reached `2026-09-02T00:05:23+09:00`, outside the permitted preferred window.
- No restart, cron action, observer run/update, launcher invocation, network action, or customer/provider mutation occurred.
- r70 remains active/running: PID `2447108`, `NRestarts=0`.
- All original r71 action roots remain absent.
- Final evidence: `.omo/evidence/nutricoach-telegram-checkin-stepper/task-10-r71-production.json`
- SHA-256: `f1ceeb586bdedd4a1c8a29d58ba0392a03293b7671d0925af5f8049d12b0ee32`
- JSON/LSP validation passed; debug artifacts removed.

Next valid boundary recorded in evidence: fallback `02:00-02:05 KST`, requiring a wholly fresh gate.


I read this as resuming the authorized live transaction in the validated 00:30-00:40 KST window - I’ll prepare and arm subscriptions now, wait event-driven if early, then enforce the fresh hard gate and execute each one-shot action exactly once or stop with no replay.


Preparation passed: addendum, original candidate/preseal, authority, ledgers, roots, and r71b tombstone digests are exact. Cron, action-root, observer, and service journal subscriptions have been armed; I’m waiting on the bounded monotonic deadline without polling and will not restart before 00:30.


The hard snapshot data is exact; the rejection was a local list-order assertion on the two unchanged draft hashes, not state drift. All zero-projection and ledger predicates passed. I’m issuing the single authorized restart now with the pre-armed subscriptions, targeting the next natural cron minute.


The one restart succeeded with new PID `3358966`, but no subscribed cron completion arrived within 120 seconds or by the 00:32 fallback tick. The addendum makes that a hard abort, so I’m stopping before observer checksum changes, observer oneshot, preflight, or launcher and capturing the safe no-replay state.


I read this as resuming the live r71 transaction - I executed until the mandatory post-restart gate failed, then stopped no-replay.

**Result:** `EXACT_BLOCKER_NO_REPLAY`

- 00:30 hard gate passed with zero Sep2 projection/send/update/retry eligibility.
- Single authorized restart executed: PID `2447108` → `3358966`.
- Fresh r70 failed startup: `WeeklyReminderStartupAuthorityIncident: weekly reminder canonical registration is unavailable`.
- `Restart=always` caused 26 automatic restarts. I stopped the unit to halt the crash loop.
- Gateway is now `inactive/dead`, PID `0`.
- No observer checksum update/run or r71 launcher invocation occurred.
- Customer, delivery, and Topic59 hashes remain unchanged.
- All r71 action roots remain absent; approval remains unused.
- Monitors and temporary artifacts were removed.

Final evidence:

`task-10-r71-production.json`
SHA-256: `e15d058ab868b510b34d2cef13c9468362cd9c2d81f1c989584d84a7ba3aea92`