docs: comprehensive update all docs to v0.0.46

11 files updated to reflect current state (v0.0.22 → v0.0.46):

ARCHITECTURE.md:
- Ring tones, group calls, read receipts, markdown rendering sections
- Bot API expanded (BotFather, numeric IDs, Telegram compat)
- Admin commands, known issues, 155 tests

TASK_PLAN.md:
- All P1-P4 marked DONE with version numbers
- Additional completed work section (bots, ETH, ring tones, group calls)
- New FC-P7 (Voice & Transport): cpal, Sender Keys, WebTransport
- FC-P6-T9/T10 added

PROGRESS.md:
- Full version history table v0.0.22 through v0.0.46
- Known issues section

README.md:
- Voice calls, ring tones, group calls, read receipts, markdown, 155 tests

SECURITY.md:
- Bot API security, voice call security, admin commands sections
- Updated protection tables

USAGE.md:
- Group calls, read receipts, markdown formatting, admin commands

CLIENT.md:
- Call commands, read receipts, markdown rendering

LLM_HELP.md + LLM_BOT_DEV.md:
- Call/group call/admin commands, ring tones, per-bot numeric IDs

TESTING_E2E.md:
- Tests 16-18: ring tones, group calls, admin commands

CLAUDE.md:
- Ring tone notes, group signal endpoint, MLS roadmap

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

warzone/docs/LLM_BOT_DEV.md

@@ -253,9 +253,30 @@ The bridge translates numeric chat_id ↔ fingerprints automatically.
 | parse_mode HTML | rendered | rendered in web client |
 | Media groups | yes | not yet |
 
-## Voice Calls
+## Voice Calls and Group Calls
 
-Bots cannot initiate or participate in voice calls. Voice is peer-to-peer only between human clients (web or TUI). Call signaling messages (`CallSignal` type) are delivered to bots via getUpdates as `text="/call_Offer"` etc., but bots should ignore them -- there is no audio path for bots.
+Bots cannot initiate or participate in voice calls or group calls. Voice is peer-to-peer only between human clients (web or TUI). Call signaling messages (`CallSignal` type) are delivered to bots via getUpdates as `text="/call_Offer"` etc., but bots should ignore them -- there is no audio path for bots. Group call signals (`/gcall`, `/gjoin`, etc.) are similarly not actionable by bots.
+
+## Markdown Rendering
+
+Bot replies support inline markdown formatting in both the web and TUI clients:
+- `**bold**` or `<b>bold</b>` (with `parse_mode: "HTML"`)
+- `*italic*` or `<i>italic</i>`
+- `` `inline code` `` or `<code>code</code>`
+- `[link text](url)` or `<a href="url">text</a>`
+- ` ```block``` ` for code blocks
+
+When using `parse_mode: "HTML"`, the HTML tags are rendered. Without `parse_mode`, the web client renders markdown syntax natively. Both paths produce styled output.
+
+## Per-Bot Numeric IDs
+
+Each bot sees a unique numeric ID for each user (`from.id` in updates). These IDs are:
+- Deterministic: the same user always maps to the same numeric ID for a given bot
+- Per-bot unique: different bots see different numeric IDs for the same user
+- Privacy-preserving: bots cannot correlate users across bots or recover raw fingerprints from the numeric ID
+- Derived via HMAC of the user's fingerprint keyed with the bot's token prefix
+
+Use `from.id` (or `chat.id`) as-is for replies. Do not attempt to reverse it to a fingerprint.
 
 ## Key Rules