spec-controller 0.1.275 → 0.1.277
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/README.md +2 -2
- package/dist/cli.js +15543 -17114
- package/dist/spec-reconciliation.schema.json +258 -195
- package/package.json +2 -3
package/README.md
CHANGED
|
@@ -65,7 +65,7 @@ A scenario tagged `@unit` names an obligation: a unit test must exist and pass.
|
|
|
65
65
|
| `0` | balanced — every obligation has evidence, and that evidence holds |
|
|
66
66
|
| `1` | out-of-balance — the scenarios and the evidence disagree, and the report says where |
|
|
67
67
|
| `2` | usage — the invocation was wrong, or an input could not be read |
|
|
68
|
-
| `3` | not reconciled — the run could not be relied on. Its run verdict says why: `unsound`, when some evidence never ran; `claim-code-errors`, when a claim code is misfiled (the report lists it under
|
|
68
|
+
| `3` | not reconciled — the run could not be relied on. Its run verdict says why: `unsound`, when some evidence never ran; `claim-code-errors`, when a claim code is misfiled (the report lists it under `## Errors in the inputs`); or `nothing-to-reconcile`, when there is no Claim Reconciliation at all |
|
|
69
69
|
| `4` | unexpected error — the run stops on an error that no refusal names, and gives no verdict. One line on stderr names the error |
|
|
70
70
|
|
|
71
71
|
The tool writes the whole report before it sets the exit code, so a failing run still tells you why.
|
|
@@ -83,7 +83,7 @@ The tool writes the whole report before it sets the exit code, so a failing run
|
|
|
83
83
|
|
|
84
84
|
The refusal names the input, the path, and what was wrong with it. A well-formed report with nothing in it, such as a Vitest run that matched no test file, is read, not refused.
|
|
85
85
|
|
|
86
|
-
**An output location it cannot write is also `2`.** This covers a `--format` path that is read-only, is a directory, is under a regular file, or is in a directory that does not exist. The tool refuses it before it prints any report, and names the location and
|
|
86
|
+
**An output location it cannot write is also `2`.** This covers a `--format` path that is read-only, is a directory, is under a regular file, or is in a directory that does not exist. The tool refuses it before it prints any report, and names the location and why.
|
|
87
87
|
|
|
88
88
|
`--exit-zero` changes `1` to `0` and leaves every other code alone (see *Report first, gate later*).
|
|
89
89
|
|