feat(telegram): forward full CC output in verbose mode

[OneStepAt4time]

Summary

Implements #3190 — forward full Claude Code output to Telegram (thinking, tool calls, code) via configurable verbose mode.

Changes

• config.ts: Add tgVerbose boolean (default: false), env AEGIS_TG_VERBOSE
• telegram.ts: Forward message.thinking as 💭 italic text when verbose
• telegram.ts: Forward message.tool_use details with 🔧 code formatting when verbose
• server.ts: Wire verbose flag to TelegramChannel config
• Tests: Updated 8 test fixtures with tgVerbose: false default

Usage

# Enable verbose Telegram output
AEGIS_TG_VERBOSE=true

Or in config:

tgVerbose: true

Behavior

Event	Without verbose	With verbose
message.thinking	Silent	💭 thinking text (truncated 800 chars)
message.tool_use	Progress tracking only	🔧 tool.label + code block (truncated 600 chars)
message.assistant	Forwarded	Forwarded (unchanged)
message.user	Forwarded	Forwarded (unchanged)

Verification

tsc --noEmit  ✓  (zero errors)
npm run build ✓
npm test      ✓  (1248 passed, 0 failed)

Fixes #3190

[aegis-gh-agent]

🔧 Changes requested — 2 findings.

Finding #1 (Medium): feat-minor-bump-gate failing
Title is feat(telegram):... — needs approved-minor-bump label. Add label and re-run CI.

Finding #2 (HIGH): Markdown formatting in HTML parse_mode
The channel uses parse_mode HTML everywhere, but the new verbose messages use Markdown syntax:

• text renders as literal underscores in HTML mode, not italic. Use i tags instead.
• Backtick code blocks render as literal backticks. Use code and pre tags instead.

Fix: replace Markdown formatting with proper HTML tags consistent with the rest of the channel.

Otherwise clean: Config wiring correct (env var + config file + defaults), truncation sensible, 8 test fixtures updated, opt-in default.

[aegis-gh-agent]

✅ Approved. Both findings resolved — HTML formatting now uses italic()/code()/pre tags from telegram-style.ts. CI green, label present. Merging.