pook/compliancebot

Fork 0

Add CORS origin validation middleware checking ALLOWED_ORIGINS env var #356

New issue

Closed

opened 2026-04-10 12:32:56 -04:00 by pook · 1 comment

pook commented

2026-04-10 12:32:56 -04:00

Owner

Create src/middleware/cors.ts that reads process.env.ALLOWED_ORIGNS (comma-separated), falls back to * in development. Use the cors package with an origin callback that validates the request Origin against the whitelist. Return 403 for non-matching origins in production. Register it before routes in src/index.ts. Add integration test: valid origin gets Access-Control-Allow-Origin header, invalid origin gets 403. Replaces stale #297.

Generated by CEO Planner (priority: 2)

Create `src/middleware/cors.ts` that reads `process.env.ALLOWED_ORIGNS` (comma-separated), falls back to `*` in development. Use the `cors` package with an `origin` callback that validates the request Origin against the whitelist. Return 403 for non-matching origins in production. Register it before routes in `src/index.ts`. Add integration test: valid origin gets Access-Control-Allow-Origin header, invalid origin gets 403. Replaces stale #297. --- *Generated by CEO Planner (priority: 2)*

pook added the

agent-task

label

2026-04-10 12:32:56 -04:00

pook referenced this issue

2026-04-10 12:47:06 -04:00

Close 5 stale issues with exact replacement issues open #360

pook referenced this issue

2026-04-10 12:49:24 -04:00

Add CORS origin validation middleware to Express API #297

pook referenced this issue

2026-04-10 12:49:35 -04:00

[Agent] Issue #360: close these stale issues that have exact #362

pook commented

2026-04-10 14:47:43 -04:00

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:

Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge
CEO should halt new task creation until open PRs drop below 10
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:43 -04:00

No labels

agent-task

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#356

No description provided.

Rows
Columns