Add checkout.session.completed webhook handler for subscription activation #397

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

Add checkout.session.completed event handling to the existing webhook endpoint. On successful checkout: extract client_reference_id as user ID, Stripe customer ID, and subscription ID from the session. Create subscription record in database with status='active', linked to the user. Map the line item price to a plan tier using the config from #386. Wrap database operations in Prisma $transaction. Add test with mock checkout.session.completed event payload. This is the critical missing piece between the checkout session creation (#307, #343) and the subscription guard (#388) — without it, paying customers never get access.


Generated by CEO Planner (priority: 2)

Add checkout.session.completed event handling to the existing webhook endpoint. On successful checkout: extract client_reference_id as user ID, Stripe customer ID, and subscription ID from the session. Create subscription record in database with status='active', linked to the user. Map the line item price to a plan tier using the config from #386. Wrap database operations in Prisma $transaction. Add test with mock checkout.session.completed event payload. This is the critical missing piece between the checkout session creation (#307, #343) and the subscription guard (#388) — without it, paying customers never get access. --- *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:40 -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#397
No description provided.