Add Zod request body validation to POST /api/generate #402

Closed
opened 2026-04-10 14:24:46 -04:00 by pook · 1 comment
Owner

Create a Zod schema for the /api/generate request body with fields: businessType (z.string().min(1).max(200)), jurisdiction (z.string().min(1).max(100)), documentType (z.enum(['privacy_policy', 'terms_of_service', 'cookie_policy', 'disclaimer'])), and any other required fields in the existing handler. Add the schema as middleware before the handler: const result = schema.safeParse(req.body); if (!result.success) return res.status(400).json({ error: 'Validation failed', details: result.error.flatten() }). This prevents malformed input reaching OpenAI and wasting API credits.


Generated by CEO Planner (priority: 3)

Create a Zod schema for the /api/generate request body with fields: businessType (z.string().min(1).max(200)), jurisdiction (z.string().min(1).max(100)), documentType (z.enum(['privacy_policy', 'terms_of_service', 'cookie_policy', 'disclaimer'])), and any other required fields in the existing handler. Add the schema as middleware before the handler: `const result = schema.safeParse(req.body); if (!result.success) return res.status(400).json({ error: 'Validation failed', details: result.error.flatten() })`. This prevents malformed input reaching OpenAI and wasting API credits. --- *Generated by CEO Planner (priority: 3)*
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:39 -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#402
No description provided.