I read this as a full release-and-deploy operation - I’ll verify the fixed profile delta, run and bind all release gates, seal a successor candidate, install it into a new isolated runtime, and launch a fresh v7 only if every preflight succeeds.


The authoritative fixed source and prior release machinery are present. I’m now reconstructing the exact predecessor/candidate contract and v6 shutdown state before creating any artifact or mutating Telegram state.


The delta is exactly the four authorized files, with no added or removed source. I’m beginning the release gates and fresh wheel build now; because the profile wheel changes runtime behavior, I’ll also rerun Hermes/profile compatibility plus the full gateway suite rather than relying on predecessor receipts.


All functional gates are green: focused compatibility 296/296 and full gateway 8,191 passed with 59 skipped. One attempted “full installed profile” harness was invalid because its copied test tree omitted packaged policy fixtures; I’m excluding that setup failure from release bindings and using the valid installed Hermes wheel gate plus direct installed-package regression/origin checks in the new runtime. I’m now sealing only the verified source and successful receipts.


The successor is sealed with candidate `74f5df5c…`, product `062fb6b6…`, unchanged Hermes wheel `c092432b…`, and new profile wheel `8d67ed55…`; inventory remains 5,493 entries with exactly four profile changes. I’m moving to the fresh offline standard install and installed regression attestation before any live launch mutation.


The first offline resolver attempt stopped before installing any product because one pinned dependency was present only as an extracted cache entry, not a resolver-visible wheel. I’m discarding that empty venv and rebuilding a local dependency wheelhouse from the already sealed standard runtime’s RECORD-verified distributions, then performing a clean `pip --no-index` install into a newly recreated venv; the old runtime remains untouched.


The fresh runtime is now `READY_ISOLATED_RUNTIME`: exact direct URLs and artifact hashes, full RECORD parity, isolated imports, `pip check`, CLI help, and installed exact-phrase attestation all pass (`넵 남성입니다` → `male` → `owner_review`). The v7 launcher dry-run also proves zero mutations against the empty baseline; I’m executing its one-use path now.


I read this as completing the successor deployment - it is sealed, installed, and stopped at fresh `READY_CUSTOMER_CLAIM`.

- Status: `READY_CUSTOMER_CLAIM`
- Candidate: `74f5df5c6ccc96451a76b0562dc0fa187be745880f30955c5cf4486643e224b3`
- Product: `062fb6b69adb84b0030b1edae334f3bc772a7920cd4a01bd8cad5846f0137e14`
- Profile wheel: `8d67ed554b3b6237ab2c09bd1b44a53edb618679c6b90fc921a0cba6751ff1d9`
- Hermes wheel: `c092432b2ed9af300342c5d402781cd16d45e21b0f239a047936d9106d675228`
- Evidence: `/home/cube/projects/richard/traning coach/.omo/evidence/task26/task26-sex-basis-successor-st_01a01309`
- Runtime: `/home/cube/.hermes/profiles/dualcoachtest/.strict-runtime/062fb6b69adb84b0-v7`

Verification:
- Exact four-file profile delta; zero added/removed source
- Profile focused: 51 passed
- Profile full: 705 passed
- Compatibility: 296 passed
- Full gateway: 8,191 passed, 59 skipped
- Installed Hermes: 55 passed
- Ruff, basedpyright, compileall: pass
- Installed regression: `넵 남성입니다` → `male` → `owner_review`
- Direct URLs, RECORD parity, imports, `pip check`, CLI help: pass

Invite:
- Message ID: `295`
- Created: `2026-08-18 13:22:23 KST`
- Expires: `2026-08-18 13:52:23 KST`
- Exactly one invite sent
- Customer: `task26_claim_20260818042223_9ea2da0b`
- Session: `cb_16TPvCuXPB7UodfLwRTQYw`

Services:
- Gateway: `hermes-gateway-dualcoachtest-strict-062fb6b6-v7.service`, PID `915634`
- Observer: `dualcoach-lifecycle-observer-74f5df5c-v7.service`, PID `915632`

Exact user action:

> Customer 8527916639: open the single DualCoach invite in this private DM and tap Start yourself; do not send onboarding answers yet.

Start was not clicked. No Git commit was created.