refactor: Remove deprecated INTERNAL_API_PORT (ultrathin monolith cleanup)

Architecture cleanup after migration to ultrathin monolith:

- Remove INTERNAL_API_PORT from .env files (was port 8002)
- Clean up bot_main.py: remove uvicorn, Thread, run_internal_api()
- Update validate.md to check /api/telegram/health instead of port 8002
- Add deprecation notices to old Windows deployment docs
- Update docs/telegram/README.md with architecture note

The Telegram internal API is now served at /api/telegram/internal/*
on the main backend port (8000/8001) instead of separate port 8002.

Also includes: menu updates, ServerLogsView improvements, script fixes

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

deployment/windows/docs/TELEGRAM_BOT_DEPLOYMENT.md

@@ -1,9 +1,20 @@
 # ROA2WEB Telegram Bot - Windows Server Deployment Guide
 
+> ⚠️ **DEPRECATED ARCHITECTURE**
+>
+> This documentation refers to the OLD microservices architecture where the Telegram bot
+> ran as a separate service on port 8002. The current architecture is an **ultrathin monolith**
+> where everything runs on a single port (8000/8001) via `backend/main.py`.
+>
+> **Current Architecture**: Telegram bot runs as a background task within the unified backend.
+> Internal API endpoints are now at `/api/telegram/internal/*` on the main port.
+>
+> See `CLAUDE.md` and `QUICK-START.md` for the current architecture.
+
 **Target Server**: Windows Server (10.0.20.36)
 **Deployment Method**: Windows Service (NSSM) - No Docker
 **Service Name**: ROA2WEB-TelegramBot
-**Internal API Port**: 8002
+**Internal API Port**: ~~8002~~ (DEPRECATED - now via main backend)
 **Created**: 2025-10-22
 **Last Updated**: 2025-10-22
 

deployment/windows/docs/TELEGRAM_BOT_TROUBLESHOOTING.md

@@ -1,5 +1,11 @@
 # ROA2WEB Telegram Bot - Windows Deployment Troubleshooting Guide
 
+> ⚠️ **DEPRECATED ARCHITECTURE**
+>
+> This documentation refers to the OLD microservices architecture (port 8002).
+> The current architecture is an **ultrathin monolith** - everything on port 8000/8001.
+> Telegram internal API is now at `/api/telegram/internal/*` on the main backend.
+
 This guide helps diagnose and fix common issues with Telegram bot integration on Windows Server deployments.
 
 ## Problem: "Link invalid sau expirat" (Invalid or expired link)