@surlymochan/evalid 0.5.11 → 0.5.13

package/CHANGELOG.md

@@ -5,6 +5,23 @@ All notable changes to this project are documented here. Detailed notes live in
 
 ## [Unreleased]
 
+## [0.5.13] - 2026-11-09
+
+### Added
+- **Proof-seal verification GitHub Action (#71)**: new JavaScript action (`action.yml`, node22) that runs the existing i6b seal validator for one change-id/phase/attempt and exits non-zero unless the seal verifies and the clean replay matches the claim. Inputs: change-id, phase, attempt, project-root, tdd-mode; outputs: ok, verdict. Test evidence: 6 new tests in `test/github-action-verify-proof.test.js` (valid sealed green proof verifies; tampered proof fails with `binding_mismatch`; test drift after the seal fails with `green_tree_mismatch`; missing proof fails with `missing`; CLI entry exit 0/1; action.yml declares inputs and entry) 6/6 pass; RED→GREEN verified (`ERR_MODULE_NOT_FOUND` before the entry existed); PR CI run 42494536803 success.
+
+### Changed
+- **Removed dead phase-run-dispatch atom wrapper (#68)**: `src/agent_team/atoms/phase-run-dispatch.js` had zero callers — repo-wide grep finds only its own definition site, it is absent from `atoms/registry.json` and from the public `src/index.js` surface, and registry entry `I2.phase_run.dispatch` points elsewhere. No runtime behaviour changed. Test evidence: local full `npm test` 440 tests / 439 pass / 0 fail / 1 skipped (pre-existing); PR CI run 42483989723 verify pass.
+
+Acceptance debt, stated plainly: the bench-number acceptance for P1-2 / P1-3 / P2-1 / P2-3 still awaits the MiniMax full-matrix batch (15 instances × 4 arms × reps 3), which is stopped on MiniMax Token Plan quota exhaustion. No bench numbers are claimed in this release.
+
+## [0.5.12] - 2026-11-08
+
+### Added
+- **Policy resolve atom coverage (#66)**: `src/core/atoms/policy/resolve.js` (P1 `policy.resolve`) was at 0% coverage. Added 6 tests to `test/policy-overlay.test.js` covering personal-default resolution with `policy_effective.json` writing, change_id and execution_mode taken from input, `team_policy_missing` / `team_policy_invalid` passthrough, no artifact when no change id is supplied, and registry wiring. Test evidence: RED→GREEN (stubbed-throwing implementation failed the new tests, then green after restore); `node --test test/policy-overlay.test.js` 18 pass / 0 fail; `npm test` 435 tests / 434 pass / 0 fail / 1 skipped (pre-existing); coverage after: resolve.js 100% statements / 83.33% branches / 100% functions / 100% lines (was 0% before; the single uncovered branch is the `process.cwd()` fallback, untested by design to avoid polluting the repo).
+
+Acceptance debt, stated plainly: the bench-number acceptance for P1-2 / P1-3 / P2-1 / P2-3 still awaits the MiniMax full-matrix batch (15 instances × 4 arms × reps 3), which is stopped on MiniMax Token Plan quota exhaustion. No bench numbers are claimed in this release.
+
 ## [0.5.11] - 2026-11-08
 
 ### Added

package/RELEASE_NOTES.md

@@ -1,5 +1,23 @@
 # Release Notes
 
+## 0.5.13 - Proof-seal verification action
+
+Patch release. One new feature and one dead-code removal since 0.5.12, both verified by the test suite.
+
+**Proof-seal verification GitHub Action (#71).** A new JavaScript GitHub Action (`action.yml`, node22) runs the existing i6b seal validator for one change-id/phase/attempt and fails the check unless the seal verifies and the clean replay matches the claim, so a replay mismatch can no longer pass CI silently. Test evidence: 6 new tests in `test/github-action-verify-proof.test.js` 6/6 pass (valid sealed green proof verifies; tampered proof fails with `binding_mismatch`; test drift after the seal fails with `green_tree_mismatch`; missing proof fails with `missing`; CLI entry exit 0/1; action.yml declares inputs and entry); RED→GREEN verified; PR CI run 42494536803 success.
+
+**Removed dead phase-run-dispatch atom wrapper (#68).** `src/agent_team/atoms/phase-run-dispatch.js` had zero callers and is absent from the atom registry and the public surface, so the wrapper is gone with no behaviour change. Test evidence: local full `npm test` 440 tests / 439 pass / 0 fail / 1 skipped (pre-existing); PR CI run 42483989723 verify pass.
+
+Acceptance debt, stated plainly: the bench-number acceptance for P1-2, P1-3, P2-1 and P2-3 — the wall-clock/token/resolved lines from issue #5 — still awaits the MiniMax full-matrix batch (15 instances × 4 arms × reps 3), which is stopped on MiniMax Token Plan quota exhaustion. No bench numbers are claimed in this release.
+
+## 0.5.12 - Policy resolve atom test coverage
+
+Patch release. One test-coverage addition since 0.5.11, verified by the full test suite. No runtime behaviour changed.
+
+**Policy resolve atom coverage (#66).** P1 `policy.resolve` (`src/core/atoms/policy/resolve.js`) now has 6 tests in `test/policy-overlay.test.js`, covering personal-default resolution with `policy_effective.json` writing, change_id and execution_mode taken from input, `team_policy_missing` / `team_policy_invalid` passthrough, no artifact when no change id is supplied, and registry wiring. Coverage went from 0% to 100% statements / 83.33% branches / 100% functions / 100% lines (the single uncovered branch is the `process.cwd()` fallback, untested by design). Test evidence: RED→GREEN verified (stubbed-throwing implementation failed the new tests, then green after restore); `npm test` 435 tests / 434 pass / 0 fail / 1 skipped (pre-existing).
+
+Acceptance debt, stated plainly: the bench-number acceptance for P1-2, P1-3, P2-1 and P2-3 — the wall-clock/token/resolved lines from issue #5 — still awaits the MiniMax full-matrix batch (15 instances × 4 arms × reps 3), which is stopped on MiniMax Token Plan quota exhaustion. No bench numbers are claimed in this release.
+
 ## 0.5.11 - Codex app bridge and layout competition atoms test coverage
 
 Patch release. Two test-coverage additions since 0.5.10, both verified by the full test suite. No runtime behaviour changed.

package/docs/launch-dossier.md

@@ -1,6 +1,6 @@
 # evalid Launch Dossier
 
-Generated: 2026-11-08T01:34:24.683Z
+Generated: 2026-11-08T16:04:31.497Z
 Mode: post_publish
 Verdict: conditionally ready: engine and adoption evidence are strong, registry publication remains required for a splash launch
 Launch ready: not yet
@@ -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.11
+- Package name/version: @surlymochan/evalid@0.5.13
 
 ## Passing Evidence
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@surlymochan/evalid",
-  "version": "0.5.11",
+  "version": "0.5.13",
   "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",

package/src/agent_team/atoms/phase-run-dispatch.js

@@ -1,8 +0,0 @@
-import { synthesizePhaseArtifact } from '../common.js';
-
-export async function phaseRunDispatch(input = {}, context = {}) {
-  return synthesizePhaseArtifact(input, context, {
-    phase: input.phase || context.phase?.id || 'execute',
-    summary: 'Phase-run dispatch completed and execution evidence was recorded.',
-  });
-}