Telegram two-way control: inbound command listener and engine dispatch

[Ryan-Atkinson87]

Make Telegram the two-way control channel: accept commands and free-text blocker replies from the phone and route them into the engine.

Spec: §9.2 two-way, §9.3 Command scope, §6.4 pause/resume, §6.5 override.

Acceptance criteria

• Inbound listener accepts replies/commands from the human's Telegram chat, making the channel two-way (§9.2).
• Commands handled from day one: status, pause, resume, override usage, and free-text blocker responses (§9.3).
• status reports current run/wave state (reads run state from the wave-loop driver Wave-loop driver: end-to-end orchestration of the deterministic wave loop #29).
• pause / resume drive the engine's pause/resume mechanism (Hard pause and two-tier automatic resume (reset-known sleep + backoff probe) #34).
• override usage toggles the usage override for the wave (Override switch and peak-hour throttle policy modifiers #36).
• Free-text blocker responses are fed by the engine into the relevant AI session for the parked issue and recorded against the blocker (Blocker model and SQLite store: structured record, park/list/resolve #43) (§9.3).
• Commands are accepted only from the configured chat id; unknown commands get a helpful reply; explicit failure paths, no silent pass.
• Tests with the Telegram inbound layer mocked, covering each command route.

Depends on: #42, #43, #29, #34, #36