feat(billing): add monthly billing cycle for Team and Enterprise seats

.env.test

@@ -34,6 +34,10 @@ WORKOS_API_KEY=invalid-mock-workos-key
 WORKOS_CLIENT_ID=invalid-mock-workos-client-id
 STRIPE_TEAMS_SUBSCRIPTION_PRODUCT_ID='STRIPE_TEAMS_SUBSCRIPTION_PRODUCT_ID'
 STRIPE_ENTERPRISE_SUBSCRIPTION_PRODUCT_ID='STRIPE_ENTERPRISE_SUBSCRIPTION_PRODUCT_ID'
+STRIPE_TEAMS_MONTHLY_PRICE_ID='price_test_teams_monthly'
+STRIPE_TEAMS_ANNUAL_PRICE_ID='price_test_teams_annual'
+STRIPE_ENTERPRISE_MONTHLY_PRICE_ID='price_test_enterprise_monthly'
+STRIPE_ENTERPRISE_ANNUAL_PRICE_ID='price_test_enterprise_annual'
 USER_DEPLOYMENTS_API_BASE_URL=''
 USER_DEPLOYMENTS_API_AUTH_KEY=''
 SESSION_INGEST_WORKER_URL=''

.specs/template.md

@@ -0,0 +1,58 @@
+# [Feature Name]
+
+## Role of This Document
+
+This spec defines the business rules and invariants for [feature].
+It is the source of truth for _what_ the system must guarantee —
+valid states, ownership boundaries, correctness properties, and
+user-facing behavior. It deliberately does not prescribe _how_ to
+implement those guarantees: handler names, column layouts,
+conflict-resolution strategies, and other implementation choices
+belong in plan documents and code, not here.
+
+## Status
+
+Draft -- created YYYY-MM-DD.
+
+## Conventions
+
+The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
+"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
+"OPTIONAL" in this document are to be interpreted as described in
+BCP 14 [RFC 2119] [RFC 8174] when, and only when, they appear in all
+capitals, as shown here.
+
+## Definitions
+
+- **Term**: Definition of a domain-specific term used throughout
+  this spec.
+
+## Overview
+
+A concise narrative (1-2 paragraphs) describing the feature from a
+user and system perspective. Cover what the feature does, who it
+serves, and the high-level lifecycle. Avoid implementation details.
+
+## Rules
+
+### [Section Name]
+
+1. The system MUST ...
+2. The system MUST NOT ...
+
+## Error Handling
+
+1. When [error condition], the system MUST [behavior].
+
+## Not Yet Implemented
+
+The following rules use SHOULD and reflect intended behavior that is
+not yet enforced in the current codebase:
+
+1. The system SHOULD ... (Currently ...)
+
+## Changelog
+
+### YYYY-MM-DD -- Initial spec
+
+- Created from [source].

AGENTS.md

@@ -66,6 +66,10 @@ Migrations live in `packages/db/src/migrations/` and are generated by `drizzle-k
 - **After a rebase that conflicts on migration files:** delete all migration files, snapshots, and journal entries that were added on the branch, then re-run `pnpm drizzle generate` to regenerate a clean migration from the current schema diff. Re-append any backfill SQL afterward.
 - Prefer a single migration per feature branch when the code has not yet been deployed to production. If multiple migrations accumulated during development, squash them by deleting all branch-local migrations and regenerating.
 
+## Stripe Subscription Schedules
+
+When using `subscriptionSchedules.create()` with `from_subscription`, Stripe prohibits setting `metadata` in the same call (it copies metadata from the subscription automatically). Set custom metadata (e.g., `origin` tags) in the subsequent `subscriptionSchedules.update()` call instead.
+
 ## KiloClaw Billing
 
 Before making **any** changes related to KiloClaw billing — including bug fixes, new features, refactors, or reviews — you **must** first read the billing spec at `.specs/kiloclaw-billing.md`. This applies to all code paths that touch billing logic, pricing, invoicing, usage metering, or payment flows.

packages/db/src/migrations/0065_low_mad_thinker.sql

@@ -0,0 +1,13 @@
+CREATE TABLE "organization_membership_removals" (
+	"id" uuid PRIMARY KEY DEFAULT pg_catalog.gen_random_uuid() NOT NULL,
+	"organization_id" uuid NOT NULL,
+	"kilo_user_id" text NOT NULL,
+	"removed_at" timestamp with time zone DEFAULT now() NOT NULL,
+	"removed_by" text,
+	"previous_role" text NOT NULL,
+	CONSTRAINT "UQ_org_membership_removals_org_user" UNIQUE("organization_id","kilo_user_id")
+);
+--> statement-breakpoint
+ALTER TABLE "organizations" ALTER COLUMN "require_seats" SET DEFAULT true;--> statement-breakpoint
+CREATE INDEX "IDX_org_membership_removals_org_id" ON "organization_membership_removals" USING btree ("organization_id");--> statement-breakpoint
+CREATE INDEX "IDX_org_membership_removals_user_id" ON "organization_membership_removals" USING btree ("kilo_user_id");