I read this as a code-quality review - I will inspect the exact diff and surrounding Telegram command-registration paths, then report PASS/FAIL with evidenced findings only.


I read this as a code-quality review - I inspected the successor behavior, related forum path, and regression test.

**FAIL**

- **P1 - staff command scopes are not retained in forum chats.** Production registers the staff menu at `gateway/platforms/telegram.py:2817-2822`, but first processable forum text/command invokes `_ensure_forum_commands` (`:14575`, `:14631`), which overwrites that same `BotCommandScopeChat` with the generic Hermes menu (`:14324-14328`). I reproduced the overwrite: `help/status/approve/deny -> generic`. This makes the root fix incomplete.

- **P2 - regression coverage does not prove the required retained behavior.** `tests/gateway/test_telegram_production_preflight.py:292-297` only asserts that customer chat IDs are absent and the staff ID remains. It passes if validation or all three global scopes are removed, or if the staff scope carries the wrong commands. It needs to assert the default/private/group customer menus and the final staff menu, including the forum path.

The removed customer-specific registration is otherwise the smallest change inside `_register_production_nutrition_chat_commands`: route validation remains (`telegram.py:2801-2804`), global menus remain (`:2812-2816`), and only staff IDs receive direct chat scopes (`:2817-2822`).

The new regression test does reject prior customer-chat registration semantics: dynamically restoring that loop caused its assertion to fail. Verification: `uv run --locked --extra dev --extra messaging pytest -q tests/gateway/test_telegram_production_preflight.py` -> **13 passed**; Ruff passed.


I read this as a follow-up code review - I will inspect candidate `4efceab` and its parent, then verify the production global, staff, and forum command-scope behavior without editing.


I read this as a follow-up code review - the corrected command-scope behavior passes.

**PASS**

No findings.

- Customer commands remain on default, all-private, and all-group scopes: `gateway/platforms/telegram.py:2801-2816`.
- Only staff chat IDs receive chat-specific staff commands: `gateway/platforms/telegram.py:2817-2822`.
- Production staff forums are marked and returned before generic lazy registration: `gateway/platforms/telegram.py:14321-14333`.
- Regression coverage prevents the former forum overwrite: `tests/gateway/test_telegram_production_preflight.py:301-321`.

Verified:
- Production preflight tests: **14 passed**
- Forum command tests: **5 passed**
- Ruff: clean
- Direct behavioral exercise confirmed three customer global scopes, one staff-scoped menu, and no forum overwrite.