Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,16 @@
All notable changes to this project are documented here. Detailed notes live in
[RELEASE_NOTES.md](RELEASE_NOTES.md).

## [0.5.36] - 2026-11-16

### Fixed
- **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.js` 36 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.sh` mode 100644 → 100755, content unchanged, plus a new regression test asserting the exec bit, the committed mode, the shebang, and the `OPENSWARM_PI_BIN` wiring. The shim was non-executable, so every openswarm cell in the M16 MiniMax pilot died in ~1s with status `unroutable` ("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.

## [0.5.35] - 2026-11-15

### Added
Expand Down
12 changes: 12 additions & 0 deletions RELEASE_NOTES.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,17 @@
# Release Notes

## 0.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.js` 36 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.sh` mode 100644 → 100755, content unchanged, plus a new regression test asserting the exec bit, the committed mode, the shebang, and the `OPENSWARM_PI_BIN` wiring. The shim was non-executable, so every openswarm cell in the M16 MiniMax pilot died in ~1s with status `unroutable` ("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.

## 0.5.35 - Milestone M15 "实时运行时验证(live verify)" accepted

Milestone release. Three merged PRs since 0.5.34, verified end to end in CI and locally — and the milestone they complete is now accepted.
Expand Down
2 changes: 1 addition & 1 deletion docs/launch-dossier.md
Original file line number Diff line number Diff line change
Expand Up @@ -117,7 +117,7 @@ Evidence:
- Adoption records: 1; status: pass
- Goal audit: pass; goal: Keep evalid credible as an open-source agent delivery runtime: repo-owned workflow contracts, executable verification gates, durable project context, and honest benchmark evidence.
- Package evidence: missing; source: registry_json
- Package name/version: @surlymochan/evalid@0.5.35
- Package name/version: @surlymochan/evalid@0.5.36

## Passing Evidence

Expand Down
4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@surlymochan/evalid",
"version": "0.5.35",
"version": "0.5.36",
"description": "Claimed != verified: a runtime verification layer for coding agents. It seals each test run and replays it from a clean snapshot, with a zero-judge gate pipeline (spec clarification, code review, TDD proof) and the xflow CLI.",
"keywords": [
"ai-agents",
Expand Down