- Created n8n webhook listener for Prometheus/Grafana alerts
- Implemented smart parsing for both Grafana and Alertmanager payload formats
- Configured Grafana Contact Point declaratively via provisioning
- Alerts are now formatted and sent to Telegram consistently
- Verified network connectivity between Grafana (CT 113) and Prometheus (CT 134)
- Applied declarative datasource provisioning via pct push
- Restarted Grafana to apply configuration
- Datasource is now set as default and ready for dashboards/alerts
- Documented fixes for Unknown Monitor, Telegram duplicates, and queue clearing
- Added SPRINT-F3-STATUS.md for overall tracking
- F3-1, F3-2, F3-3 are now DONE. F3-4 is next.
- Created comprehensive audit script (ops/audit-infrastructure.sh)
- Scanned all LXC containers and nested Docker services
- Generated infrastructure-inventory.json with full service map
- Auto-created runbook templates for all discovered services
Each runbook includes:
- LXC CT ID and Docker container name
- Port mappings and network info
- 5-step procedures (status, health, logs, restart, troubleshooting)
This provides complete operational documentation for the entire Buryan Hub infrastructure.
- Defined architecture (mautrix-telegram)
- Outlined prerequisites, implementation steps, and acceptance criteria
- Documented risks (E2EE, rate limiting) and next steps for future sprint
- Added runbook for Synapse/Coturn administration
- Added healthcheck script for Matrix API monitoring
- Documented completion of F2-5, deferred Bridge to future sprint
- Documented architecture, artifacts, and success metrics
- Noted LXC+Docker cgroup locking behavior for future fix (Variant B)
- Formalized the completion of the secure agent control channel
- Populated agents/REGISTRY.md with 8 planned agents
- Created first agent charter: CHARTER-comms-agent.md (Telegram Bot)
- Added SQL init script for agent_registry table in PG (CT 151)
- Registered comms-agent as 'active' in the database