Block a user
[Feature] Extend dashboard with deeper operational metrics once queue, worker, storage, backup, and system-health metrics are stable
[Feature] Add monitoring dashboard for queue depth, worker health, storage use, failed/unknown jobs, backup status, and system health
[Feature] Add backup/restore procedure and restore drill
[Task] Publish deployment/operator documentation from the verified production-like dev profile
[Feature] Add UI/admin visibility for worker enabled/running/stale queue states
[Task] Draft installer/deployment flow: configure, migrate, create first admin/tenant, enable modules, start web/worker services, and verify health
[Feature] Add scripts/docs for starting, stopping, resetting, and seeding the production-like dev stack without replacing the minimal dev workflow
[Feature] Add queue/worker checks covering task publishing, worker startup, retry behavior, stale worker detection, and graceful shutdown
[Feature] Add storage persistence checks for managed files, generated EML/report artifacts, audit-relevant blobs, and backup/restore boundaries
[Task] Run migrations and smoke checks against Postgres in the production-like dev profile, not only SQLite
[Feature] Add configuration validation that fails early with actionable messages when required production-like settings are missing
[Feature] Add
.env.example, generated config templates, or a config bootstrap command so new installs are configured intentionally instead of only cloned
[Task] Define the install/runtime configuration contract: database URL, broker/result backend, storage backend/root or object-store credentials, secret/encryption keys, module e...
[Feature] Add a production-realistic dev profile with Postgres, Redis, Celery worker(s), persistent file/blob storage, and explicit module configuration
[Task] Keep minimal dev mode supported and documented: SQLite, filesystem storage, and no Redis/Celery unless explicitly enabled
[Task] Define inheritance/delegation constraints explicitly: may use, must use, may override, may not override, may merge, may delegate
[Feature] Add impact analysis before delete, disable, unshare, policy changes, and cascading changes
[Task] Consider backend-provided exact policy source metadata for "which specific scope caused this value"
[Task] Surface governance source path more explicitly in tenant details and other admin panels
[Task] Review broader backend-at-rest encryption needs beyond mail secrets