Repository navigation
feat(scaffold): target SolverForge 0.31.1 - #19
Merged
Merged
Conversation
Generated projects now depend on solverforge 0.31.1, so a scaffold builds against the release that carries list element groups, joint cascading groups, planning ids in constraint matches, the resolved phase plan in final telemetry and the list-shadow row rescoring. Hosts that link a generated project's domain and constraints into their own SolverForge build, such as the SolverForge Workbench, need the project on the same release; on 0.26.1 the project's Plan implements a different crate's traits and cannot be hosted. The neutral templates compile unchanged against 0.31.1; the scaffold assertions move to the new target.
Status, snapshot, SSE and telemetry payloads now carry resolvedPhasePlan, projected from the runtime's final telemetry since SolverForge 0.28.0: every phase the solve ran, the construction chosen for each default stage and why, the move families and their limits, the acceptor and the forager. It is null while the job solves and set once it ends, so a client reads the policy that actually produced a result instead of reconstructing it from solver.toml defaults. The scaffold contract asserts the projection, and the scalar runtime pipeline asserts it is null while solving and populated once the job completes.
The README, wireframe, agent guide and modeling skill name the runtime the scaffold now targets. Each statement that rests on the runtime was rechecked against the 0.31.1 sources before moving it: BendableScore still has no ParseableScore, there is still no for_each_unique_pair, and SelectorTelemetry still carries no conflict-repair counters.
The published gate, checkout baseline, coverage and release-state lines move to 0.31.1, and each release from 0.27.0 to 0.31.1 gets a line saying what reaches generated apps: the 0.28.0 resolved phase plan, now projected in telemetry, and the opt-in 0.31.0 element groups and joint cascading groups the neutral scaffold leaves out. The rest needs no template change and arrives through the version pin.
GitHub's ubuntu-latest image is now ubuntu-26.04. Playwright 1.59.1 has no Chromium build for it, so `make install-e2e` aborted the Integration Tests job before pre-commit and the integration suites ran. Chromium downloads for ubuntu26.04-x64 start at 1.61.0.
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.
Generated projects now target
solverforge 0.31.1(was 0.26.1).Why
A host that links a generated project's
domain::Planandcreate_constraintsinto its own SolverForge build needs the project on the same release. On 0.26.1 the project'sPlanimplements another crate's traits: building such a host against 0.31.1 fails withthe trait bound Plan: Solvable is not satisfiedandthere are multiple different versions of crate solverforge_core in the dependency graph.Changes
feat(scaffold): the runtime target constants and scaffold assertions move to 0.31.1. The neutral templates compile against 0.31.1 unchanged; every shell (web, api, cli, mcp) was scaffolded and checked.feat(telemetry): 0.28.0 addedresolved_phase_plantoSolverTelemetry, and the scaffold contract projects every telemetry aggregate. Status, snapshot, SSE and telemetry payloads now carryresolvedPhasePlan:nullwhile solving, and the phase plan the solve ran once it ends.docs(scaffold): README, WIREFRAME, AGENTS and the modeling skill name 0.31.1. Each runtime claim was rechecked on 0.31.1:BendableScorestill has noParseableScore, there is still nofor_each_unique_pair, andSelectorTelemetrystill has no conflict-repair counters.docs(audit): one line per release from 0.27.0 to 0.31.1, plus the current-state lines.Verification
cargo test --bin solverforge: 238 passedscaffold_test: 43 passedruntime_pipeline_test: 3 passedruntime_mcp_pipeline_test: 2 passedinstall_skill_test(20 passed) andskill_references_test(1 passed)cargo fmt --check, templaterustfmt --checkandclippy -D warnings: cleannpm run test:e2e: 3 passedsolverforge 0.31.1(cargo generate-lockfileon a fresh scaffold).resolvedPhasePlanprojection fails the scaffold assertion and the scalar runtime pipeline ("a completed job should report the phase plan it ran").