@3f-consulting/spec-controller-core 0.1.0-alpha.65 → 0.1.0-alpha.66

package/README.md

@@ -38,7 +38,7 @@ isBalanced(ledger); // false while any scenario names evidence that did not arri
 
 ## What is on the barrel
 
-- **Parse** — `parseScenarios`, `parseUntaggedScenarios` and `countScnOccurrences`; `parseVitestEvidenceObservations`, `parseCucumberEvidenceObservations`; the readers for static checks and for what a pipeline's steps actually ran.
+- **Parse** — `parseScenarios`, `parseUntaggedScenarios` and `countScnOccurrences`; `parseVitestEvidenceObservations`, `parseCucumberEvidenceObservations`; the readers for fitness functions and for what a pipeline's steps actually ran.
 - **Reconcile** — `reconcile` for the ledger itself, `evidenceReconciliationOf` for the ledger plus its summary, and `evidenceReconciliationFromSources` for the whole composition over sources you have already read.
 - **Ask the ledger** — `isBalanced`, `hasPendingItems`, `hasBrokenEvidence`, `hasNothingToReconcile`. These are the four questions a caller decides on: the CLI's own balanced / out-of-balance / unsound / pending-under-strict / nothing-to-reconcile verdicts are built out of these four and nothing else.
 - **Render** — `renderMarkdown`, `renderJson`, `renderReport`, `renderReportFromJson`, and `assembleRenderInput` if you want the payload rather than a string.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@3f-consulting/spec-controller-core",
-  "version": "0.1.0-alpha.65",
+  "version": "0.1.0-alpha.66",
   "description": "The pure, embeddable reconciliation core behind spec-controller — Gherkin/@SCN parse, the evidence model, reconcile primitives, and renderers. No CLI, no I/O.",
   "keywords": [
     "reconciliation",