Problem
Found in the review of #102 (#98): even with the Ignored Build Step, every push to every PR branch creates a deployment of requestflow-ai – skipped builds end as CANCELED and may still count against the Hobby plan's deployment limits. On 2026-09-28 both projects hit "Deployment rate limited – retry in 24 hours". AI previews are protected by Vercel Authentication and nobody uses them; CI builds and smoke-tests the AI image on every Dockerfile or lock change (#79).
Acceptance criteria
Security/Privacy affected?
No.
Problem
Found in the review of #102 (#98): even with the Ignored Build Step, every push to every PR branch creates a deployment of
requestflow-ai– skipped builds end asCANCELEDand may still count against the Hobby plan's deployment limits. On 2026-09-28 both projects hit "Deployment rate limited – retry in 24 hours". AI previews are protected by Vercel Authentication and nobody uses them; CI builds and smoke-tests the AI image on every Dockerfile or lock change (#79).Acceptance criteria
services/ai/vercel.jsonenables Git deployments only formain(git.deploymentEnabled), checked against the current Vercel docsrequestflow-aideployment; a merge tomainthat touchesservices/ai/still deploys productionSecurity/Privacy affected?
No.