Skip to content

fix: register planningModel config section + planning-model tracking docs - #75

Merged
mbuckaway merged 3 commits into
fork/mainfrom
feat/planning-model-ship
Aug 28, 2026
Merged

fix: register planningModel config section + planning-model tracking docs#75
mbuckaway merged 3 commits into
fork/mainfrom
feat/planning-model-ship

Conversation

@mbuckaway

Copy link
Copy Markdown
Owner

Related Issue

Follow-up to the planning-model feature merged via #72/#73 and released as 0.36.0-MB.1.25.

Problem

The planningModel config section was declared in agent-core-v2 but never registered with registerConfigSection — it only worked through the generic scalar pass-through (no zod schema, no env binding, absent from the config manifest).

What changed

  • Register planningModel as a z.string().optional() config section and regenerate docs/config-manifest.toml (the configManifest test now passes).
  • Track the planning-model feature in fork/PATCHES.md.
  • Add docs/upstream-0.39.1-sync-report.md — the gap report and catch-up plan for upstream 0.36.1 → 0.39.1.

Tests

  • configManifest test green; full agent-core-v2 suite (5266 tests) green; v1 planning tests (51) green; typecheck clean; check-web-assets green.

@mbuckaway
mbuckaway merged commit 0637183 into fork/main Aug 28, 2026
12 checks passed
@mbuckaway
mbuckaway deleted the feat/planning-model-ship branch August 28, 2026 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant