Release v0.1.28: Billing Guards for Pipeline Runs

February 15, 2026

What changed

• New canRunPipelineForProject() function in the billing engine — looks up a project's owner and checks their billing status before any pipeline work starts.
• Billing guard in autoBuilder (30-min cron) — projects whose owners have insufficient credits or suspended/cancelled accounts are now skipped before dispatching expensive agent runs.
• Billing guard in manualAutoBuildRunner — returns early with a clear reason (Insufficient credits or billing issue) when billing check fails.
• 184 lines of new tests covering: project not found, positive credits, zero credits, suspended accounts, cancelled accounts, and active subscriptions with zero credits.

Why it matters

Without these guards, the autoBuilder cron could dispatch expensive AI agent runs (curation, architect, implementation) for projects whose owners have no credits or are suspended. The guard is a cheap database check that runs before any costly work begins, preventing unbilled compute costs and wasted resources.

Technical notes

• canRunPipelineForProject(projectId) resolves userId from the projects table, then delegates to the existing canRunPipeline(userId) function.
• No schema changes or breaking changes.