Repository navigation
docs: kontext dispatch in DESIGN, the README and the pm's skills - #58
Merged
Merged
Conversation
OmarAlex24
force-pushed
the
dispatch/docs
branch
from
November 16, 2026 22:53
f99ba07 to
1a44ce6
Compare
OmarAlex24
force-pushed
the
dispatch/docs
branch
from
November 16, 2026 22:53
1a44ce6 to
5644943
Compare
DESIGN gets §12.5 (the checks, the steps, the watcher, the state and the adapter) and §1, §10, §11 and §12.1 now say kontext dispatches an epic to a sandbox and what it still does not decide. The README says how to dispatch and how the tests fake Boat. kontext-orchestrate and kontext-pm launch the waves of an XL project with `kontext dispatch` and give small epics no sandbox; their new hashes go in skill-versions.txt. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
OmarAlex24
force-pushed
the
dispatch/docs
branch
from
November 16, 2026 22:59
5644943 to
66cdcd9
Compare
22 tasks done
OmarAlex24
marked this pull request as ready for review
November 17, 2026 14:30
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.
Top of the
kontext dispatchstack: the docs and the pm's skills. It also holds the steps of the real-Boat test, which nothing in this stack has run.What changed and why
kontext dispatch": the checks, the steps in order, the watcher, the state, the adapter, and what is not verified against Boat yet;[dispatch]table in §11.[dispatch]table;boatand never reach Boat.kontext-orchestrate: in an XL project with a signed plan, the pm launches each wave's epics withkontext dispatch(a new first row in the harness table), and an epic that is one small task gets no sandbox;kontext-pm§10: launching a wave with sandboxes;templates/skill-versions.txt, as for every template change, so older installs are seen as older versions.Departures from the brief
kontext-coordinator.mdis unchanged: the prompt points at it and atkontext brief, and it already says what a coordinator in a sandbox needs (ask the pm, close the epic with evidence).Not verified (no
boatcommand that makes or drives a sandbox was run)boat new,boat infoandboat prompt --jsonprint (the adapter takes thereadyevent's id,setupStatus/setupError, andconversationIdat the top or underdata);HOMEit runs as;-evariables reach the agent's session;boat promptreturns 0 when a turn ends normally.The real-Boat test (the owner's)
Against a local server through
boat forward --reverse, never the deployed Worker. Use the stack's binary, not~/.cargo/bin/kontext, with a kontext config of its own.cargo build --release, and setkx=<target>/release/kontext. In every shell below:export KONTEXT_CONFIG_DIR=$(mktemp -d)(the same folder) so the real kontext config is never touched.cd server && npm ci && node dev.mjs --port 8787 --persist <a folder>.KONTEXT_ADMIN_SECRET=dev-admin-secret $kx init boattest --home <a folder> --server http://127.0.0.1:8787. In itsproject.toml:owners = ["<you>"], a[[repos]]with a scratch GitHub repo, and[dispatch]withenvironment = "<a Boat environment that can clone that repo>"(andhours = 1for a short test). Then$kx --project boattest sync --include-config.charter --objective …andsign,goal add …andsign,epic add "Docs" --goal <G> --name docs, twotask add … --epic docs --acceptance …, thenscope summary --jsonandscope sign --hash <hash>.$kx --project boattest dispatch nosuchexits 2 with one line.$kx --project boattest dispatch docs. When it printssandbox bx_… made, in a second shell:boat forward bx_… --reverse --local 8787(the start script retrieskontext clonefor 10 minutes). Watch it print the start script done, the coordinator prompted and the watcher's pid.boat info bx_… --jsonshowssetupStatusdone; inside the sandbox (boat sshorboat exec)~/.kontext-dispatch-tokenis gone,kontext --versionis the pinned release,git statusin the repo is clean, andkontext brief docsworks;$kx --project boattest dispatch statusshows the epic running and the watcher alive.boat infoshows it stopped, not deleted), revokes the token ($kx --project boattest token list), anddispatch statussaysclosed.$kx --project boattest --actor agent:pm --role pm resume); kill the watcher, rundispatch status(it says how to restart it), restart it withdispatch watch --detachand see it pick up;dispatch stop <epic>.boat events bx_…, the watcher's log andstate.jsonunder$KONTEXT_CONFIG_DIR/dispatch/boattest/: nokxt1..boat stopanything left; the Boat sandboxes' data goes after 14 days.Test plan
cargo fmt --check,cargo clippy --all-targets -- -D warningsand the fullcargo test(42 suites, 497 tests, the template-version tests included) passed at this commit (fresh worktree and target dir, before the placeholder edit below; that edit only changed two example lines in README and DESIGN)templates/skill-versions.txt(the install test that requires it passes)src/dispatch/mod.rs(the ids are made up)🤖 Generated with Claude Code