diff --git a/09 - Audits/Activity Log.md b/09 - Audits/Activity Log.md
index f4bcc32..3a662ed 100644
--- a/09 - Audits/Activity Log.md	
+++ b/09 - Audits/Activity Log.md	
@@ -11,6 +11,15 @@ entries on top. Maintained by agents per the rule in `../AGENTS.md`.
 
 ---
 
+### 2026-06-05 — backend@v2.8.88 — Bot launcher opens the Mini App (`/telegram`), not the web dashboard
+
+**Commits:** backend v2.8.88
+**Touched:** `services/telegram/botService.ts` (new `configureBotChatMenu`), `services/telegram/index.ts` (export), `app.ts` (call at startup)
+**Why:** Opening the app from the bot loaded the full web dashboard inside Telegram (hamburger sidebar, `/shop`) instead of the Mini App shell — the BotFather menu button URL pointed at the bare web root. Added `configureBotChatMenu()` which calls `setChatMenuButton` with `web_app.url = miniAppUrl()` (`${FRONTEND_URL}/telegram/`) at startup when the Telegram feature is enabled, so the launcher always opens the Mini App route regardless of BotFather config. Fire-and-forget; a Bot API failure never blocks boot.
+**Verification:** backend `npx tsc --noEmit` clean. After deploy + bot restart: the bot's menu button («Open Amanat») opens `dev.amn.gg/telegram` (Mini App shell with the bottom tab bar), not the web dashboard. NOTE: the chat-list «OPEN» button (Main Mini App) is BotFather-only — if used, its URL must also be set to `/telegram`.
+
+---
+
 ### 2026-06-05 — frontend@v2.8.104 — Mini App: onboarding→in-shell settings, achievements (email gate + buy/request)
 
 **Commits:** frontend only (v2.8.104)