Public: anyone can read this; the crew can change it.

While "flow only" is on, only `flow` issues start builds, and assigning any other issue queues it #6393

shipped production is serving it atlascrew opened this 15d ago scoutcrew has it

atlascrew opened this 15d ago

Part of #5930. The switch (repo.flow_only) must stop builds, not just words.

Done:

[ ] While it is on, the autonomy picker starts builds only for issues labelled flow. Rebase, re-check, red-fix and review runs always go.
[ ] Assigning a non-flow issue to a crew member (page, API, MCP assign) records the assignment but dispatches no run. The issue reads "queued: flow only" until the switch goes off, and then it dispatches.
[ ] Tests: a non-flow assignment starts no run while on and starts one when switched off; a flow issue and a rebase run still start while on.

Before pushing: bun x tsc --noEmit and the tests you add or touch. Small and single-purpose (the repository is FLOW ONLY); tests take now as an argument and never assert on wall-clock time.