Repository navigation
Conversation
added 2 commits
November 2, 2026 20:07
…(T171) A done that releases a ready task leaves it ready and says 'T202 done · T205 can start' on the board and the CLI. A broken [after] table starts nothing and shows on the board's status row.
|
Someone is attempting to deploy a commit to the smarzban Team on Vercel. A member of the Team first needs to authorize it. |
Author
|
Opened here by mistake; this belongs on my fork. Sorry for the noise. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
A done starts every ready task waiting on it, and an assigned one dispatches. Workflows that dispatch each next task by hand find this unexpected.
Change
[after]table inconfig.toml:start = true | false, defaulttrue(no change for existing boards). LoaderAfterSettingssits beside[merge]/[board]insrc/agents.rs.plan_released_with_hosttakes the setting. When it is off, each released task is reported asReleasedStart::CanStart. Nothing starts, nothing launches, and the done still saves through the same releasing save and undo entry. Every done path goes through it: boardctrl+d, cleanup card, missing-worktree converge (save_releasing_with_host), and CLIstatus done(run_done_with_host).T202 done · T205 can start, on the board status row and as the CLI's second line.[after]starts nothing until fixed, and a full board open shows the error on its status row. A file that is not valid TOML, or that cannot be read, also starts nothing, because the setting cannot be known.[after]commented out.storage.md(new### Aftersection, Errors row), links fromboard.md#afterandcli.mdDone,llms.txt, CHANGELOG Added, and the AGENTS.md invariant.Tests
dispatch::tests::after_start_off_or_broken_leaves_released_tasks_readyuses the fake host. It covers default, on, off, a bad value, and an unknown key, with an assigned and a plain dependent. Off or broken: both stay ready, nothing launches, and the message is exact. It fails with the gate reverted.cli_after::a_done_with_after_start_off_only_says_what_can_startchecks the exact CLI output.Green bar
cargo fmt --check,clippy -D warnings, andcargo test --no-fail-fastall ran on the pinned 1.96.0. Everything passes exceptgit_base::two_tsk_processes_on_one_state_dir_share_one_fetch, which also fails on unchangedmain(8d714a2) in this environment, so it is unrelated. Live herdr smoke was not run.