Public: anyone can read this; the crew can change it.
Remove the Flow only toggle: the `flow` label alone says what goes first #7674
The Flow only toggle is gone, and flow alone now decides what goes first. I ran about 270 tests, including test/flow-first.test.ts, test/mcp-labels.test.ts and test/mcp-size.test.ts, plus tsc and design-lint; all pass. I did not run the whole suite, since the forge runs it on push.
stopped parked by the crew
The Flow only toggle is gone, and flow alone now decides what goes first. I ran about 270 tests, including test/flow-first.test.ts, test/mcp-labels.test.ts and test/mcp-size.test.ts, plus tsc and design-lint; all pass. I did not run the whole suite, since the forge runs it on push. The push went through after a pre-push hook added a migration pin commit (3c4d2050).
Ordering
readyNowinsrc/core/dependencies.tsis the one place that orders ready work. Issues labelledflowcome first; everything else keeps its old order, so with no labelled issue nothing changes.- The map's "Ready now" list shows labelled work on top, with a
flow ·prefix on each such row. - A test shows a labelled newer issue ahead of older unlabelled ones, and unlabelled work still starting when nothing is labelled.
What was deleted
crew/flow_only.ts,crew/flow_label.ts,flow/flow_only_auto.ts,web/flow_only_line.ts.- The settings route, the crew-card toggle, the home line and button, the header line, and the terminal's
wkey and About row. - The
flowOnlyfield in the API, OpenAPI and MCPrepo_settings, plus the "queued: flow only" line everywhere. - The dispatcher hold, the
flow_onlyheld-filter, and the held-pull comment inrequested.ts. - A new migration drops
repo.flow_onlyand theflow_only_watchtable. - The tests for the switch are removed too.
Held assignments are no longer held. The existing startup sweep dispatches them, and a test checks that an assignment of unlabelled work runs.
Applying the label
- Issue page: a "Flow first" / "Not first" button sits in the issue header.
- Issues list: each open row has the same button, for writers only. It posts to the new
POST /:owner/:name/issues/:number/flow, which creates theflowlabel on first use. - MCP:
labelstakes an optionalactionofset,addorremove. The size test passes without raising any ceiling.
Choices and leftovers
- A list row's link cannot hold a form, so the row gets a
row-aftersibling. This new CSS class is named indocs/design/areas/flow-first.md. - I kept
flow_only.clearedinevent_audience.ts, so old events from the retired switch stay admin-only. - The planner-keeps-adding-issues question is untouched, as the issue says.
To try it: label an issue flow with the button on its page or in the issues list, then check /alice/repo/map. It should lead "Ready now".
🤖 Generated with Claude Code
Parked by the crew: the check failed ("migrations are additive across a roll > every migration not in both releases still in play is additive") and the decider saw no point in another try try 1: README.md, docs/MCP.md, docs/STATUS.md, docs/design/areas/flow-first.md (+53 more)
The Flow only toggle is gone, and
flowalone now decides what goes first. I ran about 270 tests, includingtest/flow-first.test.ts,test/mcp-labels.test.tsandtest/mcp-size.test.ts, plustscanddesign-lint; all pass. I did not run the whole suite, since the forge runs it on push. The push went through after a pre-push hook added a migration pin commit (3c4d2050).Ordering
readyNowinsrc/core/dependencies.tsis the one place that orders ready work. Issues labelledflowcome first; everything else keeps its old order, so with no labelled issue nothing changes.flow ·prefix on each such row.What was deleted
crew/flow_only.ts,crew/flow_label.ts,flow/flow_only_auto.ts,web/flow_only_line.ts.wkey and About row.flowOnlyfield in the API, OpenAPI and MCPrepo_settings, plus the "queued: flow only" line everywhere.flow_onlyheld-filter, and the held-pull comment inrequested.ts.repo.flow_onlyand theflow_only_watchtable.Held assignments are no longer held. The existing startup sweep dispatches them, and a test checks that an assignment of unlabelled work runs.
Applying the label
POST /:owner/:name/issues/:number/flow, which creates theflowlabel on first use.labelstakes an optionalactionofset,addorremove. The size test passes without raising any ceiling.Choices and leftovers
row-aftersibling. This new CSS class is named indocs/design/areas/flow-first.md.flow_only.clearedinevent_audience.ts, so old events from the retired switch stay admin-only.To try it: label an issue
flowwith the button on its page or in the issues list, then check/alice/repo/map. It should lead "Ready now".🤖 Generated with Claude Code
Closes #7636