I read this as QA verification - run the specified local regression, migration, and installed-wheel checks without modifying production integrations.


I read this as QA verification - report the local regression and installed-wheel validation result.

**PASS**

```sh
PYTHONDONTWRITEBYTECODE=1 .venv/bin/python -m pytest -q -p no:cacheprovider \
  tests/gateway/test_telegram_production_preflight.py
```
```
13 passed in 0.41s
```

```sh
PYTHONDONTWRITEBYTECODE=1 .venv/bin/python -m pytest -q -p no:cacheprovider \
  tests/gateway/test_nutrition_coaching.py \
  tests/gateway/test_telegram_nutrition_onboarding_recovery.py \
  tests/gateway/test_telegram_publication_recovery.py
```
```
84 passed in 1.93s
```

```sh
PYTHONDONTWRITEBYTECODE=1 .venv/bin/python -m pytest -q -p no:cacheprovider \
  tests/gateway/test_dualcoach_v111_migration.py
```
```
41 passed in 0.43s
```

Candidate binding validation used `validate_product_binding` against successor build-A Hermes and the prior stability profile wheel:
```
{"binding_sha256":"3bb8d4d70ac4319c0dfe2633f92713f15eb14ed202bb0e33ad5f294d72acac1a","candidate_digest":"e55ac326eab1fa81a56c8798efc14d3bcc7956d08761af095168e7ec8573b9ae","hermes_wheel_sha256":"738d5d8cc0abdddb28e305c6cccbd9fa2098052d359535b106e3aed4a237b820","prior_profile_wheel_sha256":"27f7427199d4a0a2e8a08aba26431552655f615544be0f13741e88b4b7f2250a","status":"CANDIDATE_BINDING_PASS"}
```

Installed-wheel driver: created a fresh `/tmp` Python 3.12 venv offline with:
- `.omo/evidence/v1.1.1-successor/build-a/hermes_agent-0.17.0-py3-none-any.whl`
- `.omo/evidence/v1.1.1-stability/build/physique_checkin_cli-0.1.0-py3-none-any.whl`
- wheelhouse dependencies and `python-telegram-bot==22.6`

It ran outside the repository with `PYTHONPATH`, `HERMES_HOME`, and `TELEGRAM_BOT_TOKEN` unset. Output:
```json
{
  "customer_ids_supplied": [7558064272, 8527916639],
  "global_private_customer_menu": ["start", "help"],
  "hermes_agent_version": "0.17.0",
  "positive_customer_specific_chat_scopes": [],
  "profile_package_version": "0.1.0",
  "staff_specific_menu": {
    "chat_id": -100700,
    "commands": ["help", "status", "approve", "deny"]
  }
}
```
Both imported modules resolved from that venv's `site-packages`; `pip check` reported `No broken requirements found.` The driver asserted and would fail on any positive `BotCommandScopeChat`.

Blockers: none. No live profile, Telegram, systemd, or external service was accessed. The target worktree remained in its pre-existing dirty state; temporary QA artifacts were removed.


I read this as final QA verification - locate the new candidate evidence, then run the specified local preflight, E2E, receipt, binding, and installed-wheel checks without external writes.


I read this as final QA verification - report the local candidate-bound regression, receipt, binding, and installed-wheel results.

**PASS** - candidate `4efceab409e16ad38740a0faaa5a899e0630991b862e2592a5e2d5c9e825820d`.

```sh
PYTHONDONTWRITEBYTECODE=1 .venv/bin/python -m pytest -q -p no:cacheprovider \
  tests/gateway/test_telegram_production_preflight.py
```
```
14 passed in 0.42s
```

```sh
PYTHONDONTWRITEBYTECODE=1 .venv/bin/python -m pytest -q -p no:cacheprovider \
  tests/gateway/test_dualcoach_disposable_e2e_contract.py \
  tests/gateway/test_fake_telegram_bot_api.py \
  tests/gateway/test_dualcoach_admin_loopback.py \
  tests/gateway/test_dualcoach_loopback_model_provider.py
```
```
30 passed in 9.35s
```

```sh
env -u PYTHONPATH -u HERMES_HOME -u TELEGRAM_BOT_TOKEN \
  .venv/bin/python scripts/run_dualcoach_v111_disposable_e2e.py \
  --candidate-binding .omo/evidence/v1.1.1-successor/candidate-binding.json \
  --evidence-dir /tmp/nutricoach-v111-final-candidate-bound-e2e
```
```
DISPOSABLE_E2E_PASS
```

Fresh E2E receipts:
```json
{"activation_generation":6,"candidate_digest":"4efceab409e16ad38740a0faaa5a899e0630991b862e2592a5e2d5c9e825820d","customer_delivery_replay_duplicates":0,"customer_delivery_sends":1,"customer_key":"disposable_001","model_provider_requests":1,"operator_generation_card":1,"receipt_replay_cursor":1,"response_replay_cursor":2}
```
```json
{"schema":"draft-delivery-capability-issue-v2","status":"ISSUED","provider_actions":0,"telegram_actions":0}
```
```json
{"duplicates":0,"operator_delivery":1,"operator_generation_card":1,"owner_card":1,"question":23}
```
```json
{"authority_directory_removed":true,"bot_api_port_released":true,"child_processes_reaped":true,"fake_server_thread_stopped":true,"loopback_port_released":true,"model_api_port_released":true,"model_server_thread_stopped":true,"temporary_profile_removed":true}
```
```json
{"bind_host":"127.0.0.1","bot_api_host":"127.0.0.1","loopback_only":true,"model_api_host":"127.0.0.1"}
```

Binding validation against build-A Hermes and the prior profile wheel:
```json
{"binding_sha256":"bae83f96d367a351ecf15654740c14f17bbb0a9ddc98ba57c358e5cc71efa66b","candidate_digest":"4efceab409e16ad38740a0faaa5a899e0630991b862e2592a5e2d5c9e825820d","hermes_wheel_sha256":"8e99762ee3ce53e43f086d3bfb99edc3246f8f990b3da8e53f6e6aef3181a91e","profile_wheel_sha256":"27f7427199d4a0a2e8a08aba26431552655f615544be0f13741e88b4b7f2250a","status":"CANDIDATE_BINDING_PASS"}
```

Installed-wheel driver ran from `/tmp` against both `install-a` and `install-b`, with customer IDs `7558064272`, `8527916639`, and staff forum `-100700`:
```json
{"customer_ids_supplied":[7558064272,8527916639],"forum_overwrite":false,"global_private_customer_menu":["start","help"],"positive_customer_specific_chat_scopes":[],"staff_specific_menu":{"chat_id":-100700,"commands":["help","status","approve","deny"]}}
```
Both imports resolved from each slot's `site-packages`; both `pip check` runs returned:
```
No broken requirements found.
```
Installed member provenance also passed for both slots against the exact Hermes/profile wheel bytes.

Blockers: none. The E2E used only loopback fake APIs and temporary profiles; no live profile, Telegram, systemd, or external service was accessed. Temporary QA artifacts were removed.