Schedule generation by provider capacity and content length

[Ankit6149]

Advances #27 without claiming full completion.

Implemented:

• hosted/custom generation keeps a hard destination concurrency ceiling of 2
• local-model routes default to a concurrency ceiling of 1
• configured concurrency may lower, never raise, the provider ceiling
• long-form destinations (blog, newsletter, YouTube, Reddit) run in a separate sequential scheduling phase
• duplicate-repair work uses the same provider-aware scheduling policy
• ordering is preserved in returned results
• cancellation remains respected between phases
• regression coverage verifies hosted/local ceilings, long-form isolation, ordering, and orchestration wiring

Still open for #27:

• durable cross-restart execution
• real-model twelve-destination stress acceptance
• provider/model-specific adaptive limits beyond hosted-vs-local policy
• broader job persistence/recovery

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
signal-flow-studio	Ignored		Sep 25, 2026 1:53pm UTC

[vercel]

Deployment failed for project signal-flow-studio with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/ankit6149s-projects?upgradeToPro=build-rate-limit