@surlymochan/evalid 0.5.7 → 0.5.8

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 CHANGED
@@ -5,6 +5,16 @@ All notable changes to this project are documented here. Detailed notes live in
5
5
 
6
6
  ## [Unreleased]
7
7
 
8
+ ## [0.5.8] - 2026-11-08
9
+
10
+ ### Added
11
+ - **README Commands section (#54)**: README had no single command reference; top-level commands were only scattered through prose examples. A Commands section after "3 Minute Start" now lists all 31 top-level commands with a one-line description each, and states explicitly that the installed binary is `xflow` (there is no `evalid` binary). Every entry was checked against live `--help` output (`node bin/xflow.js --help` plus `xflow <command> --help` for all 31 commands, including subcommand lists for spec/qa/visual/launch/adoption/package/demo/goal/atom/host/compare). No CLI behaviour changed; docs only. Test evidence: `npm test` 46 files / 373 tests / 372 pass / 0 fail / 1 skipped (pre-existing).
12
+
13
+ ### Changed
14
+ - **CI actions bumped to v7 (#55)**: `actions/checkout` v4 → v7.0.1 and `actions/setup-node` v4 → v7.1.0, in both workflows (ci.yml, npm-publish.yml — 4 pin sites). Both v4 actions ran on the Node 20 runtime and CI reported Node 20 deprecation warnings; v7 runs on node24 (`runs.using: node24`, read from the action.yml files), so the warnings go away. No behaviour change for this repo: the only trigger events are push / pull_request / release / workflow_dispatch, so checkout v7's fork-PR guard for pull_request_target / workflow_run does not apply; setup-node v7's removal of the dummy NODE_AUTH_TOKEN export does not affect npm Trusted Publishing (OIDC), which npm-publish.yml uses and which never sets NODE_AUTH_TOKEN; node-version stays '22' with cache: npm unchanged. Test evidence: `npm run verify` exit 0 on the merged tree.
15
+
16
+ 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.
17
+
8
18
  ## [0.5.7] - 2026-11-08
9
19
 
10
20
  ### Added
package/README.md CHANGED
@@ -149,6 +149,46 @@ node bin/xflow.js compare codex-goal
149
149
  node bin/xflow.js launch copy
150
150
  ```
151
151
 
152
+ ## Commands
153
+
154
+ The installed binary is `xflow` (`npm install -g evalid` installs the `xflow` CLI). Every
155
+ top-level command below was verified against `xflow <command> --help` at v0.5.7; run
156
+ `xflow --help` for the full list with examples, or `xflow <command> --help` for one command.
157
+
158
+ | Command | What it does |
159
+ | --- | --- |
160
+ | `xflow workflow run \| validate <yaml>` | Run a workflow (`yolo` / `corps` / a YAML path), or validate its YAML as preflight |
161
+ | `xflow corps` | Run the heavy product/multi-agent workflow through its governed entry point |
162
+ | `xflow proof` | Verify workflow completion evidence and write the proof file |
163
+ | `xflow doctor` | Check local xflow readiness: package scripts, workflow YAMLs, skill topology |
164
+ | `xflow init` | Create project-local `.as-xflow/config.json` with portable defaults |
165
+ | `xflow goal show \| set \| audit \| clear` | Manage the project-level `.xflow/GOAL.md` anchor |
166
+ | `xflow profile show \| set` | Manage the personal/team execution profile |
167
+ | `xflow policy validate` | Validate the effective policy overlay |
168
+ | `xflow intake recommend` | Recommend a workflow track and gate overlays from a demand profile |
169
+ | `xflow evaluate` | One-shot external evaluator brief: quality score, blockers, next actions |
170
+ | `xflow release status` | Release-owner publish status: current blocker, package evidence, next action |
171
+ | `xflow assess` | Public quality assessment for goal, yolo, corps and the skill family |
172
+ | `xflow demo launch \| clean` | Show launch demo paths, or run the clean-project adoption smoke |
173
+ | `xflow launch audit \| dossier \| claims \| copy` | Audit launch readiness, or print the dossier, claimable statements, or safe launch copy |
174
+ | `xflow adoption validate \| init \| kit \| trial \| brief \| status` | Validate real adoption evidence records, or guide an external trial |
175
+ | `xflow package audit \| preflight \| status` | Validate npm package evidence; preflight checks publish prerequisites without publishing |
176
+ | `xflow score` | Print the competitive readiness score |
177
+ | `xflow objective` | Audit the top-level product objective against proof from source checkout |
178
+ | `xflow compare <system>` | Evidence-backed comparison against `superpowers`, `codex-goal`, `super-assistant`, `openspec`, `gstack`, or `spec-kit` |
179
+ | `xflow adapter import-file` | Import a generic tracker item JSON into `specs/changes/<change-id>/` |
180
+ | `xflow spec start \| delta \| openspec-map` | Scaffold specs, generate a spec delta review, or map an OpenSpec layout |
181
+ | `xflow qa capture \| review \| ship \| benchmark` | Browser-QA capture with QA-focused defaults, packaged as review, ship-gate, or benchmark |
182
+ | `xflow host status \| sync \| diff` | Show or maintain installed xflow skill copies across host roots |
183
+ | `xflow coach <topic>` | Concise execution checklist (`bugfix`, `feature`, `review`, `qa`, `ship`, `tdd`, `debug`, `red`, `green`, `verify`) |
184
+ | `xflow role <role>` | Named specialist operator surface (`developer`, `reviewer`, `qa`, `release`, `product`) |
185
+ | `xflow visual capture-page-evidence \| export-dom-rects \| export-visual-tokens \| diff-images \| render-report` | Screenshot/DOM capture and visual-token / image-diff tooling |
186
+ | `xflow quickstart` | Copy-paste-safe first-run commands |
187
+ | `xflow guide` | The human-facing delivery loop in one screen |
188
+ | `xflow gate ack <phase>` | Approve a pending human gate so a run can resume |
189
+ | `xflow atom list \| show \| run` | List, inspect, or run a single registered atom directly |
190
+ | `xflow serve` | Start the HTTP control plane for heavy-track workflows |
191
+
152
192
  ## Run a change
153
193
 
154
194
  ```bash
package/RELEASE_NOTES.md CHANGED
@@ -1,5 +1,15 @@
1
1
  # Release Notes
2
2
 
3
+ ## 0.5.8 - README command reference; CI actions to v7
4
+
5
+ Patch release. One docs addition and one CI maintenance bump since 0.5.7, both verified by the full test suite.
6
+
7
+ **README Commands section (#54).** README now has a single command reference after "3 Minute Start": all 31 top-level xflow commands with a one-line description each, verified against live `--help` output, and an explicit note that the installed binary is `xflow` (there is no `evalid` binary). Docs only — no CLI behaviour changed. Test evidence: `npm test` 373 tests / 372 pass / 0 fail / 1 skipped.
8
+
9
+ **CI actions bumped to v7 (#55).** `actions/checkout` v4 → v7.0.1 and `actions/setup-node` v4 → v7.1.0 across both workflows (4 pin sites). Both v7 actions run on node24, clearing the Node 20 deprecation warnings CI reported under v4. No behaviour change for this repo: the fork-PR guard in checkout v7 does not apply to this repo's trigger events, and setup-node v7's removal of the dummy NODE_AUTH_TOKEN export does not affect the OIDC Trusted Publishing flow in npm-publish.yml. Test evidence: `npm run verify` exit 0 on the merged tree.
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.7 - Coverage config (c8)
4
14
 
5
15
  Patch release. One addition since 0.5.6, verified by the full test suite.
@@ -1,6 +1,6 @@
1
1
  # evalid Launch Dossier
2
2
 
3
- Generated: 2026-11-07T17:29:14.617Z
3
+ Generated: 2026-11-07T21:23:51.607Z
4
4
  Mode: post_publish
5
5
  Verdict: conditionally ready: engine and adoption evidence are strong, registry publication remains required for a splash launch
6
6
  Launch ready: not yet
@@ -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.7
120
+ - Package name/version: @surlymochan/evalid@0.5.8
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.7",
3
+ "version": "0.5.8",
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",