docs: sync docs with swarm-planner-v2 and schema v13 - #75
Merged
Merged
Conversation
PR #73 moved the Agent Zero planner to swarm-planner-v2 semantic strategic options and advanced the export schema to version 13, but README, ROADMAP, architecture, security, testing, gameplay, comparison, and archive docs still described swarm-planner-v1 and schema v12. - State schema v13 wherever current exports and archive imports are described, and that v12 and earlier are rejected - Describe the v2 option model: server-compiled options, opaque optionId selection, no raw H3 cell or agent IDs in the model request - Point the models/verify probe at swarm-planner-v2 - Drop the stale claim that full plans remain accepted; decodePlanChoice only accepts the compact optionId schema - Add a PR #73 entry to the roadmap's delivered migration list ADRs are left unchanged as decision history. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016aHdPe3nkZ7bEQRB33qwEm
christopherjnelson
marked this pull request as ready for review
September 29, 2026 18:37
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
2 participants
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.
Before: after #73, README, ROADMAP, architecture, security, testing, gameplay, comparison and archive docs still described
swarm-planner-v1and export schema 12. For example, the archive guide said it accepts only v12, but the code only accepts v13.After: every current-state statement describes schema 13 and
swarm-planner-v2. That covers the server-compiled semantic options, the opaqueoptionIdselection with no raw H3 cell or agent IDs in the model request, and themodels/verifyprobe contract. The docs now say that schema 12 and earlier are rejected.How: 8 docs are updated, and ROADMAP gets a PR #73 entry in the delivered migration list. ARCHITECTURE's claim that full plans remain accepted is removed, because
decodePlanChoice(packages/agent-runtime/src/swarm-planner.ts) accepts only the compactoptionIdschema. ADRs are left unchanged as decision history.Validation (run locally in the agent session):
pnpm validatepassed: format check, lint, typecheck, 247 tests, build.pnpm test:e2epassed (2/2), using the environment's preinstalled Chromium.🤖 Generated with Claude Code
https://claude.ai/code/session_016aHdPe3nkZ7bEQRB33qwEm
Generated by Claude Code