docs(workflow): enforce state-first checks before setup advice
This commit is contained in:
@@ -10,4 +10,8 @@
|
||||
- Brave MCP fallback on failure or weak/empty results
|
||||
- Search routing preference documented in `TOOLS.md`.
|
||||
|
||||
## Execution lesson
|
||||
- I missed that Telegram was already set up and incorrectly asked setup-style follow-up questions instead of checking current state first.
|
||||
- New rule: before suggesting setup/re-setup, first inspect current config, memory, and recent evidence; if already configured, treat it as ops/validation/debugging.
|
||||
|
||||
Source: workspace changes + gateway config patch on 2026-03-10.
|
||||
|
||||
Reference in New Issue
Block a user