Build production Discord control plane - #13
Conversation
|
Release-candidate verification update
|
|
Release-hardening update for What this slice adds:
Fresh CI evidence:
The PR should remain draft. Current production still fails the read-only verifier as not ready. Remaining gates require authorized production credentials/resources, production migration/deployment, bot installation only in |
|
Checkpoint published at This slice adds the friendly web setup desk, protected per-guild configuration API, stronger bot role/channel safety, queue role handling, durable moderation ordering, guild-isolated database writes, schema-aware health checks, exact release identity, security headers, auth/a11y polish, and expanded route/integration/browser coverage. Fresh local gates before publication:
The PR remains draft while the fixed-revision deep security review and live production/isolated-Discord gates continue. No secrets were committed. |
Summary
Verification
Release gates still required
This remains a draft until GitHub Actions builds/smoke-tests the Docker image and production credentials are configured. Before merge/deploy, apply the migrations and complete OAuth, install, setup, restart-persistence, queue/RBAC, moderation, removal, and reinstall testing in the isolated Discord release server.