Skip to content

Build production Discord control plane - #13

Draft
rupayon123 wants to merge 5 commits into
mainfrom
codex/discord-control-plane
Draft

Build production Discord control plane#13
rupayon123 wants to merge 5 commits into
mainfrom
codex/discord-control-plane

Conversation

@rupayon123

Copy link
Copy Markdown
Owner

Summary

  • add database-backed Discord OAuth sessions, manageable-server selection, guild-locked install/status/removal, and a polished responsive organizer workspace
  • replace preview/demo behavior with guild-scoped durable setup, Q&A, onboarding, teams, queues, moderation, audit, RBAC, rate limiting, and prompt-injection safeguards
  • add atomic database operations and migrations, deterministic bot packaging, production health checks, migration validation, Docker smoke checks, and full browser/unit coverage

Verification

  • frozen pnpm 10.25.0 install
  • all workspace type checks
  • 193 substantive unit/integration tests
  • production bot and web builds
  • authenticated-config Next.js production build
  • 27 applicable Playwright desktop/mobile scenarios passed; 1 intentional device-specific skip
  • dependency audit: no known vulnerabilities
  • migration journal/file integrity and Drizzle check
  • formatting, diff hygiene, and staged secret-pattern scan

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.

Copy link
Copy Markdown
Owner Author

Release-candidate verification update

  • GitHub Actions run #35 is fully green: audit, secret scan, migration integrity, typecheck, formatting, 193 unit/integration tests, production build, Docker build/runtime smoke, and browser tests.
  • The settled branch is fe523e0857bc0b80b713914d42014f3e9d4828d1.
  • Independent packaging, security, correctness, and final-release passes found no remaining P0–P2 code blocker after the latest fixes.
  • This PR intentionally remains a draft. The remaining gates require production account authorization: provision/link the database, configure Discord/Vercel secrets, deploy the web app and long-running bot, register commands in the isolated release server, and complete live OAuth/install/remove/RBAC/onboarding/Q&A testing.
  • No production mutation, secret rotation, merge, or paid resource will occur without explicit authorization.

Copy link
Copy Markdown
Owner Author

Release-hardening update for be10970CI run #36 is fully green.

What this slice adds:

  • guarded isolated-guild/global command publication and stricter bot/web environment validation
  • offline deployment preflight, deterministic secret scanner, read-only live release verifier, and production next start smoke
  • bounded fallback rate-limit storage
  • real OAuth/RBAC route coverage and a PostgreSQL 17 migration/session integration job
  • fixes for public /ask delivery and the unconfigured OAuth recovery redirect
  • exact isolated-guild command-set validation so obsolete commands fail the live gate

Fresh CI evidence:

  • database-integration: all migrations applied; account/session, refresh lease, CAS, touch, and revocation passed on real PostgreSQL
  • browser: Playwright passed
  • test: audit, secret scan, migration check, typecheck, formatting, full tests/build, production Next smoke, Docker image build, and container runtime/import smoke all passed

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 PipHackLup Release Lab, and interactive two-account Discord verification for OAuth, setup, RBAC, restart persistence, removal, and reinstall. No secrets were committed.

Copy link
Copy Markdown
Owner Author

Checkpoint published at 06b2fb15ca4484e2eea2be9efd4dc019b5e48b0c.

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:

  • typechecks passed across all workspaces
  • 44 script tests, 17 core tests, 30 DB tests (3 environment-gated skips), 128 bot tests, and 91 web tests passed
  • Playwright: 31 passed, 1 intentional skip
  • production build and next start fail-closed smoke passed
  • dependency audit, full-tree secret scan, migration history/Drizzle check, formatting, and diff checks passed

The PR remains draft while the fixed-revision deep security review and live production/isolated-Discord gates continue. No secrets were committed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant