@sdd-method/verify-cli 0.1.0
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/LICENSE +201 -0
- package/NOTICE +17 -0
- package/README.md +7 -0
- package/dist/lib/catalogue/baseline-check.js +136 -0
- package/dist/lib/catalogue/canonical-schema.yaml +3557 -0
- package/dist/lib/catalogue/cli-version.js +10 -0
- package/dist/lib/catalogue/coverage-predicates.js +603 -0
- package/dist/lib/catalogue/coverage-render.js +522 -0
- package/dist/lib/catalogue/coverage-run.js +115 -0
- package/dist/lib/catalogue/csv-reader.js +97 -0
- package/dist/lib/catalogue/csv-writer.js +96 -0
- package/dist/lib/catalogue/ddl-generator.js +233 -0
- package/dist/lib/catalogue/engine-validator.js +222 -0
- package/dist/lib/catalogue/finding-identity.js +183 -0
- package/dist/lib/catalogue/findings.js +46 -0
- package/dist/lib/catalogue/fk-validator.js +136 -0
- package/dist/lib/catalogue/gate-checks.js +338 -0
- package/dist/lib/catalogue/graph-projection.js +329 -0
- package/dist/lib/catalogue/impact-run.js +228 -0
- package/dist/lib/catalogue/manifest-loader.js +422 -0
- package/dist/lib/catalogue/relationship-semantics.js +66 -0
- package/dist/lib/catalogue/rubric-coverage-map.yaml +764 -0
- package/dist/lib/catalogue/scaffold-delta.js +261 -0
- package/dist/lib/catalogue/schema-compat.js +52 -0
- package/dist/lib/catalogue/schema-loader.js +87 -0
- package/dist/lib/catalogue/scores-coverage.js +535 -0
- package/dist/lib/catalogue/staleness-verdicts.js +345 -0
- package/dist/lib/catalogue/validate.js +176 -0
- package/dist/lib/catalogue/version.js +18 -0
- package/dist/lib/list/discover.js +100 -0
- package/dist/lib/list/format.js +84 -0
- package/dist/lib/list/index.js +16 -0
- package/dist/lib/lock-file.js +413 -0
- package/dist/lib/pack/log.js +18 -0
- package/dist/lib/pack/schema.js +121 -0
- package/dist/lib/pack/seed.js +182 -0
- package/dist/lib/pack/validate.js +49 -0
- package/dist/lib/package-version.js +25 -0
- package/dist/lib/repo-kind.js +129 -0
- package/dist/lib/scripts.js +7 -0
- package/dist/lib/validate/aggregate.js +35 -0
- package/dist/lib/validate/bundle-coherence.js +69 -0
- package/dist/lib/validate/dispatch.js +218 -0
- package/dist/lib/validate/index.js +88 -0
- package/dist/lib/validate/runner.js +85 -0
- package/dist/verbs/catalogue-verify.js +114 -0
- package/dist/verbs/list.js +45 -0
- package/dist/verbs/pack-validate.js +17 -0
- package/dist/verbs/path-option.js +25 -0
- package/dist/verbs/validate.js +22 -0
- package/dist/verify-bin.js +8 -0
- package/dist/verify-program.js +115 -0
- package/package.json +32 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/NOTICE
ADDED
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
sdd-cli
|
|
2
|
+
Copyright 2026 Tom Foster
|
|
3
|
+
|
|
4
|
+
This product includes software developed as part of the SDD method
|
|
5
|
+
distribution (https://github.com/tomfosteruk/sdd-method).
|
|
6
|
+
|
|
7
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
8
|
+
you may not use this file except in compliance with the License.
|
|
9
|
+
You may obtain a copy of the License at
|
|
10
|
+
|
|
11
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
12
|
+
|
|
13
|
+
Unless required by applicable law or agreed to in writing, software
|
|
14
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
15
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
16
|
+
See the License for the specific language governing permissions and
|
|
17
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,7 @@
|
|
|
1
|
+
# @sdd-method/verify-cli
|
|
2
|
+
|
|
3
|
+
`sdd-verify` checks an SDD repository and **cannot change it**.
|
|
4
|
+
|
|
5
|
+
Verbs: `validate`, `list`, `pack validate`, `catalogue validate` (incl. `--coverage`), `catalogue impact`, `catalogue baseline-check`, `catalogue version`.
|
|
6
|
+
|
|
7
|
+
The package contains only the code those verbs reach. Authoring and maintenance verbs — `sync`, `catalogue build`, `init`, `scaffold`, `mcp` and the rest — are not present in it, and are in `@sdd-method/sdd-cli`. Invoking one fails with exit 1.
|
|
@@ -0,0 +1,136 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* `catalogue baseline-check` — compares emitted findings against a repo's
|
|
3
|
+
* findings baseline BY IDENTITY (M-ADR 0132 §9), and reports the four outcomes
|
|
4
|
+
* a re-take needs to be reviewable: unbaselined, reworded, closed, unchanged.
|
|
5
|
+
*
|
|
6
|
+
* WHY THIS IS A COMMAND AND NOT A DISCIPLINE. The comparison was previously
|
|
7
|
+
* described in prose and performed per repo, which is why the rewording class
|
|
8
|
+
* (§9.1) went undetected twice on the same finding family: every repo
|
|
9
|
+
* implemented "is this line in the file" independently and correctly, and the
|
|
10
|
+
* defect was in the question, not the implementations.
|
|
11
|
+
*
|
|
12
|
+
* It reads findings rather than producing them, so it composes with whatever
|
|
13
|
+
* produced them and cannot disagree with a separate run of the builder:
|
|
14
|
+
*
|
|
15
|
+
* sdd-cli catalogue validate --coverage > findings.txt
|
|
16
|
+
* sdd-cli catalogue baseline-check --findings findings.txt
|
|
17
|
+
*
|
|
18
|
+
* ONLY GATE-ACTING CATEGORIES ARE COMPARED (`orphan`, `divergence` — M-ADR 0132
|
|
19
|
+
* §4.3). Filtering happens here, visibly, and the count of what was filtered is
|
|
20
|
+
* printed: a comparator that silently dropped categories would make an empty
|
|
21
|
+
* result ambiguous between "nothing gate-acting" and "nothing at all".
|
|
22
|
+
*/
|
|
23
|
+
import { readFile } from "node:fs/promises";
|
|
24
|
+
import { join } from "node:path";
|
|
25
|
+
import { compareToBaseline } from "./finding-identity.js";
|
|
26
|
+
/** The categories a baseline governs, per M-ADR 0132 §4.3. */
|
|
27
|
+
const GATE_ACTING = new Set(["orphan", "divergence"]);
|
|
28
|
+
export const DEFAULT_BASELINE_REL = join("orchestration", "catalogue-findings-baseline.txt");
|
|
29
|
+
const FINDING_LINE = /^\[finding\] (\w+)(?: \[error\])?[ (:]/;
|
|
30
|
+
/**
|
|
31
|
+
* Findings from a stream of mixed output. Non-finding lines (metrics, headers,
|
|
32
|
+
* blank lines, a baseline file's `#` provenance) are not findings and are
|
|
33
|
+
* dropped without comment; a `[finding]` line of a non-gate-acting category is
|
|
34
|
+
* dropped and COUNTED, because that number is the difference between "nothing
|
|
35
|
+
* to compare" and "nothing was comparable".
|
|
36
|
+
*/
|
|
37
|
+
export function extractGateActing(text) {
|
|
38
|
+
const lines = [];
|
|
39
|
+
let nonGateActing = 0;
|
|
40
|
+
for (const raw of text.split("\n")) {
|
|
41
|
+
const line = raw.trimEnd();
|
|
42
|
+
const m = FINDING_LINE.exec(line);
|
|
43
|
+
if (!m)
|
|
44
|
+
continue;
|
|
45
|
+
if (GATE_ACTING.has(m[1]))
|
|
46
|
+
lines.push(line);
|
|
47
|
+
else
|
|
48
|
+
nonGateActing++;
|
|
49
|
+
}
|
|
50
|
+
return { lines, nonGateActing };
|
|
51
|
+
}
|
|
52
|
+
export async function runBaselineCheck(options, write) {
|
|
53
|
+
const root = options.sddPath ?? process.cwd();
|
|
54
|
+
const baselinePath = options.baseline ?? join(root, DEFAULT_BASELINE_REL);
|
|
55
|
+
let findingsText;
|
|
56
|
+
if (options.findings !== undefined) {
|
|
57
|
+
findingsText = await readFile(options.findings, "utf-8");
|
|
58
|
+
}
|
|
59
|
+
else if (options.stdin) {
|
|
60
|
+
findingsText = await options.stdin();
|
|
61
|
+
}
|
|
62
|
+
else {
|
|
63
|
+
write("[error] baseline-check: no findings source (--findings <path>, or pipe them in)\n");
|
|
64
|
+
return { exitCode: 2 };
|
|
65
|
+
}
|
|
66
|
+
let baselineText;
|
|
67
|
+
try {
|
|
68
|
+
baselineText = await readFile(baselinePath, "utf-8");
|
|
69
|
+
}
|
|
70
|
+
catch (err) {
|
|
71
|
+
if (err.code !== "ENOENT")
|
|
72
|
+
throw err;
|
|
73
|
+
// A MISSING baseline is not an empty one. Under §9.3 the canonical zero is
|
|
74
|
+
// an empty-but-present file, precisely so that "measured, and there were
|
|
75
|
+
// none" is distinguishable from "never measured" — so this reports rather
|
|
76
|
+
// than treating every live finding as unbaselined.
|
|
77
|
+
write(`[error] baseline-check: no baseline at ${baselinePath} — a missing file is not a ` +
|
|
78
|
+
`recorded zero (M-ADR 0132 §9.3); create it empty, with its provenance header, ` +
|
|
79
|
+
`to record that findings were measured and there were none\n`);
|
|
80
|
+
return { exitCode: 2 };
|
|
81
|
+
}
|
|
82
|
+
const live = extractGateActing(findingsText);
|
|
83
|
+
const base = extractGateActing(baselineText);
|
|
84
|
+
const cmp = compareToBaseline(live.lines, base.lines);
|
|
85
|
+
write(`[metric] baseline_check: ${live.lines.length} gate-acting finding(s) against ` +
|
|
86
|
+
`${base.lines.length} baseline entr(ies) — ${cmp.unchanged} unchanged, ` +
|
|
87
|
+
`${cmp.reworded.length} reworded, ${cmp.unbaselined.length} unbaselined, ` +
|
|
88
|
+
`${cmp.stale.length} closed; ${live.nonGateActing} non-gate-acting finding(s) not compared\n`);
|
|
89
|
+
// ⚠ THE WHOLE-BASELINE-CLOSED GUARD. An all-closed result against a non-empty
|
|
90
|
+
// baseline is far more likely to mean the comparison read the WRONG STREAM than
|
|
91
|
+
// that an estate fixed everything at once, and until now it rendered as a clean
|
|
92
|
+
// green number: "0 gate-acting findings, 215 closed" reads as success and is
|
|
93
|
+
// indistinguishable from a gate comparing against nothing.
|
|
94
|
+
//
|
|
95
|
+
// Raised by an adopter estate that hit it on a 215-entry baseline: its
|
|
96
|
+
// baseline had been captured from one stream/tier and was being compared
|
|
97
|
+
// against another, so every entry reported closed and the regression gate
|
|
98
|
+
// passed unconditionally. The `--findings` default is stdin, so an empty pipe
|
|
99
|
+
// reaches here as legitimately-zero findings — the same estate had already
|
|
100
|
+
// been caught once by a bare invocation reporting 832 closed.
|
|
101
|
+
//
|
|
102
|
+
// The condition is deliberately narrow: live gate-acting findings ZERO, baseline
|
|
103
|
+
// non-empty, and EVERY entry closed. That triple cannot arise from ordinary
|
|
104
|
+
// remediation without also being worth a human look.
|
|
105
|
+
if (live.lines.length === 0 && base.lines.length > 0 && cmp.stale.length === base.lines.length) {
|
|
106
|
+
write(`[finding] divergence: baseline_check compared ZERO live gate-acting findings ` +
|
|
107
|
+
`against ${base.lines.length} baseline entr(ies) and reported ALL of them closed. ` +
|
|
108
|
+
`This is reported as a DEFECT rather than a pass: an all-closed baseline is far ` +
|
|
109
|
+
`more likely to mean the findings stream was empty or was the wrong one than that ` +
|
|
110
|
+
`every finding was fixed at once. Check that --findings received the stream the ` +
|
|
111
|
+
`baseline was CAPTURED from (note the default is stdin, so an empty pipe arrives ` +
|
|
112
|
+
`here as zero findings), and that --tier matches. Re-taking the baseline against ` +
|
|
113
|
+
`this comparison would bake the empty stream in as the new truth and destroy the ` +
|
|
114
|
+
`${base.lines.length}-entry record.\n`);
|
|
115
|
+
}
|
|
116
|
+
// Reported even at zero. While it is above zero those entries are matched on
|
|
117
|
+
// whole text and remain exposed to the rewording class; silence here would
|
|
118
|
+
// imply a protection the repo has not got.
|
|
119
|
+
write(`[metric] baseline_check.legacy_keyed: ${cmp.legacyKeyed} baseline entr(ies) carry no ` +
|
|
120
|
+
`identity and are matched on their whole line — re-take them as their emission ` +
|
|
121
|
+
`sites migrate (M-ADR 0132 §9.2)\n`);
|
|
122
|
+
for (const r of cmp.reworded) {
|
|
123
|
+
// Named, not counted only: a re-take must be able to show which line
|
|
124
|
+
// replaced which, and "N reworded" is not reviewable evidence.
|
|
125
|
+
write(`[reworded] ${r.baseline}\n[reworded] -> ${r.live}\n`);
|
|
126
|
+
}
|
|
127
|
+
for (const s of cmp.stale)
|
|
128
|
+
write(`[closed] ${s}\n`);
|
|
129
|
+
for (const u of cmp.unbaselined)
|
|
130
|
+
write(`[unbaselined] ${u}\n`);
|
|
131
|
+
// Only genuinely unbaselined findings fail. A reworded finding is the case
|
|
132
|
+
// this whole mechanism exists to stop failing, and a closed one is good news
|
|
133
|
+
// that a re-take tidies — neither is a regression.
|
|
134
|
+
return { exitCode: cmp.unbaselined.length > 0 ? 1 : 0 };
|
|
135
|
+
}
|
|
136
|
+
//# sourceMappingURL=baseline-check.js.map
|