update commands should only route to beaver or raccoon, never otter

Bug

`/update` commands dispatched through the Telegram bot (via dog) are currently being routed to otter — this is incorrect. Update commands should only ever be dispatched to beaver or raccoon.

Context

Dog is the dispatch layer that routes slash commands from Telegram to the appropriate wolt/agent. When a user sends `/update`, dog is incorrectly including otter as a valid dispatch target. Otter should not handle update commands.

Expected behavior

`/update` routes exclusively to beaver or raccoon — never otter.

Actual behavior

Dog dispatches `/update` to otter in at least some cases.

Where to look

• Dog's command routing / dispatch logic (the part that maps slash commands to target agents)
• Telegram bot handler for `/update`
• Any allowlist or routing table that determines which wolts handle which commands

Notes

This is a routing/dispatch architecture issue. Needs review to confirm:

1. Where the dispatch decision is made (dog logic vs. bot-level routing)
2. Whether otter is explicitly listed as a handler or if it's catching a wildcard
3. Whether beaver/raccoon should be tried in order or load-balanced

Flagging for architecture review before fixing.

Start by tracing Dog's command-routing or dispatch entry point for Telegram /update messages, then inspect the bot handler and any command allowlist or routing table. Confirm whether otter is explicitly included or reached through a wildcard, and determine how beaver and raccoon are selected. Done means /update dispatches only to beaver or raccoon and tests cover the exclusion of otter.