docs(swarm): mark "one lifecycle for N executors" RESOLVED (#294)#437
Merged
Conversation
docs/swarm.md still listed per-slice closure as a Known limitation with `gate complete` firing once for the whole wave. #294 (per- executor slice closure) shipped that since: `gate complete --by X` is now per-slice, and the wave transitions to completed only when every executor's slice is terminal. Surfaced by running the worked sequence for real — `complete --by agent-alpha` on a two-slice wave reports "open slices remaining: agent-beta" and leaves the wave executing; the final --by auto- transitions it. Two drift spots fixed: - Known-limitations item struck through (kept for the trail) with the resolved behavior + executors object-shape / jq migration note. - step-7 code comment in the worked sequence ("one complete — lifecycle is wave-scoped, not per-executor") updated to the per- slice `complete --by <each>` shape. Wording verified against CHANGELOG #294 and the runtime strings (requestLifecycle.ts "open slices remaining", transcript.ts "all slices closed").
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
1 participant
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.
What
docs/swarm.mdstill listed per-slice closure as a Knownlimitation — "
gate completefires once for the wave even whenmultiple executors finished different slices; per-slice closure is
not first-class." But #294
(per-executor slice closure) shipped that since. This is doc drift,
not a behavior change.
How it surfaced
Running the worked sequence in § Swarm × Claude SubAgent harness
for real (a two-slice
agent-alpha/agent-betawave on athrowaway
substrate/swarm-experiments/content_root):completeis per-executor; the wave auto-transitions only when thelast slice closes. The docs described the pre-#294 shape.
Changes (docs only)
the file's own "items are the trail behind the rule" convention)
with the resolved behavior + the
executorsobject-shape /jq '.executors[] | (.name // .)'migration note.lifecycle is wave-scoped, not per-executor") updated to the
per-slice
complete --by <each>shape with the auto-transition note..changelog/next/docs-swarm-per-slice-closure-resolved.md.Verification
Wording cross-checked against
CHANGELOG.md#294 entry(
any-fail-wave-failphase-1 default,#235 phase 2template-boundfollow-up) and the runtime strings (
requestLifecycle.ts"openslices remaining",
transcript.ts"all slices closed"). No codetouched; no tests affected.