I read this as test-only implementation - I’ll inspect the Python preflight surface, write faithful behavioral RED tests in the owned file, run the exact pytest command, and save its transcript. WORKING.


I read this as test-only implementation - the existing safe config loader is usable, while the live identity/topic/admin/package/scope gate is absent; I’m now encoding that boundary as behavioral tests without importing a nonexistent future module.


I read this as verification - the owned test file is 157 pure LOC and imports only existing modules; I’m running the exact target now and will preserve the expected behavioral RED transcript.


I read this as completed test-only RED delivery - the requested behavioral gaps are captured without production edits.

- Added `tests/gateway/test_telegram_production_preflight.py`
- Added RED transcript at `.omo/evidence/v1.1.1-stability/red-production-preflight.txt`
- Verification: **1 passed, 10 failed, exit 1** due to missing production preflight behavior
- Ruff and Python compilation passed
- File is 157 pure LOC, single-responsibility, boundary-focused, with no type escape hatches or production changes
- Other untracked files shown by Git belong to concurrent sibling tasks; this task modified only its owned test and evidence files.


I read this as correcting the RED tests - I’ll replace the synthetic future-symbol gate with direct execution of existing config, adapter identity, membership, topic, authority, and command-registration seams, then refresh the failing transcript and static checks.


I read this as implementation correction - I found the concrete current seams: per-turn dotenv reload, identity pinning, membership readiness, topic allowlist/inventory, Task26 activation authority, forum command registration, and adapter base-URL setup. I’m rewriting the tests to drive those directly.


I read this as final verification - I removed the only fixture setup defect (the membership inventory now has its required owner authority), so each remaining failure can represent the intended production behavior gap.


I read this as revision complete - the RED suite now exercises existing production seams directly.

- Pytest: **10 behavioral failures, 2 passes, exit 1**
- Ruff and Python compilation pass
- Evidence updated at `.omo/evidence/v1.1.1-stability/red-production-preflight.txt`
- Only the owned test and evidence files were modified
- Tests now cover runtime dotenv token clobbering, getMe identity mismatch, admin readiness, topic validation/reachability, candidate activation, scoped menus, and remote fake API rejection
- Architectural review: single preflight-test responsibility, real boundary seams, no type escapes or one-off production abstractions
- File is 208 pure LOC, in the warning band; split before adding further cases