I read this as implementation - I’ll inspect the existing evidence conventions, build the isolated capture harness only under `.omo/evidence/task26`, then run its deterministic tests, dry-run, verifier, inventory, and seal checks.


I found the sealed lifecycle binding and archived delivery record, including message `232` and the durable send time `2026-08-17T14:47:21.037712+09:00`. I’m starting the isolated implementation now; the receipt will carry only identifiers, hashes, dimensions, timing, and the attestation—not durable text or customer answers.


The capture path is implemented with Linux `O_NOFOLLOW`, regular/single-link and mode checks, strict format framing, full decoder validation, bounded dimensions/bytes, complete-write loops, file/directory fsync, atomic no-replace publication, fixed binding metadata, and one-use semantics. I’m moving into verification and seal generation.


I read this as implementation - the isolated capture harness is complete, sealed, and verified.

Created:

`.omo/evidence/task26/task26-strict-rerun-customer-surface-capture-st_01a00ed6`

Status:

- 14 deterministic tests: PASS
- Dry-run: `PASS_AWAITING_FINAL_RUN_IMAGE`
- Independent inventory/seal verification: PASS
- LSP errors: 0
- Vault and final receipt absent, awaiting one operator image
- No live/customer, product, config, service, Git, plan, todo, or ledger actions

The exact future command and Mac-to-Linux placement requirement are in `exact-future-command.txt` and `README.md`. The screenshot must be privately transferred to an absolute Linux filesystem path and set mode `0600`; a chat attachment is not filesystem evidence.