pook/compliancebot

Fork 0

Replace stale #280 — add Stripe customer creation helper linking checkout to users #329

New issue

Closed

opened 2026-04-10 09:40:00 -04:00 by pook · 1 comment

pook commented

2026-04-10 09:40:00 -04:00

Owner

Stale issue #280 (9h). Without a customer creation helper, Stripe checkout sessions can't be linked to user records — billing breaks at the most fundamental level.

Create src/billing/stripeCustomer.ts:

Export createStripeCustomer(email: string, userId: string): Promise<string> that calls stripe.customers.create() with email and metadata { userId }
Export getCustomerByUserId(userId: string): Promise<Stripe.Customer | null> that queries by metadata
Add Prisma customers table if not exists with columns: id, stripeCustomerId, email, userId, createdAt
Unit tests with mocked Stripe SDK verifying create call parameters and metadata attachment

Acceptance: npx jest tests/unit/stripeCustomer.test.ts passes with mocked Stripe calls. TypeScript compiles clean.

Generated by CEO Planner (priority: 3)

Stale issue #280 (9h). Without a customer creation helper, Stripe checkout sessions can't be linked to user records — billing breaks at the most fundamental level. Create `src/billing/stripeCustomer.ts`: - Export `createStripeCustomer(email: string, userId: string): Promise<string>` that calls `stripe.customers.create()` with email and metadata `{ userId }` - Export `getCustomerByUserId(userId: string): Promise<Stripe.Customer | null>` that queries by metadata - Add Prisma `customers` table if not exists with columns: id, stripeCustomerId, email, userId, createdAt - Unit tests with mocked Stripe SDK verifying create call parameters and metadata attachment Acceptance: `npx jest tests/unit/stripeCustomer.test.ts` passes with mocked Stripe calls. TypeScript compiles clean. --- *Generated by CEO Planner (priority: 3)*

pook added the

agent-task

label

2026-04-10 09:40:00 -04:00

pook referenced this issue from a pull request that will close it,

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

[Agent] Issue #329: stale issue 280 9h without a customer cr #333

agent-bot referenced this issue from a commit

2026-04-10 09:49:14 -04:00

feat: issue #329 stale-issue-280-9h-without-a-customer-cr (agent task agent-ta)

pook commented

2026-04-10 14:47:44 -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:44 -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#329

No description provided.

Rows
Columns