@surlymochan/evalid 0.5.10 → 0.5.11
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +8 -0
- package/RELEASE_NOTES.md +10 -0
- package/docs/launch-dossier.md +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,14 @@ All notable changes to this project are documented here. Detailed notes live in
|
|
|
5
5
|
|
|
6
6
|
## [Unreleased]
|
|
7
7
|
|
|
8
|
+
## [0.5.11] - 2026-11-08
|
|
9
|
+
|
|
10
|
+
### Added
|
|
11
|
+
- **Codex app bridge atom coverage (#63)**: `src/agent_team/atoms/codex-app-bridge.js` (I5 `codex.app_bridge`) was at 0% coverage. Added 6 tests to `test/heavy-atoms.test.js` covering the default local-bridge placeholder return, input.phase preference over context.phase.id, empty-string and missing-phase fallbacks, and registry wiring. Test evidence: RED→GREEN (stubbed-throwing implementation failed all 6 new tests, then green after restore); `npm run coverage` 424 pass / 0 fail; coverage after: codex-app-bridge 100% (all four measures, was 0% before).
|
|
12
|
+
- **Visual layout competition atom coverage (#64)**: `src/agent_team/atoms/visual/layout-competition.js` (H3b `visual.layout_competition`) was at 0% coverage. Added 4 tests to `test/heavy-atoms.test.js` covering `layout_competition.json` writing with the fixed phase and summary (verdict accept / confidence 0.76, two findings), the fixed phase winning over input/context phase names, the missing-change_id error, and registry wiring. Test evidence: RED→GREEN (an intentionally wrong assertion failed, then green after restore); `node test/heavy-atoms.test.js` 64 pass / 0 fail; `npm run coverage` 429 tests / 428 pass / 0 fail / 1 skipped (pre-existing); coverage after: layout-competition 100 / 100 / 100 / 100 (was 0% before).
|
|
13
|
+
|
|
14
|
+
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.
|
|
15
|
+
|
|
8
16
|
## [0.5.10] - 2026-11-08
|
|
9
17
|
|
|
10
18
|
### Added
|
package/RELEASE_NOTES.md
CHANGED
|
@@ -1,5 +1,15 @@
|
|
|
1
1
|
# Release Notes
|
|
2
2
|
|
|
3
|
+
## 0.5.11 - Codex app bridge and layout competition atoms test coverage
|
|
4
|
+
|
|
5
|
+
Patch release. Two test-coverage additions since 0.5.10, both verified by the full test suite. No runtime behaviour changed.
|
|
6
|
+
|
|
7
|
+
**Codex app bridge atom coverage (#63).** I5 `codex.app_bridge` (`src/agent_team/atoms/codex-app-bridge.js`) now has 6 tests in `test/heavy-atoms.test.js`, covering the default local-bridge placeholder return, input.phase preference over context.phase.id, empty-string and missing-phase fallbacks, and registry wiring. Coverage went from 0% to 100% on all four measures. Test evidence: RED→GREEN verified (stubbed-throwing implementation failed all 6 new tests, then green after restore); `npm run coverage` 424 pass / 0 fail.
|
|
8
|
+
|
|
9
|
+
**Visual layout competition atom coverage (#64).** H3b `visual.layout_competition` (`src/agent_team/atoms/visual/layout-competition.js`) now has 4 tests in `test/heavy-atoms.test.js`, covering `layout_competition.json` writing with the fixed phase and summary (verdict accept / confidence 0.76, two findings), the fixed phase winning over input/context phase names, the missing-change_id error, and registry wiring. Coverage went from 0% to 100 / 100 / 100 / 100. Test evidence: RED→GREEN verified (an intentionally wrong assertion failed, then green after restore); `node test/heavy-atoms.test.js` 64 pass / 0 fail; `npm run coverage` 429 tests / 428 pass / 0 fail / 1 skipped (pre-existing).
|
|
10
|
+
|
|
11
|
+
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.
|
|
12
|
+
|
|
3
13
|
## 0.5.10 - Intake and phase-run fail atoms test coverage
|
|
4
14
|
|
|
5
15
|
Patch release. Two test-coverage additions since 0.5.9, both verified by the full test suite. No runtime behaviour changed.
|
package/docs/launch-dossier.md
CHANGED
|
@@ -117,7 +117,7 @@ Evidence:
|
|
|
117
117
|
- Adoption records: 1; status: pass
|
|
118
118
|
- 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.
|
|
119
119
|
- Package evidence: missing; source: registry_json
|
|
120
|
-
- Package name/version: @surlymochan/evalid@0.5.
|
|
120
|
+
- Package name/version: @surlymochan/evalid@0.5.11
|
|
121
121
|
|
|
122
122
|
## Passing Evidence
|
|
123
123
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@surlymochan/evalid",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.11",
|
|
4
4
|
"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.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"ai-agents",
|