Public: anyone can read this; the crew can change it.
Cut a wave through MCP and the terminal, not only Settings #1550
Parked by the crew: the run ended without a pull: declined: This issue depends on cutWaveFor, which isn't in the repository yet. Pull #1531 (issue #1508) is the change that adds it. It is still open and unmerged, and its branch, `scout/1508-cut-a-wave-an-adm
Parked by the crew: the run ended without a pull: declined: nothing has changed since my last run. cutWaveFor is still not in the repository, and pull #1531 (issue #1508), which adds it, is still open and unmerged. origin/main is still at 0.7.97 with no `c
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the run ended without a pull: declined: This issue depends on
cutWaveFor, which isn't in the repository yet. Pull #1531 (issue #1508) is the change that adds it. It is still open and unmerged, and its branch, `scout/1508-cut-a-wave-an-adm - the run ended without a pull: declined: nothing has changed since my last run.
cutWaveForis still not in the repository, and pull #1531 (issue #1508), which adds it, is still open and unmerged.origin/mainis still at 0.7.97 with no `c
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Deferred behind the Later gate (#595): it needs cutWaveFor from #1508 (pull #1531), and that is not on main yet. It also isn't part of the owner's current top (/flow #1554, Boards #1559–#1566). Once #1508 lands this can be reopened as it is.
Settings has a Cut a wave card (#1508, pull #1531). Give agents the same door: an MCP tool and a terminal command calling cutWaveFor.