- Added canonical n8n workflow to workflows/n8n/ (SSOT compliance).
- Integrated Telegram Bot API for admin approval/denial via inline keyboards.
- Implemented Authentik Core API integration to dynamically create active users.
- Resolved critical technical constraints for audit compliance:
* Fixed Telegram 'callback_data' 64-byte limit by optimizing payload format.
* Resolved Authentik API 405 errors by enforcing trailing slash in endpoint URL.
* Explicitly defined HTTP headers to prevent n8n import stripping.
Definition of Done (F6-2) Met:
- [x] Test user created via self-service flow.
- [x] Owner received enrollment link and instructions in Telegram.
- [x] Workflow committed to Git (workflows-as-code).
Closes #F6-2
Related: Sprint F6 v2, Phase 4.1 Automation Roadmap
- Xray 26.3.27 with VLESS + TLS + TCP on port 10443
- Let's Encrypt certificate for git.buryans.ru
- NAT configured for outbound traffic routing
- 5 user profiles with unique UUIDs
- Port 10443 opened in provider firewall
- Runbook and audit report added
- Documented final state of Phase 5 (Audit & Transparency)
- Defined infrastructure baseline v1.3 metrics and achievements
- All automation, monitoring, and backup goals met
- Implemented ops/weekly-report.sh to gather 7-day stats (alerts, commits, uptime, LXC)
- Automated Gitea Issue creation via API with 'weekly-report' and 'audit' labels
- Added webhook placeholder for Matrix/Telegram notifications
- Scheduled weekly execution via cron (Sundays at 20:00)
- Implemented ops/audit.sh for sub-second system state snapshotting
- Automated CHANGELOG.md updates with daily metrics (LXC, alerts, disk, git)
- Verified auto-commit and auto-push to Gitea main branch
- Scheduled daily execution via cron at 09:00
- Added supporting scripts to version control (audit.sh, backup.sh)
- Automated mass installation script executed successfully across 28+ LXC containers
- node_exporter (port 9100) deployed and enabled via systemd on all CTs
- postgres_exporter (port 9187) deployed on CT 151 with secure socket auth
- Verified metric exposure: Prometheus now has full observability over all infrastructure
- Fixed JSON parsing to correctly handle n8n webhook payload wrapping (payload.body)
- Verified end-to-end delivery to Telegram with proper HTML formatting
- Grafana Contact Point configured declaratively via provisioning
- 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
- Added base64-decoding for Gitea API runbook reading
- Implemented 30s heartbeat to agent_registry (PG CT 151)
- Strictly excluded .env and __pycache__ from version control
- Fulfills 'Everything as Code' principle from MASTER-PLAN
- 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
- Created canonical directories: services/comms, agents, audit, workflows/n8n, policies
- Moved Telegram Admin Bot source to services/comms/telegram-admin-bot/
- Added base policy stubs and agent REGISTRY.md
- Bulk-closed and labeled 'auto:spam' all 'AUTO-FIX: Unknown Monitor DOWN' issues in Gitea
- .env strictly excluded from version control
- Deployed on VPS (direct-emerald) with local danted SOCKS5 proxy
- Integrated read-only access to PostgreSQL (CT 151, host_states)
- Integrated read-only access to Gitea API (CT 140, issues)
- Foundation for F3-4 (Escalations) and F2 (Swarm Agents communication)
- .env strictly excluded from version control
- Added async Python bot (aiogram 3.x) with /start, /status, /issues commands
- Integrated PostgreSQL (CT 151) and Gitea API (CT 140) read access
- Configured secure local SOCKS5 proxy (danted) for Telegram API access
- Excluded .env from version control for security best practices
- Documented that CT 140 (Gitea) is currently on SQLite for stability
- Formalized the plan for a dedicated 'Database Sprint' for clean PG migration
- Ensures this technical context is not lost for future planning
- Documented completion of core policies and repo structure
- Formalized deferral of deep security hardening to dedicated sprint
- System baseline is now stable and ready for functional expansion
- Documented completion of core policies and repo structure
- Formalized deferral of deep security hardening to dedicated sprint
- System baseline is now stable and ready for functional expansion
- Prioritizing functional stability and agent swarm deployment
- Security hardening (Vaultwarden integration) will be addressed in a future dedicated sprint
- Verified no duplicate workflows in n8n DB
- Generated cryptographically strong passwords for Matrix, Mealie, Authentik
- Documented mautrix token revocation steps
- Updated CHANGELOG.md with SEC-debts status
- Diagnosed broken SQLite->PostgreSQL migration from 02.10
- Rolled back to stable gitea.db.migrated
- Created change request for clean PG migration in Phase 1 (Epic #150)
- Gitea API is now fully operational (HTTP 200)