I read this as hands-on QA of the uncommitted Channel Direct Messages feature - I will inspect the feature and its test seams, run the required isolated checks without live integrations, then report one evidence-backed PASS/FAIL verdict.


I read this as hands-on QA of the uncommitted Channel Direct Messages feature - the isolated Hermes test environment has the required PTB 22.6 objects, so I am now executing the feature scenarios through the real adapter and coordinator seams with credentials and live homes removed.


I read this as hands-on QA of the uncommitted Channel Direct Messages feature - verdict: **FAIL**.

**Behavior exercised**
- Real PTB `Message`, `User`, `Update`, `CallbackQuery`, and `Application`; real adapter/coordinator seams:
  ```bash
  env -i ... /home/cube/projects/richard/hermes-agent/.venv/bin/python - <<'PY'
  ```
  Output: `REAL-PTB QA PASS: 34 assertions... no Bot API call executed`
- Covered default-off DM, valid canonical DM source/address, sender/topic/chat/direct rejection, reservation, callback clicker identity, synthetic `direct_messages_topic_id`, all four authority mismatches, migration stale/forged rejection, and byte-identical rollback.

**Test results**
```bash
.../python -m pytest -q -p no:cacheprovider tests/gateway/test_telegram_channel_inbox.py
# 6 passed

.../python -m pytest -q -p no:cacheprovider tests/gateway/test_telegram_channel_inbox_adapter.py
# 8 passed, 2 failed

.../python -m pytest -q -p no:cacheprovider tests/gateway/test_channel_inbox_migration.py
# 8 passed
```
Feature total: **22 passed, 2 failed**.

Blocker: the two adapter tests import mocked `Update`/`User` from `tests/gateway/conftest.py` before `channel_inbox_testkit` swaps in real PTB. Failures:
- `test_channel_inbox_admin_command_never_reaches_generic_agent`
- `test_channel_inbox_callback_uses_clicking_customer_identity`

Related isolated suites:
```text
test_telegram_topic_mode.py: 44 passed
test_telegram_callback_auth_fail_closed.py: 5 passed
test_telegram_physique_checkin.py: 75 passed, 15 failed
```
The same physique suite against `git archive HEAD` is also **75 passed, 15 failed**; those are pre-existing.

**Quality gates**
```text
ruff check --no-cache <10 changed files>: PASS
ty check --project ... --python ... <10 changed files>: FAIL, 711 inherited errors; 0 on feature-added lines
basedpyright --level error --outputjson <10 changed files>: FAIL, 992 inherited errors / 6132 warnings; 0 on feature-added lines
check-no-excuse-rules.py <10 changed files>: FAIL, 1180 total violations
```

Feature-caused no-excuse blockers (5):
```text
gateway/platforms/nutrition_coaching.py:21338 no-object
gateway/platforms/telegram.py:927 no-object
gateway/platforms/telegram.py:928 no-object
gateway/platforms/telegram.py:929 no-object
gateway/platforms/telegram.py:2860 broad-except
```

LOC:
```text
new production modules: 181, 161, 63, 183
new tests/testkit: 92, 81, 164, 129
modified existing modules: telegram.py 13,809; nutrition_coaching.py 21,142
```

```bash
git diff --check
git diff --no-index --check /dev/null <each untracked feature Python file>
```
Both clean.

No live Telegram/network call, service write, watcher start, commit, or Todo14 access occurred. Tests used empty environments and temporary homes. A failed `uv run` probe briefly created `.venv`; it was removed immediately. Final check: no repo `.venv` or QA artifacts remain; git status contains only the original feature worktree changes.


I read this as final hands-on QA of the current Channel Direct Messages worktree - I will re-baseline the repaired diff and evidence, execute the real-PTB and isolated/reverse gates without live state, then return a single PASS/FAIL with every blocker.


I read this as final hands-on QA of the current Channel Direct Messages feature - the repaired suite now uses real PTB fixtures; I am running its forward/reverse isolation, related routing checks, and clean static gates in temporary homes.


I read this as a renewed final QA after targeted privacy and test-order repairs - I will inspect the latest diff and tests, then independently rerun the three root orders, real-PTB authority-loss behavior, migration, and static gates.


I read this as a read-only final revalidation after the concurrent type-race restoration - I will re-read the frozen bytes and rerun the feature, privacy, and static checks without modifying the worktree.


I read this as the final read-only QA pass on the newly frozen compatibility revision - I will verify the typed legacy defaults, `object.__new__` fail-closed behavior, all three 30-test orders, and the remaining static gate on these exact bytes.


I read this as final read-only QA of the frozen Channel Inbox revision - verdict is **FAIL** because two feature-added no-excuse violations remain.

Blockers:
- `gateway/platforms/telegram.py:222` — `[no-object]` `_ChannelInboxCallbackQuery.answer` returns `object`.
- `gateway/platforms/telegram.py:997` — `[generic-exception]` new `RuntimeError` needs a typed error.

Verified on the final frozen hashes:
- All three root orders: **30/30 passed** each, including migration tamper/rollback and cached `checkin_cli` purge.
- Related topic/callback suite: **49 passed**.
- Real PTB QA: **28 assertions passed** using real `Message`, `User`, `Update`, `CallbackQuery`, and `Application`; checked default-off, canonical routing, callback identity, authority loss fail-close, startup denial, and `object.__new__` inert defaults. No Bot API call, app start, watcher, service, or profile write.
- Ruff, migration basedpyright profile, compile, and diff checks passed.
- No QA `.venv` or temp artifact remains; no new matching listener/process was started.

No files were edited.


I read this as exact-current read-only acceptance QA - I will re-read the repaired authority and callback types, then independently rerun all root orders, diff-aware integration scanning, and real-PTB fail-closed behavior.


I read this as exact-current read-only acceptance QA - **PASS**.

- Three root test orders: **30/30 passed** each.
- Ruff: passed.
- Diff-aware no-excuse scan across new and modified integration lines: **0 feature-added violations**.
- `git diff --check`: clean.
- Real PTB acceptance: **19 assertions passed** for typed `ChannelInboxAuthorityError`, disabled/authority-loss fail-close, legacy `object.__new__` inert defaults, canonical update/callback identity, and denied startup with real `Application`.
- No Bot API call, app start, watcher, persistent write, QA venv/temp artifact, or matching listener was created.
- Final source fingerprints matched the pre-QA exact-current candidate.