spec-controller 0.1.202 → 0.1.204
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/dist/cli.js +10 -10
- package/package.json +2 -2
package/dist/cli.js
CHANGED
|
@@ -28566,8 +28566,8 @@ var init_messages4 = __esm({
|
|
|
28566
28566
|
[CoreMessage.ConfigurationWrongKind]: (entry, is, reads) => `${entry} is ${is} where ${reads} is read, so this run read it as absent.`,
|
|
28567
28567
|
[CoreMessage.ConfigurationUnknownKey]: (key) => `${key} is not a key the specController block reads, so this run read nothing from it.`,
|
|
28568
28568
|
[CoreMessage.RunIntegrityHeading]: "## Run integrity: unsound",
|
|
28569
|
-
[CoreMessage.OneProofNeverRan]: "1
|
|
28570
|
-
[CoreMessage.ProofsNeverRan]: (count) => `${count}
|
|
28569
|
+
[CoreMessage.OneProofNeverRan]: "1 Evidence Observation never ran to a result, so the behaviour it proves was never exercised.",
|
|
28570
|
+
[CoreMessage.ProofsNeverRan]: (count) => `${count} Evidence Observations never ran to a result, so the behaviours they prove were never exercised.`,
|
|
28571
28571
|
[CoreMessage.RunUnsound]: (proofs) => `**This run is unsound.** ${proofs} A broken proof sits on the row of the claim it names, as every Evidence Observation does. On a scenario's row, an Evidence Obligation of its kind of quality check that no other proof answers reads "${MISSING}", though its test may already be written. A broken proof on the row of a phantom claim or of the unnamed claim may be the proof behind any item of its kind of quality check that reads "${MISSING}", on any row. Fix what stopped each proof listed below from running, such as its test, the code it loads, its step definitions, its runner or the CI job that runs it. Then run them again and regenerate this report.`,
|
|
28572
28572
|
[CoreMessage.BrokenEvidenceNotNamed]: "(evidence not named by the runner)",
|
|
28573
28573
|
[CoreMessage.BrokenEvidenceWhatBroke]: (locator) => `${locator} \u2014 what broke:`,
|
|
@@ -28616,9 +28616,9 @@ var init_messages4 = __esm({
|
|
|
28616
28616
|
[CoreMessage.NothingToReconcileGloss]: (corpusDir) => `there were no accounts to agree. The ledger carries no Claim Reconciliation at all, so this run has NO BASIS FOR A VERDICT \u2014 the corpus \`${corpusDir}\` carried no scenario and nothing was produced. Not balanced: a run that examined nothing must not certify.`,
|
|
28617
28617
|
[CoreMessage.PendingItemsOutstanding]: "Pending Items are outstanding \u2014 deferred, not out-of-balance, so the verdict stands. A run that treats a deferral as a failure gives exit 3 under `--strict`.",
|
|
28618
28618
|
[CoreMessage.EvidenceReconciliationHeading]: "### Evidence reconciliation",
|
|
28619
|
-
[CoreMessage.EvidenceReconciliationClaimReconciliationTerm]: "A Claim Reconciliation is one row of the ledger: one claim, reconciled in its Quality Check Reconciliations. A claim is a scenario, a phantom claim (a code that evidence cites and no scenario carries, which the table below calls an unknown Scenario) or the unnamed claim (the one row for the evidence that no scenario or phantom claim takes).",
|
|
28620
|
-
[CoreMessage.EvidenceReconciliationReconciliationLineTerm]: "A Reconciliation line is one line of a Quality Check Reconciliation, with its own outcome: each Evidence Observation it holds is one line, its Evidence Obligation is one more when no Evidence Observation that ran answers it, and one holding neither is a single line. No line stands in for another: a scenario whose one Evidence Obligation two passing tests answer adds one to the Claim Reconciliation total and two to the Reconciliation line total.",
|
|
28621
|
-
[CoreMessage.EvidenceReconciliationEvidenceObligationTerm]: "An Evidence Obligation is
|
|
28619
|
+
[CoreMessage.EvidenceReconciliationClaimReconciliationTerm]: "A Claim Reconciliation is one row of the ledger: one claim, reconciled in its Quality Check Reconciliations. A Quality Check Reconciliation reconciles the evidence of one kind of quality check within the claim: the claim's Evidence Obligation of that kind, when it has one, against its Evidence Observations of that kind. A claim is a scenario, a phantom claim (a code that evidence cites and no scenario carries, which the table below calls an unknown Scenario) or the unnamed claim (the one row for the evidence that no scenario or phantom claim takes).",
|
|
28620
|
+
[CoreMessage.EvidenceReconciliationReconciliationLineTerm]: "A Reconciliation line is one line of a Quality Check Reconciliation, with its own outcome: each Evidence Observation it holds is one line, and its Evidence Obligation is one more when no Evidence Observation that ran answers it. A scenario with no Evidence Obligation, no Pending Item and no Evidence Observation still has one Quality Check Reconciliation, holding neither, and it is a single line. No line stands in for another: a scenario whose one Evidence Obligation two passing tests answer adds one to the Claim Reconciliation total and two to the Reconciliation line total.",
|
|
28621
|
+
[CoreMessage.EvidenceReconciliationEvidenceObligationTerm]: "An Evidence Obligation is the evidence a scenario asks for, by the tags it carries, to be met by Evidence Observations. A pending tag such as `@unitpending` defers the evidence of its kind of quality check, and a deferral tag such as `@wip` defers all of the scenario's: what a tag defers raises no Evidence Obligation and is a Pending Item instead, tallied after the table, apart from balanced and out-of-balance, when there is one.",
|
|
28622
28622
|
[CoreMessage.EvidenceReconciliationEvidenceObservationTerm]: "An Evidence Observation is one reported result of a test or a fitness function, attributed by the codes it cites: to the one scenario that carries its one code, to a phantom claim when no scenario carries its one code, and otherwise to the unnamed claim, because no one scenario can take it. One that never reached its assertions is broken: it was reported, but did not run to a result.",
|
|
28623
28623
|
[CoreMessage.SubjectColumn]: "Subject",
|
|
28624
28624
|
[CoreMessage.TotalColumn]: "Total",
|
|
@@ -28654,7 +28654,7 @@ var init_messages4 = __esm({
|
|
|
28654
28654
|
[CoreMessage.StepAccountingPlumbingLabel]: "GitHub plumbing:",
|
|
28655
28655
|
[CoreMessage.StepAccountingCandidatesTerm]: "A Candidate is a step read that is not a Runner, Reconciler, Excluded or GitHub plumbing step. It is read as a fitness function, and no list below names it.",
|
|
28656
28656
|
[CoreMessage.StepAccountingReconcilerTerm]: "A Reconciler step runs this reconciliation or writes the step record it reads.",
|
|
28657
|
-
[CoreMessage.StepAccountingExcludedTerm]: "An Excluded step is one the target names a non-check under `specController.notChecks
|
|
28657
|
+
[CoreMessage.StepAccountingExcludedTerm]: "An Excluded step is one the target names a non-check under `specController.notChecks`, unless it is a Reconciler step. A GitHub plumbing step named there is Excluded too.",
|
|
28658
28658
|
[CoreMessage.StepAccountingPlumbingTerm]: "A GitHub plumbing step is one that is neither a Reconciler nor an Excluded step and uses one of GitHub's own actions `actions/checkout`, `actions/cache`, `actions/upload-artifact`, `actions/download-artifact` or `actions/setup-*`. A step that runs a command, an install included, is never plumbing.",
|
|
28659
28659
|
[CoreMessage.StepAccountingAccountedForTerm]: "Accounted for is the sum of the five columns from Candidates to GitHub plumbing, in which each step read is counted once.",
|
|
28660
28660
|
[CoreMessage.OutOfBalanceByFeatureHeading]: "### Out-of-balance by feature",
|
|
@@ -28680,16 +28680,16 @@ var init_messages4 = __esm({
|
|
|
28680
28680
|
[CoreMessage.CiStepsColumn]: "CI steps",
|
|
28681
28681
|
[CoreMessage.EvidenceCellKey]: [
|
|
28682
28682
|
"Key: each evidence cell reads *obligation*/*observations*.",
|
|
28683
|
-
"- The letter says the scenario's tags raise an Evidence Obligation of that kind: (F)itness, (U)nit, (I)ntegration, (E)2e, (P)erformance. `-` means none
|
|
28683
|
+
"- The letter says the scenario's tags raise an Evidence Obligation of that kind: (F)itness, (U)nit, (I)ntegration, (E)2e, (P)erformance. `-` means they raise none of that kind, as a pending tag raises none.",
|
|
28684
28684
|
"- The number counts the scenario's Evidence Observations of that kind that ran. `-` means none.",
|
|
28685
|
-
"- For example, `U/2` is a unit obligation answered by two unit tests; `U/-` is a unit obligation that no unit test answered; `-/1` is one unit test citing a scenario that
|
|
28685
|
+
"- For example, `U/2` is a unit obligation answered by two unit tests; `U/-` is a unit obligation that no unit test answered; `-/1` is one unit test citing a scenario that raises no unit obligation, which puts the row out of balance even where its unit evidence is pending.",
|
|
28686
28686
|
"- A blank cell means no obligation and no Evidence Observation that ran; `\u2014` marks the row of a phantom claim or of the unnamed claim.",
|
|
28687
28687
|
"- A row named `feature file : scenario title` is a scenario that carries no @SCN code. The run reads none of its tags, so its evidence cells are blank, and its reconciling item says that no Evidence Observation can link to it.",
|
|
28688
28688
|
"- In Reconciling items, `\u2014` means the row has no reconciling item, and *untagged* means a scenario that carries an @SCN code and no tag that raises an Evidence Obligation.",
|
|
28689
|
-
"- On the unnamed claim's row, the counts after an item, such as `1 ran, 1 passed, 0 failed`, are of that item's own tests, and a fitness item counts its CI steps; a broken item stands alone
|
|
28689
|
+
"- On the unnamed claim's row, the counts after an item, such as `1 ran, 1 passed, 0 failed`, are of that item's own tests, and a fitness item counts its CI steps; a broken item stands alone, outside those counts.",
|
|
28690
28690
|
"- CI steps names the steps the Evidence observations table gives for each kind of quality check other than fitness that the row obligates or observes, whether or not an Evidence Observation of that kind ran for the row, and the step each of the row's fitness Evidence Observations names: `U/-` beside a step names the step that runs unit tests, none of which answered this row. A blank CI steps cell means no such step is known."
|
|
28691
28691
|
].join("\n"),
|
|
28692
|
-
[CoreMessage.WatermelonItemKey]: "- Where a row
|
|
28692
|
+
[CoreMessage.WatermelonItemKey]: "- Where a row's item says its CI step or its job sets `continue-on-error`, the name in parentheses after it is its fitness function. Remove `continue-on-error` from its CI step and from its job, or set it to false, and the check's red fails the CI run.",
|
|
28693
28693
|
[CoreMessage.PendingItem]: "pending",
|
|
28694
28694
|
[CoreMessage.PendingItemFor]: (qualityCheckKind) => `pending: ${qualityCheckKind}`,
|
|
28695
28695
|
[CoreMessage.CheckStepNoOutcome]: (scnId) => `${scnId}: the CI run's record carries no outcome for this check's step \u2014 so the check did not run.`,
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "spec-controller",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.204",
|
|
4
4
|
"description": "Reconcile the behaviour your scenarios name against the evidence that actually ran — the deterministic `balance` CLI.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"reconciliation",
|
|
@@ -26,7 +26,7 @@
|
|
|
26
26
|
"fast-xml-parser": "^5.11.2",
|
|
27
27
|
"ts-json-schema-generator": "^2.9.0",
|
|
28
28
|
"yaml": "^2.9.0",
|
|
29
|
-
"@3f-consulting/spec-controller-core": "0.1.
|
|
29
|
+
"@3f-consulting/spec-controller-core": "0.1.204"
|
|
30
30
|
},
|
|
31
31
|
"publishConfig": {
|
|
32
32
|
"access": "public"
|