The planner fills each team's queue from the direction and its charter, in proportion to its dial #2838

Dispatch now hands builder starts to teams in proportion to their dials. The planner is now told which teams it owes work. The part where the forge itself makes sure every team gets planned work each day is not built.

bun x tsc --noEmit, the new test/team-share.test.ts, test/crew-teams.test.ts and test/agents.test.ts pass. I did not run the whole check.

What changed

• New module: src/crew/team_share.ts. An issue belongs to the team whose slug matches one of its labels, such as design. The module counts the last 24 hours of agent-run starts per team and reorders the queued runs so each team's share follows its dial.
• Unlabelled work: it takes whatever share the dials leave. A team with no dial only starts when no team with a share has work waiting. With every dial at 0, pump in src/crew/dispatch.ts is unchanged and runs oldest first.
• Planner brief: each planning run is told every team above 0: its dial, its charter, and how many labelled issues are open and opened in the last day. It is told to plan and label work for each team, and "NONE READY" is flagged for a team with no open issues. The code is teamLines in src/crew/brief.ts, fed from src/crew/runner.ts.
• Test: the day simulation is in test/team-share.test.ts. With design at 30% on a real database, 100 builder starts over 200 queued runs give design 28–32 of them. The file also covers FIFO with all dials at 0, an empty lane not blocking the rest, past starts counting against a share, and the brief text going only to planners.

What I left out

• The forge does not check that a team got planned work today. It relies on the planner following its brief.
• The planner has to create the team label and label each issue with two extra API calls, because /plan does not take labels yet.
• Dials still do not limit budget. Fairness counts all agent-run starts, not builders only.
• I did not change AGENTS.md (the repo has none), only the README line that said nothing read the dials.

To try it: set design to 30% at /settings/teams, label some issues design, and queue agent runs. About 30% of starts go to design.

Closes #2680

Dispatch now hands builder starts to teams in proportion to their dials. The planner is now told which teams it owes work. The part where the forge itself makes sure every team gets planned work each day is not built.

bun x tsc --noEmit, the new test/team-share.test.ts, test/crew-teams.test.ts and test/agents.test.ts pass. I did not run the whole check.

What changed

• New module: src/crew/team_share.ts. An issue belongs to the team whose slug matches one of its labels, such as design. The module counts the last 24 hours of agent-run starts per team and reorders the queued runs so each team's share follows its dial.
• Unlabelled work: it takes whatever share the dials leave. A team with no dial only starts when no team with a share has work waiting. With every dial at 0, pump in src/crew/dispatch.ts is unchanged and runs oldest first.
• Planner brief: each planning run is told every team above 0: its dial, its charter, and how many labelled issues are open and opened in the last day. It is told to plan and label work for each team, and "NONE READY" is flagged for a team with no open issues. The code is teamLines in src/crew/brief.ts, fed from src/crew/runner.ts.
• Test: the day simulation is in test/team-share.test.ts. With design at 30% on a real database, 100 builder starts over 200 queued runs give design 28–32 of them. The file also covers FIFO with all dials at 0, an empty lane not blocking the rest, past starts counting against a share, and the brief text going only to planners.

What I left out

• The forge does not check that a team got planned work today. It relies on the planner following its brief.
• The planner has to create the team label and label each issue with two extra API calls, because /plan does not take labels yet.
• Dials still do not limit budget. Fairness counts all agent-run starts, not builders only.
• I did not change AGENTS.md (the repo has none), only the README line that said nothing read the dials.

To try it: set design to 30% at /settings/teams, label some issues design, and queue agent runs. About 30% of starts go to design.

Dispatch now hands builder starts to teams in proportion to their dials. It no longer starves a zero-dial team's labelled work, and the pump and planner wiring are now tested. bun x tsc --noEmit, test/team-share.test.ts and test/team-dispatch.test.ts pass. I did not run the whole check.

What changed

• Zero-dial teams: a label for a team whose dial is 0 now counts as unlabelled work. teamOfIssues in src/crew/team_share.ts only matches teams with a dial above zero, and startsSince goes through it. A security issue with security at 0 keeps its place in line with other unlabelled work. test/team-share.test.ts covers the label going from dial 10 to 0 and back.
• Pump wiring: the new test/team-dispatch.test.ts queues five labelled and unlabelled issues, starts the crew with one slot and design at 60%, and checks the start order is Design one, Unlabelled one, Design two, Security work, Unlabelled two. This also checks that security work isn't starved. With byDials removed from pump, the test fails.
• Planner wiring: the same file assigns the direction issue to the planner. It checks the prompt the run receives contains "design (60% of builder starts)" and the charter. With owed removed from runner, the test fails.
• Tidy: team-share.test.ts imports teams.ts once and the as never casts are gone.

What I left out

• Effective share view: no page, terminal or MCP view shows it.
• Run counts: startsSince still counts planner and reviewer runs as starts, not only builders.
• Budget: the dial still doesn't limit budget.
• Daily planned work: nothing but the planner's brief enforces that each team has planned work every day.
• README: the Crew teams section now lists the first three of these.