Restored stuck Telegram bot by flipping .env mode from off to polling
Takeaway: Next time I'd just say 'check if SKAZKA_BOT_MODE got flipped in .env' up front since that's happened before per the memory notes.
3 sessions on telegram with a coding agent: the agent failed at least once in 2, and 1 finished without a human stepping in.
Takeaway: Next time I'd just say 'check if SKAZKA_BOT_MODE got flipped in .env' up front since that's happened before per the memory notes.
Takeaway: Next time I'd ask upfront whether the messaging platform requires a reply anchor for topic delivery before wiring cron jobs to a named topic — that assumption cost two failed delivery attempts.
Takeaway: Next time I'd ask straight away 'does routing cron output through Telegram's topic system require a reply anchor?' instead of discovering it twice through failed live tests.