I read this as hands-on QA verification - I’ll inspect the sealed worktree and execute the requested focused, adjacent, and manual checks without modifying production.


I read this as QA conclusion - I’ll report the decisive verification results without further execution.

FAIL

- Manual QA passed under both isolated installs from `/tmp`:
  - Korean button: `확인했습니다 - 임상 승인 아님`
  - same generation `26`; successor `27`
  - exact-owner `/status` accepted; foreign owner rejected
  - `workflow_transition: false`; `customer_messages: 0`
- Focused suite: **46 passed** (includes systemd `CREDENTIALS_DIRECTORY` capability coverage).
- Adjacent suites: **161 passed** for nutrition coaching + physique check-in.
- Adjacent combined run: **236 passed, 10 failed, 1 warning**. All failures are in `test_telegram_group_gating.py`, including trainer-route collision handling, adaptive lifecycle/terminal-card rendering, Korean edit-note callback acknowledgement, invalid-grounding publication, and missing `_ensure_trainer_topic_keyboard`.
- Candidate `102cbbb...` is bound by evidence; build-a/build-b wheels are byte-identical (`e3b200...`), and sealed golden-path `pass.json` records `PASS`.

No production service, Telegram API, or live profile was touched.


I read this as final focused QA for the replacement candidate - I’ll locate its sealed evidence, then run only the notification tests and isolated-install manual QA.


I read this as final candidate QA - I ran only the notification suite and manual checks.

PASS

- Candidate binding: `9208d72c...1f97a555`.
- Focused notification tests: **8 passed**.
- `manual_qa.py`: **2/2 passed** under install-a and install-b from `/tmp`.
- Both manual runs: `OPERATOR_NOTIFICATION_MANUAL_QA_PASS`.
- `status_then_restart_deduped: true`; same generation `26`, successor `27`.
- Korean button correct; exact-owner status behavior correct; zero customer messages; no workflow transition.


I read this as final targeted recovery QA - I’ll confirm the new candidate binding, run only the bidirectional recovery test, and execute manual QA in both isolated installs.


I read this as final targeted recovery QA - focused recovery and both isolated manual checks passed.

PASS

- Candidate `e06a4e8a...97da2fc6` binds wheel A/B `ea618eaf...defc1db9`.
- Bidirectional recovery test: **1 passed**.
- Manual QA: **2/2 passed** (install-a, install-b).
- Both: `status_then_restart_deduped: true`; same generation `26`, successor `27`.


I read this as final verdict - PASS.