Add startup environment variable validation with fail-fast #381

Closed
opened 2026-04-10 13:33:43 -04:00 by pook · 1 comment
Owner

Add a startup validation module that checks DATABASE_URL, OPENAI_API_KEY, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, ALLOWED_ORIGINS, and RESEND_API_KEY are set as non-empty strings. Log which vars are missing and call process.exit(1) immediately. Prevents the app from starting with missing configuration.

Acceptance criteria:

  • New file src/config/validateEnv.ts (or add to existing config module)
  • Called before Express app.listen()
  • Logs exact missing var names on failure
  • Returns typed config object on success
  • Unit test confirming exit on missing var and success when all present

Generated by CEO Planner (priority: 2)

Add a startup validation module that checks DATABASE_URL, OPENAI_API_KEY, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, ALLOWED_ORIGINS, and RESEND_API_KEY are set as non-empty strings. Log which vars are missing and call process.exit(1) immediately. Prevents the app from starting with missing configuration. Acceptance criteria: - New file src/config/validateEnv.ts (or add to existing config module) - Called before Express app.listen() - Logs exact missing var names on failure - Returns typed config object on success - Unit test confirming exit on missing var and success when all present --- *Generated by CEO Planner (priority: 2)*
Author
Owner

Bulk-closed 2026-04-10 during pipeline triage.

Context: CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch agent/dispatch/* because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key.

What to do next:

  1. Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge
  2. CEO should halt new task creation until open PRs drop below 10
  3. Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks)

This issue was superseded, not abandoned. Reopen if still relevant after PR triage.

Bulk-closed 2026-04-10 during pipeline triage. **Context:** CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch `agent/dispatch/*` because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key. **What to do next:** 1. Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge 2. CEO should halt new task creation until open PRs drop below 10 3. Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks) This issue was superseded, not abandoned. Reopen if still relevant after PR triage.
pook closed this issue 2026-04-10 14:47:41 -04:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pook/compliancebot#381
No description provided.