feat: orchestrate zero-swarm two-stage ticks - #53
Merged
Merged
Conversation
christopherjnelson
marked this pull request as ready for review
September 20, 2026 03: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.
Summary
SwarmPlannerfor Agent Zero with bounded strategic observations, engine-generated target/action allowlists, and structured plans.zero-swarm-v1ticks as Zero plan → Jev worker choices → seeded engine resolution → atomic commit. Keep the legacy tick path intact.Validation
The repository owner confirmed final local validation passed:
pnpm validatepnpm test:e2eNew offline tests cover the two-stage path through the real engine, API response, planner and Jev failure behavior, directive reuse, cancellation and attempt retention, safe player-pressure export, and archive import.
Scope
This is PR B only. Agent Zero plans every tick. World Lab swarm presentation and persistent/event-driven directives remain later milestones. No live OpenRouter planning call was part of default validation.