Builder slots serve the roadmap first: tests-only and small-addition pulls get at most a set share of builder slots #7684

Builders now pick roadmap work first, and tests-only or small-addition issues can hold at most a set share of builder slots.

Pick order. Before the decider sees the ready list, driveRepo puts it in this order:

1. Issues under an open epic or a P0/P1 pillar.
2. Everything else.
3. Small issues.

Each group keeps the map's existing order. The rules live in a new module, src/crew/small_share.ts.

What counts as small. A title starting "A test pins/proves/shows/names/covers …", "Tests: …" or "Small: …", or a label tests, tests-only, test or small.

The cap. Small issues may hold ceil(slots × slots.smallShare / 100) slots: 2 of 5 at the default 30%, and 1 of 1. Once small issues fill that, the rest are dropped from this tick's pick list rather than waited on.

The setting. slots.smallShare is a new capacity key in src/core/capacity.ts: a percent from 0 to 100, default 30, environment variable FORGE_SLOTS_SMALL_SHARE. It shows up on /settings/capacity, the capacity API and the terminal like the other keys, and is read on every pick.

Visibility. Small issues in flight against their cap (2/2) appear in three places:

• the tick line, as small: 2/2;
• the app's row in Today on /boards (the old /pipeline panel lives there now);
• the studio crew panel.

docs/CREW.md describes all of this.

Tests. test/crew-small-share.test.ts drives the real loop with 5 builders and 5 slots:

• With only small issues ready, exactly 2 start and the share reads 2/2.
• When a slot frees up, an issue under an epic starts before the remaining small ones.

There are also unit tests for isSmall, smallCap and slotOrder. Type check and design lint pass, and the capacity, board, crew-pick, merge-queue, flow and mcp-size suites pass (224 tests). scripts/fast.ts named 1,356 of the 1,665 test files, so I picked the covering suites by hand rather than run them all.

Left out:

• "Small" is read from the title and labels only. A small terminal or MCP addition with neither pattern nor label isn't caught.
• No new MCP tool. The share shows on the tick line and pages, and the setting goes through the existing capacity API.
• Epic means any open issue that waits on this one, other than the pillar umbrellas, the Later gate and the Later umbrella.
• Roadmap order now outranks the "owner raised it again" order within the ready list.

To try: set slots.smallShare on /settings/capacity, open a few "A test pins …" issues on an autonomous app, and watch the small: field on the tick line and the app's row in Today on /boards.

🤖 Generated with Claude Code

Closes #7571

Builders now pick roadmap work first, and tests-only or small-addition issues can hold at most a set share of builder slots.

Pick order. Before the decider sees the ready list, driveRepo puts it in this order:

1. Issues under an open epic or a P0/P1 pillar.
2. Everything else.
3. Small issues.

Each group keeps the map's existing order. The rules live in a new module, src/crew/small_share.ts.

What counts as small. A title starting "A test pins/proves/shows/names/covers …", "Tests: …" or "Small: …", or a label tests, tests-only, test or small.

The cap. Small issues may hold ceil(slots × slots.smallShare / 100) slots: 2 of 5 at the default 30%, and 1 of 1. Once small issues fill that, the rest are dropped from this tick's pick list rather than waited on.

The setting. slots.smallShare is a new capacity key in src/core/capacity.ts: a percent from 0 to 100, default 30, environment variable FORGE_SLOTS_SMALL_SHARE. It shows up on /settings/capacity, the capacity API and the terminal like the other keys, and is read on every pick.

Visibility. Small issues in flight against their cap (2/2) appear in three places:

• the tick line, as small: 2/2;
• the app's row in Today on /boards (the old /pipeline panel lives there now);
• the studio crew panel.

docs/CREW.md describes all of this.

Tests. test/crew-small-share.test.ts drives the real loop with 5 builders and 5 slots:

• With only small issues ready, exactly 2 start and the share reads 2/2.
• When a slot frees up, an issue under an epic starts before the remaining small ones.

There are also unit tests for isSmall, smallCap and slotOrder. Type check and design lint pass, and the capacity, board, crew-pick, merge-queue, flow and mcp-size suites pass (224 tests). scripts/fast.ts named 1,356 of the 1,665 test files, so I picked the covering suites by hand rather than run them all.

Left out:

• "Small" is read from the title and labels only. A small terminal or MCP addition with neither pattern nor label isn't caught.
• No new MCP tool. The share shows on the tick line and pages, and the setting goes through the existing capacity API.
• Epic means any open issue that waits on this one, other than the pillar umbrellas, the Later gate and the Later umbrella.
• Roadmap order now outranks the "owner raised it again" order within the ready list.

To try: set slots.smallShare on /settings/capacity, open a few "A test pins …" issues on an autonomous app, and watch the small: field on the tick line and the app's row in Today on /boards.

🤖 Generated with Claude Code

Builders now pick roadmap work first, and tests-only or small-addition issues can hold at most a set share of builder slots.

Pick order. Before the decider sees the ready list, driveRepo puts it in this order:

1. Issues under an open epic or a P0/P1 pillar.
2. Everything else.
3. Small issues.

Each group keeps the map's existing order. The rules live in a new module, src/crew/small_share.ts.

What counts as small. A title starting "A test pins/proves/shows/names/covers …", "Tests: …" or "Small: …", or a label tests, tests-only, test or small.

The cap. Small issues may hold ceil(slots × slots.smallShare / 100) slots: 2 of 5 at the default 30%, and 1 of 1. Once small issues fill that, the rest are dropped from this tick's pick list rather than waited on.

The setting. slots.smallShare is a new capacity key in src/core/capacity.ts: a percent from 0 to 100, default 30, environment variable FORGE_SLOTS_SMALL_SHARE. It shows up on /settings/capacity, the capacity API and the terminal like the other keys, and is read on every pick.

Visibility. Small issues in flight against their cap (2/2) appear in three places:

• the tick line, as small: 2/2;
• the app's row in Today on /boards (the old /pipeline panel lives there now);
• the studio crew panel.

docs/CREW.md describes all of this.

Tests. test/crew-small-share.test.ts drives the real loop with 5 builders and 5 slots:

• With only small issues ready, exactly 2 start and the share reads 2/2.
• When a slot frees up, an issue under an epic starts before the remaining small ones.

There are also unit tests for isSmall, smallCap and slotOrder. The first push failed the check's type check: the test passed a possibly-null assignee to createRun. That was a mistake in the test, now fixed; the type check and this test file pass again on the new push. The capacity, board, crew-pick, merge-queue, flow and mcp-size suites (224 tests) and the design lint passed before that fix, which touched only the test file. scripts/fast.ts named 1,356 of the 1,665 test files, so I picked the covering suites by hand rather than run them all.

Left out:

• "Small" is read from the title and labels only. A small terminal or MCP addition with neither pattern nor label isn't caught.
• No new MCP tool. The share shows on the tick line and pages, and the setting goes through the existing capacity API.
• Epic means any open issue that waits on this one, other than the pillar umbrellas, the Later gate and the Later umbrella.
• Roadmap order now outranks the "owner raised it again" order within the ready list.

To try: set slots.smallShare on /settings/capacity, open a few "A test pins …" issues on an autonomous app, and watch the small: field on the tick line and the app's row in Today on /boards.

🤖 Generated with Claude Code

Builder slots now serve the roadmap first. Small issues can hold at most slots.smallShare of a repository's builder slots, so roadmap work always has slots left. The crew page shows the current share as a "Small issues … slots" line next to the autonomy status.

This update merges main. The only conflict was in src/web/studio/crew.ts, and the merge keeps both sides:

• Imports: smallShareWords from this branch and governorSeen from main are both imported.
• Autonomy status list: the "Small issues" row stays, and the "Governor" row from main sits just below it.

Checks run after the merge:

• bun x tsc --noEmit passes.
• bun scripts/design-lint.ts reports nothing outside the design system.
• 64 tests pass across six files: autonomy, crew direction/autonomy, the two crew-governor suites, crew small share and governor log. scripts/fast.ts mapped the merge to 1364 test files, so I picked the ones covering this change. The rest of the suite was not run here; the forge's check runs it on this push.

To try it, open an app's crew settings in the preview. The "Small issues" line shows the share, and a "Governor" line appears when a governor reason is present.

🤖 Generated with Claude Code

Builder slots now serve the roadmap first. Of the startable issues, the crew picks what the owner raised again first. Next come issues under an open epic or a P0/P1 pillar, then other work, and small issues last.

An issue is small when its title reads like "A test pins …" or "Tests: …", or it carries a label test, tests, tests-only or small. Small issues hold at most slots.smallShare percent of the builder slots. The default is 30, rounded up, so 2 of 5. An admin sets it on /settings/capacity. At the cap a small issue is skipped, not waited on.

The share shows in four places:

• the tick line: small: 1/2
• the terminal's Flow command, at the end of each app's line: small 1/2
• the app's row in Today on /board: small issues: 1 of 2 slots
• the studio's crew panel: "Small issues 1/2 slots"

Changes from review:

• Owner-raised order stays on top. slotOrder ranks raised issues above roadmap work and keeps the map's order among them. A raised small issue still counts against the cap: the share is the admin's limit, and at 0 it starts none.
• Terminal. The share is added to the Flow rows in flow/held.ts, and heldLines prints it.
• Tests that fail without the feature, in test/crew-small-share.test.ts:

- the /board Today row, the studio crew panel on /alice/notes/settings, and the terminal's Flow line - an owner-raised plain issue starting before an epic's issue - slots.smallShare posted on /settings/capacity: 0 starts no small issue, 100 does, and 101, -1 and "half" are refused with the value left at 100

• Docs match code. test is listed among the small labels in CREW.md, the module comment and the capacity help. shareWords' comment now says it returns 1/2.
• Nits. The board.ts import is back in order. The Today row reads small issues: 1 of 2 slots, built by smallIssuesWords from the new smallShareOf.

bun x tsc --noEmit passes and the design lint reports nothing. The small-share, held, board, studio-runs, capacity and autonomy test files pass (126 tests); the rest of the suite runs in the forge's check on this push.

To try it, open /board and an app's settings page in the preview, or set slots.smallShare on /settings/capacity.

🤖 Generated with Claude Code