Repository navigation
release: v0.5.36 - #210
Merged
Merged
release: v0.5.36#210
Conversation
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.
v0.5.36 — Two merged PRs, no milestone acceptance
Patch release. Two merged PRs since 0.5.35, verified end to end in CI and locally — M16 is not accepted yet, so this release carries no milestone claim.
Diagnostic sentences are not test-run claims (PR #207, merged 2026-11-16T08:40:26Z, squash b504fd4; fixes issue #201). The live-claims extractor now drops sentences reporting a command failing to run (failed spawn / ENOENT / command not found) from the claim set — they are diagnostic context, not assertions the agent made. Evidence:
node test/live-claims.test.js36 pass, 0 fail (7 new diagnostic-context tests); merged-main CI run 43833145541 success. Recovery note: the dispatch run was killed mid-flight by a VM runtime restart; the executor's uncommitted work survived in the run worktree and was verified, committed, and pushed by the operator — ledger gap disclosed in swrm #244.pi_shim.sh executable so the openswarm arm can run (PR #209, merged 2026-11-16T14:18:45Z, squash 28d6416; fixes issue #208).
bench/swebench/harness/pi_shim.shmode 100644 → 100755, content unchanged, plus a new regression test asserting the exec bit, the committed mode, the shebang, and theOPENSWARM_PI_BINwiring. The shim was non-executable, so every openswarm cell in the M16 MiniMax pilot died in ~1s with statusunroutable("no working pi binary") — 0/6, an infrastructure failure, not a model signal. Evidence, independently re-run by the main round on PR head 84b4a88: new test 4/4 pass; related suites + live-claims 43/43 pass; negative control (mode reverted) fails with EACCES; merged-main CI run 43884400880 success.Honest note, stated plainly: milestone M16 is not accepted in this release — the pilot ran 24/24 complete (baseline 1/6, superpowers 4/6, openflow 1/6, openswarm 0/6), and the openswarm 0/6 was the infrastructure failure fixed by PR #209; the openswarm re-run is pending. No bench numbers are claimed in this release.
Acceptance ledger, stated plainly: the issue #5 ledger is settled as a conclusion on the MiniMax full-matrix recheck (135/135 complete, 2026-11-10) — P2-1 passed, P1-2 / P1-3 / P2-3 did not pass — so no bench numbers are claimed in this release.
Local check on this branch: full suite across all 73 test files — 817 tests, 812 pass, 4 fail, 1 skipped. The 4 failures are the same pre-existing I6d environment failures as the 0.5.35 baseline (
pytestnot on PATH in this VM: 1 in test/i6d-acceptance-demo.test.js, 3 in the I6d assertion-execution gate suite of test/xflow-audit.test.js, allspawnSync pytest ENOENT); the +11 tests / +11 pass over the 0.5.35 baseline (806 / 801) are exactly the 7 new live-claims tests from #207 plus the 4 new shim tests from #209 — zero regression. Note:npm test(scripts/run-tests.mjs) is fail-fast and stops at the first failing file, so the full count was measured with a singlenode --test test/*.test.jsrun; this branch changes version/docs files only. Files changed: CHANGELOG.md, RELEASE_NOTES.md, docs/launch-dossier.md, package.json, package-lock.json (same 5 files as release PR #200).