feat(swarm): add directive completion semantics - #62
Merged
Merged
Conversation
christopherjnelson
marked this pull request as ready for review
September 21, 2026 00:41
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.
Purpose
The 25-tick zero-swarm run showed that workers often finished short assignments and then waited for Zero's stall/periodic review. This PR adds deterministic mission completion before the paired live Jev-versus-deterministic-worker benchmark. It does not tune Jev, change the worker candidate policy, or change Zero's periodic cadence.
Changes
expandonly when the target is infected and controlled by its assigned worker;relocateandreinforceon arrival at their assigned targets; andevadeon arrival or after leaving previously high observed cleaning pressure. A reinforce target must be infected or adjacent to infection when issued.holdpersists until another review trigger.directive-completeas a Zero replan reason. The next strategic observation identifies the completed worker/directive pair, and the compact OpenRouter request supplies a per-worker completion flag.Validation
The repository owner confirmed the initial local checks passed. After the
open-only expand amendment, a coding subagent reran both local gates and they
passed:
No paid-provider test is part of this PR or CI. The next step after merging is the paired live
trail-hunter-v1A/B benchmark, with the same Zero model and scenario inputs for Jev and deterministic workers.