releases

solverforge-cli 3.2.x through 3.5.x: Scaffold Targets and the MCP Shell

solverforge-cli 3.2.0 retargets fresh scaffolds to solverforge 0.19.7, 3.3.0 moves the MCP shell to rmcp 3.5.0, 3.3.2/3.3.3 fix generated constraint code, and 3.4.0/3.5.0/3.5.1/3.5.2 retarget scaffolds to newer cores.

solverforge-cli 3.3.1 was published on crates.io and released on GitHub (2026-09-29), so cargo install solverforge-cli installed 3.3.1 directly. The previous package, solverforge-cli 3.1.0, scaffolded solverforge 0.19.5, solverforge-ui 0.9.0, and rmcp 3.4.0. Use solverforge --version to confirm exactly what an installed binary carries.

Projects generated by the historical 3.3.1 release target:

  • solverforge 0.19.7
  • solverforge-ui 0.9.0 for the web shell
  • solverforge-maps 2.1.4 for the web shell
  • rmcp 3.5.0 for the MCP shell

What Changed

Scaffolds retarget to SolverForge 0.19.7

3.2.0 moves the scaffold runtime target to the published solverforge 0.19.7 core, so a fresh project starts on the current runtime instead of the previous line. The UI and maps targets are unchanged at solverforge-ui 0.9.0 and solverforge-maps 2.1.4.

solverforge --version

solverforge solverforge-cli 3.3.1
CLI version: 3.3.1
Scaffold runtime target: SolverForge crate target 0.19.7
Scaffold UI target: solverforge-ui 0.9.0
Scaffold maps target: solverforge-maps 2.1.4
Scaffold MCP target: rmcp 3.5.0

The MCP shell moves to rmcp 3.5.0

3.3.0 retargets the mcp shell to rmcp 3.5.0 as the Model Context Protocol client and server SDK. Projects scaffolded with --shell mcp pick up 3.5.0 in their own manifests, and the version output reports the target so an installed binary never leaves the SDK implicit.

The CLI’s own dependency baseline is aligned

3.3.1 brings the CLI’s own dependencies onto the current releases, including clap 4.6.7, clap_complete 4.6.11, serde 1.0.229, serde_json 1.0.151, owo-colors 4.4.0, syn 3.0.6, toml 1.1.6, toml_edit 0.25.15, and jsonc-parser 0.34. These are the CLI’s own crates rather than scaffold targets, so a generated project is unaffected.

3.5.2 retargets the runtime without changing the command surface

3.5.2 replaces the solverforge 0.21.2 scaffold target with 0.21.3. The CLI flags, templates, generators, shell transports, and default search configuration are unchanged from 3.5.1; UI, maps, and MCP targets remain 0.9.0, 2.1.4, and 3.5.1. Existing projects keep their own dependencies and configuration until edited.

The runtime update preserves net route-edge changes during list-precedence trial moves. Paired retract/insert notifications retain unchanged edges; interleaved owner retractions and trial undo are checked against fresh scores. It does not introduce a new generator flag or change list precedence hook metadata.

The 3.5.2 artifact was published on October 15, 2026 from source bb53b77. Its SHA-256 is 64356b66f1b99eb5408253e425c0ce2c3bd6ac3899028ad79df4ed57fad922a9. At that commit, CI, crates.io publication, and the GitHub Release workflow all completed successfully.

Published Version Boundaries

Surface Version Scaffold target
CLI (current) solverforge-cli 3.5.2 solverforge 0.21.3, web solverforge-ui 0.9.0 + solverforge-maps 2.1.4, MCP rmcp 3.5.1
CLI solverforge-cli 3.5.1 solverforge 0.21.2, web solverforge-ui 0.9.0 + solverforge-maps 2.1.4, MCP rmcp 3.5.1
CLI solverforge-cli 3.5.0 solverforge 0.21.0, web solverforge-ui 0.9.0 + solverforge-maps 2.1.4, MCP rmcp 3.5.1
CLI solverforge-cli 3.4.0 solverforge 0.20.4, web solverforge-ui 0.9.0 + solverforge-maps 2.1.4, MCP rmcp 3.5.1
CLI solverforge-cli 3.3.1 solverforge 0.19.7, web solverforge-ui 0.9.0 + solverforge-maps 2.1.4, MCP rmcp 3.5.0
CLI solverforge-cli 3.3.0 solverforge 0.19.7, web solverforge-ui 0.9.0 + solverforge-maps 2.1.4, MCP rmcp 3.5.0
CLI solverforge-cli 3.2.0 solverforge 0.19.7, web solverforge-ui 0.9.0 + solverforge-maps 2.1.4, MCP rmcp 3.4.0
CLI (previous line) solverforge-cli 3.1.0 solverforge 0.19.5, web solverforge-ui 0.9.0 + solverforge-maps 2.1.4, MCP rmcp 3.4.0

Patch History

Version Date Notes
3.5.2 2026-10-15 Retargets fresh scaffolds to solverforge 0.21.3, including the list-precedence net route-delta fix; no CLI command or template behavior change.
3.5.1 2026-10-14 Retargets fresh scaffolds to solverforge 0.21.2 and the MCP shell to rmcp 3.5.1.
3.5.0 2026-10-14 Retargets fresh scaffolds to solverforge 0.21.0 and the MCP shell to rmcp 3.5.1.
3.4.0 2026-10-14 Migrates the release toolchain to csemver, retargets fresh scaffolds to solverforge 0.20.4 and the MCP shell to rmcp 3.5.1, and adds network-outage retry to generated-app test commands.
3.3.3 2026-10-02 Rewrites every score-bearing surface on generate score and re-renders src/data/data_seed.rs on destroy; no scaffold-target change.
3.3.2 2026-10-01 Streams generated constraint skeletons from the #[planning_solution] accessors and aligns the bundled skill docs; no scaffold-target change.
3.3.1 2026-09-29 Aligns the CLI dependency baseline with the current releases; no scaffold-target change.
3.3.0 2026-09-29 Retargets the MCP shell to rmcp 3.5.0.
3.2.0 2026-09-29 Retargets fresh scaffolds to solverforge 0.19.7.
3.1.0 2026-09-16 Targets the latest released scaffold crates, writes MCP configs for opencode, Claude Code, and Cursor, consolidates the agent skills behind the agent-centric installer with ownership receipts, and fixes the MCP solve result schema.
3.0.0 2026-09-15 Adds the mcp scaffold shell, solverforge connect, countable scalar ranges, the full list-metadata flags, and the solverforge-modeling agent skill; moves fresh scaffolds to solverforge 0.19.4.

Upgrade Checklist

  • Re-run solverforge --version / solverforge -V after installing to confirm the binary’s scaffold targets.
  • Existing generated apps keep their own manifests; move them to solverforge 0.21.3 deliberately and run their model, config, and lifecycle tests. Fresh scaffolds target 0.21.3 and solverforge-ui 0.9.0.
  • MCP-shell projects scaffolded before 3.3.0 pin rmcp 3.4.0; moving to 3.5.1 is a dependency update in the project manifest, not a re-scaffold.

Use the CLI manual for the current command surface, the command reference for the --version output this release reports, and the MCP Shell page for the agent-facing delivery surface built on rmcp 3.5.1.