I read this as a read-only final F4 audit - I’ll trace the exact v38/Task27 real-surface proof, verifier/bootstrap, supplemental cleanup receipt, and current stopped/no-delivery state, then return a strict PASS/FAIL with gaps.


The evidence chain is located and the supplemental receipt hash matches exactly. I’m now checking the delivered root directly and reconciling the original Telegram lifecycle/cleanup timestamps with the supplemental archive-only operation and current inactive profile state.


I read this as a read-only final F4 audit - I verified the exact v38 candidate, historical Telegram proof, supplemental cleanup, and current inactive state.

## Verdict: PASS

**F4 may be checked.**

### Exact evidence

- Candidate: `d1109d8f78aaccf949ec4f664d9e62584c3cca33032030518bc3e2d712239112`
- Delivered root:
  `.omo/evidence/task26/task26-combined-v38-delivered-st_01a019d7`
- Direct verifier rerun:
  - `TASK26_INDEPENDENT_CANDIDATE_PASS`, exit `0`
  - Delivered seal: `54be54cf89720057486596a21941ec5d456a1c54148f66dbde0475503a752f67`
- Direct bootstrap rerun:
  - `TASK26_FROZEN_BOOTSTRAP_PASS`, exit `0`
  - `ACTUAL_INSTALLED_GOLDEN_PATH_PASS`

### Real Telegram lifecycle

- Task24 evidence SHA:
  `7431b043f1aa9f67481692ed3555f9072f091984b931e77041ee5aa50d2258b4`
- It records:
  - owner explicit Send;
  - customer/chat `8527916639`;
  - exactly one `sent_audited` delivery;
  - provider message ID `157`;
  - zero duplicate customer deliveries.
- Task25 terminal evidence SHA:
  `30275bb8a9d0637fb4b46889672105836f18baa64e02270f1a4728efe2d6378d`
- Task25 archive remains bound to:
  - archive `2009ac177177839cefddb98f285e27fa`;
  - digest `644d74b05bc8115f9e3aeeba035188da195a7de18f1bc737648931d64bf43bcf`;
  - 23 verified scopes.
- Both historical files still match their recorded hashes after supplemental cleanup.

### Supplemental cleanup

- Exact receipt SHA matches:
  `13b28b5745cf1fb6e8aa9457f14ad86dbf972c3c203394e2fd919d99b7bf659d`
- Status: `COMMITTED`
- Operation: `005a3c3f9897e2d298a9a7409759509e`
- It only copied, verified, archived, and pruned:
  - `telegram-publication-outbox-v1`
  - `telegram-staff-membership-v1`
- Source and archived digests match exactly.
- Archived receipt is byte-identical to the delivered receipt.
- Archive manifest SHA matches:
  `636acca796ef627cc488c85d5cbc79894eaaa1ee68bbd8660aaf7692d4b9b7e2`
- Archive has zero symlinks and zero writable paths.
- The controller contains no activation, delivery, Telegram, provider, or network operation in its execute path.

### Current live state

- `hermes-gateway-dualcoachtest.service`: `inactive/dead`, `MainPID=0`
- Matching live processes: `NONE`
- Customer remains `enabled: false`
- AI consent remains `granted: false`
- `delivery_enabled: false`
- Operational outbox and membership directories are absent.
- Supplemental receipt reports zero active-target matches.
- No service start, activation, Telegram action, provider action, or customer delivery occurred during cleanup.

### Gap

The old `.omo/evidence/task27/receipt-hashes.sha256` is stale: its `task27_final_cleanup_controller.py` hash no longer matches and it does not cover the supplemental receipts. This was already disclosed by F4/F5. It is a final-handoff manifest gap, not an F4 real-surface-proof failure.

The supplemental archive preserves local residue and leaves the immutable Task24/Task25 real-surface evidence unchanged.