@agent-ix/quoin 0.21.9 → 0.22.5

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.
Files changed (116) hide show
  1. package/.claude-plugin/plugin.json +1 -1
  2. package/.codex-plugin/plugin.json +1 -1
  3. package/default-modules.yaml +18 -2
  4. package/dist/{advisor-BiKhR9Yp.js → advisor-BkgwDKvQ.js} +1 -1
  5. package/dist/auditor/audit.d.ts +23 -18
  6. package/dist/auditor/audit.d.ts.map +1 -1
  7. package/dist/auditor/index.d.ts +2 -1
  8. package/dist/auditor/index.d.ts.map +1 -1
  9. package/dist/{auditor-ww0MC62a.js → auditor-C3bSmPD_.js} +82 -65
  10. package/dist/{base-W7vrLi5E.js → base-CqKNs2Kd.js} +1 -1
  11. package/dist/cli.js +1 -1
  12. package/dist/commands/advise.js +16 -15
  13. package/dist/commands/assurance.d.ts.map +1 -1
  14. package/dist/commands/assurance.js +84 -61
  15. package/dist/commands/catalog/list.js +2 -2
  16. package/dist/commands/catalog/methods.js +3 -3
  17. package/dist/commands/catalog/show.js +2 -2
  18. package/dist/commands/catalog/validate.js +2 -2
  19. package/dist/commands/completeness.js +2 -2
  20. package/dist/commands/config/doctor.d.ts.map +1 -1
  21. package/dist/commands/config/doctor.js +3 -3
  22. package/dist/commands/config/edit.d.ts.map +1 -1
  23. package/dist/commands/config/edit.js +3 -3
  24. package/dist/commands/config/get.js +1 -1
  25. package/dist/commands/config/set.js +1 -1
  26. package/dist/commands/evidence/affirm.js +6 -5
  27. package/dist/commands/evidence/audit.d.ts.map +1 -1
  28. package/dist/commands/evidence/audit.js +57 -45
  29. package/dist/commands/evidence/baseline.d.ts.map +1 -1
  30. package/dist/commands/evidence/baseline.js +52 -42
  31. package/dist/commands/evidence/gc.js +3 -2
  32. package/dist/commands/evidence/index.js +1 -1
  33. package/dist/commands/evidence/inspect-mocks.d.ts +16 -0
  34. package/dist/commands/evidence/inspect-mocks.d.ts.map +1 -0
  35. package/dist/commands/evidence/inspect-mocks.js +49 -0
  36. package/dist/commands/evidence/record.d.ts +1 -0
  37. package/dist/commands/evidence/record.d.ts.map +1 -1
  38. package/dist/commands/evidence/record.js +42 -31
  39. package/dist/commands/matrix.js +1 -1
  40. package/dist/commands/measurement/index.d.ts +7 -0
  41. package/dist/commands/measurement/index.d.ts.map +1 -0
  42. package/dist/commands/measurement/index.js +11 -0
  43. package/dist/commands/measurement/record.d.ts +10 -0
  44. package/dist/commands/measurement/record.d.ts.map +1 -0
  45. package/dist/commands/measurement/record.js +35 -0
  46. package/dist/commands/module/ensure-defaults.js +3 -3
  47. package/dist/commands/module/install.js +2 -2
  48. package/dist/commands/module/list.js +2 -2
  49. package/dist/commands/module/remove.js +2 -2
  50. package/dist/commands/report.d.ts +15 -0
  51. package/dist/commands/report.d.ts.map +1 -0
  52. package/dist/commands/report.js +70 -0
  53. package/dist/commands/review.js +1 -1
  54. package/dist/commands/to-plan.js +1 -1
  55. package/dist/commands/update.js +2 -2
  56. package/dist/commands/validate.d.ts +13 -0
  57. package/dist/commands/validate.d.ts.map +1 -0
  58. package/dist/commands/validate.js +123 -0
  59. package/dist/commands/write.js +3 -3
  60. package/dist/{completeness-BQDxME0a.js → completeness-DamWradt.js} +1 -1
  61. package/dist/evidence/index.d.ts +3 -2
  62. package/dist/evidence/index.d.ts.map +1 -1
  63. package/dist/evidence/mock-inspection.d.ts +16 -0
  64. package/dist/evidence/mock-inspection.d.ts.map +1 -0
  65. package/dist/evidence/store.d.ts +11 -1
  66. package/dist/evidence/store.d.ts.map +1 -1
  67. package/dist/evidence/types.d.ts +31 -0
  68. package/dist/evidence/types.d.ts.map +1 -1
  69. package/dist/{evidence-BA5vyZJk.js → evidence-DD0CHzJ0.js} +246 -316
  70. package/dist/{flow-command-C_dUJNm-.js → flow-command-BfFNY0Rv.js} +1 -1
  71. package/dist/index.d.ts +1 -0
  72. package/dist/index.d.ts.map +1 -1
  73. package/dist/index.js +9 -8
  74. package/dist/measurement/compare.d.ts +4 -0
  75. package/dist/measurement/compare.d.ts.map +1 -0
  76. package/dist/measurement/index.d.ts +9 -0
  77. package/dist/measurement/index.d.ts.map +1 -0
  78. package/dist/measurement/plans.d.ts +4 -0
  79. package/dist/measurement/plans.d.ts.map +1 -0
  80. package/dist/measurement/portfolio.d.ts +48 -0
  81. package/dist/measurement/portfolio.d.ts.map +1 -0
  82. package/dist/measurement/profiles.d.ts +9 -0
  83. package/dist/measurement/profiles.d.ts.map +1 -0
  84. package/dist/measurement/report.d.ts +44 -0
  85. package/dist/measurement/report.d.ts.map +1 -0
  86. package/dist/measurement/store.d.ts +7 -0
  87. package/dist/measurement/store.d.ts.map +1 -0
  88. package/dist/measurement/types.d.ts +83 -0
  89. package/dist/measurement/types.d.ts.map +1 -0
  90. package/dist/measurement/validate.d.ts +9 -0
  91. package/dist/measurement/validate.d.ts.map +1 -0
  92. package/dist/measurement-CzB74Q07.js +595 -0
  93. package/dist/{modules-Cn9Htfp0.js → modules-ez9httBA.js} +2 -2
  94. package/dist/{plugins-Byi1bWLD.js → plugins-C-ta0llj.js} +1 -1
  95. package/dist/quire/contract.d.ts +11 -12
  96. package/dist/quire/contract.d.ts.map +1 -1
  97. package/dist/quire/exec.d.ts +10 -0
  98. package/dist/quire/exec.d.ts.map +1 -1
  99. package/dist/quire/index.d.ts +2 -2
  100. package/dist/quire/index.d.ts.map +1 -1
  101. package/dist/quire/types.d.ts +119 -1
  102. package/dist/quire/types.d.ts.map +1 -1
  103. package/dist/{quire-UzoK3Azf.js → quire-D8tCpgyA.js} +526 -499
  104. package/dist/schemas/coverage-v1.schema.json +919 -105
  105. package/dist/schemas/properties-v1.schema.json +25 -0
  106. package/dist/store--2sAv12X.js +219 -0
  107. package/dist/validators/gates.d.ts +18 -0
  108. package/dist/validators/gates.d.ts.map +1 -0
  109. package/dist/validators/index.d.ts +2 -0
  110. package/dist/validators/index.d.ts.map +1 -0
  111. package/dist/{version-BMXhyIie.js → version-Dg0e6CZU.js} +1 -1
  112. package/dist/{write-BDxILTLC.js → write-DElwS9xc.js} +1 -1
  113. package/package.json +22 -16
  114. package/skills/assurance-status-report/SKILL.md +135 -0
  115. package/skills/assurance-status-report/references/report-contract.md +110 -0
  116. package/skills/spec-architecture-evaluation/SKILL.md +30 -0
@@ -10,9 +10,34 @@
10
10
  "documents": {
11
11
  "type": "array",
12
12
  "items": { "$ref": "#/$defs/Document" }
13
+ },
14
+ "engine": {
15
+ "$ref": "#/$defs/EngineProvenance"
13
16
  }
14
17
  },
15
18
  "$defs": {
19
+ "EngineProvenance": {
20
+ "type": "object",
21
+ "additionalProperties": false,
22
+ "required": ["cli", "engine", "capabilities"],
23
+ "description": "Which instrument produced this payload (agent-ix/quire-cli#68, CR-104). Identical in shape and meaning to the definition in `coverage-v1.schema.json`; both are hand-authored per FR-055-CON-1, so the duplication is two artifacts stating one contract rather than one deriving from the other. NOT the contract version — that stays in the `$id` and the filename (FR-055-CON-2). This is provenance of the MEASUREMENT.",
24
+ "properties": {
25
+ "cli": {
26
+ "type": "string",
27
+ "description": "The `quire-cli` crate version."
28
+ },
29
+ "engine": {
30
+ "type": "string",
31
+ "description": "The resolved `quire-rs` version actually linked, read from the `?tag=` / `?rev=` / `?branch=` locator of the consuming crate's lockfile entry, or the commit sha where the locator is absent — not that entry's `version` field, which for a git dependency is the dependency's own stale manifest constant. A `-<n>-g<sha>` suffix, a bare rev, or a branch name is carried VERBATIM and never rounded to the nearest tag."
32
+ },
33
+ "capabilities": {
34
+ "type": "array",
35
+ "uniqueItems": true,
36
+ "description": "What this build can emit, as tokens. Deliberately open, and deliberately not version arithmetic.",
37
+ "items": { "type": "string" }
38
+ }
39
+ }
40
+ },
16
41
  "Document": {
17
42
  "type": "object",
18
43
  "additionalProperties": false,
@@ -0,0 +1,219 @@
1
+ import { existsSync as e, mkdirSync as t, readFileSync as n, readdirSync as r, rmSync as i, writeFileSync as a } from "node:fs";
2
+ import { dirname as o, join as s } from "node:path";
3
+ //#region src/evidence/types.ts
4
+ var c = "runs", l = "scans", u = "mock-inspections", d = "mutation-score";
5
+ //#endregion
6
+ //#region src/evidence/store.ts
7
+ function f(e) {
8
+ return s(e, "spec", "evidence");
9
+ }
10
+ function p(e) {
11
+ return s(f(e), "bindings.json");
12
+ }
13
+ function m(e) {
14
+ return s(f(e), "baseline.json");
15
+ }
16
+ function h(e, t, n) {
17
+ return s(f(e), c, t, `${v(n)}.json`);
18
+ }
19
+ function g(e, t, n) {
20
+ return s(f(e), l, t, `${v(n)}.json`);
21
+ }
22
+ function _(e, t, n) {
23
+ return s(f(e), u, t, `${v(n)}.json`);
24
+ }
25
+ function v(e) {
26
+ return e.slice(0, 12);
27
+ }
28
+ function y(e) {
29
+ return `${JSON.stringify(b(e), null, 2)}\n`;
30
+ }
31
+ function b(e) {
32
+ if (Array.isArray(e)) return e.map(b);
33
+ if (typeof e != "object" || !e) return e;
34
+ let t = {};
35
+ for (let n of Object.keys(e).sort()) t[n] = b(e[n]);
36
+ return t;
37
+ }
38
+ function x(e, n) {
39
+ t(o(e), { recursive: !0 }), a(e, y(n), "utf8");
40
+ }
41
+ var S = class extends Error {
42
+ path;
43
+ cause;
44
+ constructor(e, t) {
45
+ let n = t instanceof Error ? t.message : String(t);
46
+ super(`${e} exists but is not readable JSON: ${n}. A merge conflict in a checked-in store file is the usual cause — resolve it, or delete the file to start from an empty store.`), this.path = e, this.cause = t, this.name = "StoreReadError";
47
+ }
48
+ };
49
+ function C(t) {
50
+ if (!e(t)) return null;
51
+ try {
52
+ return JSON.parse(n(t, "utf8"));
53
+ } catch (e) {
54
+ throw new S(t, e);
55
+ }
56
+ }
57
+ function w(e, t) {
58
+ try {
59
+ return C(e);
60
+ } catch (n) {
61
+ if (n instanceof S) return t.push(e), null;
62
+ throw n;
63
+ }
64
+ }
65
+ function T(e, t) {
66
+ let n = h(e, t.suite, t.commit);
67
+ return x(n, {
68
+ ...t,
69
+ schemaVersion: 1
70
+ }), n;
71
+ }
72
+ function E(e, t) {
73
+ let n = g(e, t.suite, t.commit);
74
+ return x(n, {
75
+ ...t,
76
+ schemaVersion: 1
77
+ }), n;
78
+ }
79
+ function D(e, t) {
80
+ let n = _(e, t.suite, t.commit);
81
+ return x(n, {
82
+ ...t,
83
+ schemaVersion: 1
84
+ }), n;
85
+ }
86
+ function O(e, t, n) {
87
+ return C(_(e, t, n));
88
+ }
89
+ function k(t, n) {
90
+ let i = s(f(t), l, n);
91
+ return e(i) ? r(i).filter((e) => e.endsWith(".json")).sort() : [];
92
+ }
93
+ function A(e, t, n = []) {
94
+ return k(e, t).map((r) => w(g(e, t, r.replace(/\.json$/, "")), n)).filter((e) => e !== null).sort((e, t) => R(e.timestamp, t.timestamp) || R(e.commit, t.commit));
95
+ }
96
+ function j(e, t, n = []) {
97
+ return A(e, t, n).at(-1) ?? null;
98
+ }
99
+ function M(e) {
100
+ return e.rulesEvaluated === void 0 ? null : e.rulesEvaluated === 0;
101
+ }
102
+ function N(t, n) {
103
+ let i = s(f(t), c, n);
104
+ return e(i) ? r(i).filter((e) => e.endsWith(".json")).sort() : [];
105
+ }
106
+ function P(e, t, n = []) {
107
+ return N(e, t).map((r) => w(h(e, t, r.replace(/\.json$/, "")), n)).filter((e) => e !== null).sort((e, t) => R(e.timestamp, t.timestamp) || R(e.commit, t.commit));
108
+ }
109
+ function F(e, t, n = []) {
110
+ return P(e, t, n).at(-1) ?? null;
111
+ }
112
+ function I(e) {
113
+ return z(e).map((t) => F(e, t)).filter((e) => e !== null);
114
+ }
115
+ function L(e) {
116
+ return z(e).map((t) => j(e, t)).filter((e) => e !== null);
117
+ }
118
+ function R(e, t) {
119
+ return e === t ? 0 : e < t ? -1 : 1;
120
+ }
121
+ function z(t) {
122
+ let n = /* @__PURE__ */ new Set();
123
+ for (let i of [
124
+ c,
125
+ l,
126
+ u
127
+ ]) {
128
+ let a = s(f(t), i);
129
+ if (e(a)) for (let e of r(a, { withFileTypes: !0 })) e.isDirectory() && n.add(e.name);
130
+ }
131
+ return [...n].sort();
132
+ }
133
+ function B(e) {
134
+ return C(p(e)) ?? {
135
+ schemaVersion: 1,
136
+ bindings: []
137
+ };
138
+ }
139
+ function V(e, t) {
140
+ let n = [...t.bindings].sort(G);
141
+ x(p(e), {
142
+ schemaVersion: 1,
143
+ bindings: n
144
+ });
145
+ }
146
+ function H(e) {
147
+ return C(m(e));
148
+ }
149
+ function U(e, t) {
150
+ x(m(e), {
151
+ schemaVersion: 1,
152
+ commit: t.commit,
153
+ accepted: [...t.accepted].sort(R)
154
+ });
155
+ }
156
+ function W(e, t = !1) {
157
+ let n = new Set(B(e).bindings.map((e) => `${e.suite}/${v(e.commit)}.json`)), r = [];
158
+ for (let a of z(e)) {
159
+ let o = N(e, a), u = /* @__PURE__ */ new Set(), d = F(e, a);
160
+ d && u.add(`${v(d.commit)}.json`);
161
+ for (let l of o) {
162
+ if (u.has(l) || n.has(`${a}/${l}`)) continue;
163
+ let o = s(f(e), c, a, l);
164
+ r.push(o), t || i(o);
165
+ }
166
+ let p = k(e, a), m = /* @__PURE__ */ new Set(), h = j(e, a);
167
+ h && m.add(`${v(h.commit)}.json`);
168
+ for (let o of p) {
169
+ if (m.has(o) || n.has(`${a}/${o}`)) continue;
170
+ let c = s(f(e), l, a, o);
171
+ r.push(c), t || i(c);
172
+ }
173
+ }
174
+ return r.sort();
175
+ }
176
+ function G(e, t) {
177
+ return e.obligation === t.obligation ? e.suite === t.suite ? 0 : e.suite < t.suite ? -1 : 1 : e.obligation < t.obligation ? -1 : 1;
178
+ }
179
+ function K(e, t) {
180
+ let n = e.findIndex((e) => e.obligation === t.obligation && e.suite === t.suite);
181
+ if (n === -1) return {
182
+ bindings: [...e, { ...t }],
183
+ created: !0,
184
+ suspect: !1
185
+ };
186
+ let r = e[n], i = r.statementHashAtBinding !== t.statementHashAtBinding, a = {
187
+ ...r,
188
+ commit: t.commit,
189
+ symbols: t.symbols
190
+ }, o = [...e];
191
+ return o[n] = a, {
192
+ bindings: o,
193
+ created: !1,
194
+ suspect: i
195
+ };
196
+ }
197
+ function q(e, t, n, r, i, a, o) {
198
+ let s = e.map((e, t) => [e, t]).filter(([e]) => e.obligation === t && (!o || e.suite === o));
199
+ if (s.length === 0) return {
200
+ bindings: e,
201
+ found: !1
202
+ };
203
+ let c = [...e];
204
+ for (let [e, t] of s) c[t] = {
205
+ ...e,
206
+ statementHashAtBinding: n,
207
+ affirmations: [...e.affirmations ?? [], {
208
+ who: r,
209
+ commit: i,
210
+ note: a
211
+ }]
212
+ };
213
+ return {
214
+ bindings: c,
215
+ found: !0
216
+ };
217
+ }
218
+ //#endregion
219
+ export { V as _, W as a, E as b, j as c, H as d, B as f, U as g, f as h, y as i, L as l, M as m, m as n, F as o, O as p, K as r, I as s, q as t, z as u, D as v, d as x, T as y };
@@ -0,0 +1,18 @@
1
+ export interface EmptyGateFinding {
2
+ kind: "gate-that-gates-nothing";
3
+ obligation: string;
4
+ path: string;
5
+ line: number;
6
+ wiredBy: string;
7
+ summary: string;
8
+ subject: string;
9
+ changeTarget: string;
10
+ remedy: string;
11
+ }
12
+ /**
13
+ * Find a declared, wired shell gate that counts forbidden matches but never
14
+ * asserts the count. The three-way join is deliberate: script text alone
15
+ * cannot distinguish a gate from a report (agent-ix/quoin#224).
16
+ */
17
+ export declare function inspectEmptyGates(repo: string): EmptyGateFinding[];
18
+ //# sourceMappingURL=gates.d.ts.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"gates.d.ts","sourceRoot":"","sources":["../../src/validators/gates.ts"],"names":[],"mappings":"AAYA,MAAM,WAAW,gBAAgB;IAC/B,IAAI,EAAE,yBAAyB,CAAC;IAChC,UAAU,EAAE,MAAM,CAAC;IACnB,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,OAAO,EAAE,MAAM,CAAC;IAChB,OAAO,EAAE,MAAM,CAAC;IAChB,OAAO,EAAE,MAAM,CAAC;IAChB,YAAY,EAAE,MAAM,CAAC;IACrB,MAAM,EAAE,MAAM,CAAC;CAChB;AAED;;;;GAIG;AACH,wBAAgB,iBAAiB,CAAC,IAAI,EAAE,MAAM,GAAG,gBAAgB,EAAE,CA4ClE"}
@@ -0,0 +1,2 @@
1
+ export { inspectEmptyGates, type EmptyGateFinding } from './gates.js';
2
+ //# sourceMappingURL=index.d.ts.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/validators/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iBAAiB,EAAE,KAAK,gBAAgB,EAAE,MAAM,YAAY,CAAC"}
@@ -11,7 +11,7 @@ function a(e) {
11
11
  return e || i();
12
12
  }
13
13
  function o() {
14
- return a("0.21.9");
14
+ return a("0.22.5");
15
15
  }
16
16
  //#endregion
17
17
  export { a as n, o as t };
@@ -1,4 +1,4 @@
1
- import { i as e } from "./base-W7vrLi5E.js";
1
+ import { i as e } from "./base-CqKNs2Kd.js";
2
2
  import { n as t, r as n, t as r } from "./config-schema-Dp-vlxuR.js";
3
3
  import { ConfigService as i } from "@agent-ix/ix-cli-core";
4
4
  import { existsSync as a, readFileSync as o, statSync as s } from "node:fs";
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@agent-ix/quoin",
3
3
  "description": "Spec-driven development for Claude Code — author validated, ISO/IEC/IEEE 29148-aligned specs, then plan and build against them.",
4
- "version": "0.21.9",
4
+ "version": "0.22.5",
5
5
  "license": "AGPL-3.0-or-later",
6
6
  "type": "module",
7
7
  "files": [
@@ -36,6 +36,9 @@
36
36
  "evidence": {
37
37
  "description": "The evidence store — what actually ran, and against which statement (record, affirm, gc)."
38
38
  },
39
+ "measurement": {
40
+ "description": "Record plan-validated QA measurements as atomic producer collections."
41
+ },
39
42
  "module": {
40
43
  "description": "Install and manage user/community spec modules (list, install, remove, ensure-defaults)."
41
44
  },
@@ -76,10 +79,13 @@
76
79
  "pkg:add": "pnpm add",
77
80
  "pkg:add-dev": "pnpm add -D",
78
81
  "pkg:update": "pnpm update",
79
- "pkg:update-latest": "pnpm update --latest",
80
- "pkg:use-local": "pnpm dlx @agent-ix/js-deps use-local",
81
- "pkg:use-upstream": "pnpm dlx @agent-ix/js-deps use-upstream",
82
- "pkg:refresh-local": "pnpm dlx @agent-ix/js-deps refresh-local",
82
+ "experimental:pkg:update-latest": "pnpm update --latest",
83
+ "pkg:use-local": "pnpm dlx @agent-ix/js-deps@0.2.4 use-local",
84
+ "pkg:use-upstream": "pnpm dlx @agent-ix/js-deps@0.2.4 use-upstream",
85
+ "pkg:refresh-local": "pnpm dlx @agent-ix/js-deps@0.2.4 refresh-local",
86
+ "audit:tool-drift": "node scripts/check-tool-drift.mjs",
87
+ "test:tool-drift": "node scripts/check-tool-drift-selftest.mjs",
88
+ "test:verification-stack": "node scripts/verification-stack-selftest.mjs",
83
89
  "test-results:summary": "./node_modules/.bin/jest-results summary",
84
90
  "test-results:groups": "./node_modules/.bin/jest-results groups",
85
91
  "test-results:detail": "./node_modules/.bin/jest-results detail",
@@ -90,27 +96,27 @@
90
96
  "typecheck": "tsc --noEmit -p tsconfig.json"
91
97
  },
92
98
  "dependencies": {
93
- "@agent-ix/filament-plan-sync": ">=0.1.0",
94
- "@agent-ix/ix-cli-core": ">=0.12.0",
95
- "@agent-ix/ts-plugin-kit": ">=0.2.0",
96
- "@oclif/core": ">=4.13.3",
97
- "ajv": "^8.20.0",
98
- "yaml": "^2.9.0",
99
- "zod": ">=4.4.3"
99
+ "@agent-ix/filament-plan-sync": "0.1.0",
100
+ "@agent-ix/ix-cli-core": "0.12.0",
101
+ "@agent-ix/ts-plugin-kit": "0.2.0",
102
+ "@oclif/core": "4.13.3",
103
+ "ajv": "8.20.0",
104
+ "yaml": "2.9.0",
105
+ "zod": "4.4.3"
100
106
  },
101
107
  "devDependencies": {
102
- "@agent-ix/quire-cli": "^0.29.0",
108
+ "@agent-ix/quire-cli": "0.30.2",
103
109
  "@types/node": "26.1.2",
104
110
  "@typescript-eslint/eslint-plugin": "8.66.0",
105
111
  "@typescript-eslint/parser": "8.66.0",
106
112
  "@vitest/coverage-v8": "4.1.10",
107
- "add": "^2.0.9",
113
+ "add": "2.0.9",
108
114
  "eslint": "10.8.0",
109
115
  "eslint-plugin-prettier": "5.5.6",
110
- "fast-check": "^4.9.0",
116
+ "fast-check": "4.9.0",
111
117
  "pnpm": "11.20.0",
112
118
  "prettier": "3.9.6",
113
- "ts-node": "^10.9.2",
119
+ "ts-node": "10.9.2",
114
120
  "typescript": "6.0.3",
115
121
  "vite": "8.2.0",
116
122
  "vite-plugin-dts": "5.0.3",
@@ -0,0 +1,135 @@
1
+ ---
2
+ name: assurance-status-report
3
+ description: Produce an evidence-backed status report for a Quoin/Quire epic, phase, or assurance campaign. Use when asked for progress, percent complete, before/after metrics, completed-ticket inventory, open-work classification, or readiness for the next phase. The workflow is read-only and does not comment on, close, or modify tickets or repositories.
4
+ ---
5
+
6
+ # Assurance Status Report
7
+
8
+ Report what the retained evidence proves about a named goal. Use Quoin for
9
+ measurement meaning and history, Quire for producer provenance, git for local
10
+ state, and GitHub for current ticket and promotion state. Do not recreate their
11
+ analysis in the skill.
12
+
13
+ Read [references/report-contract.md](references/report-contract.md) before
14
+ assembling the report.
15
+
16
+ ## Boundary
17
+
18
+ This workflow is read-only. It may inspect repositories, retained evidence, and
19
+ remote ticket state. It must not run measurement producers, update baselines,
20
+ modify evidence, push branches, or create/comment/close/reopen issues or pull
21
+ requests unless the user separately authorizes that mutation.
22
+
23
+ A closed ticket is workflow state, not proof of completion. Match each claimed
24
+ result to its acceptance evidence, promoted commit, and relevant current-state
25
+ check.
26
+
27
+ ## Inputs
28
+
29
+ Establish these before collecting evidence:
30
+
31
+ - the goal, epic, phase, or campaign being reported;
32
+ - repositories and tickets in scope;
33
+ - work the user explicitly excluded;
34
+ - the baseline and current endpoint; and
35
+ - whether the user also wants an intermediate phase boundary.
36
+
37
+ If no baseline is named, use the earliest retained collection explicitly linked
38
+ by the target epic. Use the latest compatible retained collection as current.
39
+ State that selection instead of silently choosing favorable snapshots.
40
+
41
+ ## Collect exact evidence
42
+
43
+ ### Repository state
44
+
45
+ For every participating repository, record:
46
+
47
+ ```bash
48
+ git rev-parse HEAD
49
+ git status --porcelain
50
+ git remote get-url origin
51
+ ```
52
+
53
+ Resolve revisions to full 40-character SHAs. Use the canonical remote and a
54
+ versioned, read-only GitHub query to confirm current default-branch and commit
55
+ reachability, for example:
56
+
57
+ ```bash
58
+ gh api --header 'X-GitHub-Api-Version: 2022-11-28' \
59
+ repos/OWNER/REPO/commits/FULL_SHA
60
+ ```
61
+
62
+ Validate required response fields rather than assuming a successful command
63
+ returned the requested object. Record dirty, unreachable, ambiguous, or
64
+ wrong-origin state as a limitation; never normalize it to clean.
65
+
66
+ ### Tool and measurement state
67
+
68
+ Use existing machine-readable interfaces:
69
+
70
+ ```bash
71
+ quoin report --format json
72
+ quoin report --series METRIC --format json
73
+ quoin report --since FULL_BASELINE_REVISION --format json
74
+ quire provenance --json
75
+ ```
76
+
77
+ Use `quoin report` to discover active MeasurementPlans and retained values. Use
78
+ the series or comparison view for historical values; do not scrape rendered
79
+ human output when JSON exists. Confirm Quire's provenance schema, full CLI and
80
+ engine revisions, clean state, and required capabilities before attributing a
81
+ measurement to it.
82
+
83
+ Record the exact collection id, timestamp, source revision, corpus revision,
84
+ tool identity/version, configuration digest, definition version, and population
85
+ identity supporting each reported value. If the repository has a verification
86
+ stack attestation, report its lock and executable digests.
87
+
88
+ Do not regenerate evidence merely to answer a status question. A new run changes
89
+ the evidence state and requires separate authorization.
90
+
91
+ ### Ticket and promotion state
92
+
93
+ Use versioned read-only GitHub REST or GraphQL queries. For each issue capture at
94
+ least number, title, state, URL, and closed time. For each delivery pull request
95
+ capture state, base/head branches, merge time, merge commit, and URL. Confirm the
96
+ current default-branch SHA separately.
97
+
98
+ Follow relationships from the target epic and its retained implementation
99
+ comments. Do not equate “mentioned nearby” with “child.” Classify every remaining
100
+ item as blocking, non-blocking, downstream, excluded, or unknown and state the
101
+ evidence for that disposition.
102
+
103
+ ## Interpret without hiding drift
104
+
105
+ Define every project-specific term before its first use in the metrics section.
106
+ Derive definitions from the active MeasurementPlan or other versioned contract.
107
+ At minimum define any use of finding, controlled case, differential pair,
108
+ localization, L1/L2/L3, actionability, span grounding, safe refusal, Tier 1,
109
+ Tier 2, ratchet, drift mutation, comparability, or fail closed.
110
+
111
+ For every percentage, report its numerator and denominator. Express rate changes
112
+ as percentage points. Compare baseline and current numerically only when their
113
+ definition versions and population identities are compatible. If either moved,
114
+ show both values and explain the change, but mark the delta incomparable.
115
+
116
+ Keep historical metrics visible when a stronger successor exists. Explain why
117
+ the successor is more decision-relevant; do not relabel old evidence under the
118
+ new definition.
119
+
120
+ If the user asks for percent complete, use authored task weights when present.
121
+ Otherwise report the unweighted count of proven-complete in-scope tasks and say
122
+ that this is the method. Present verification and promotion gates separately so
123
+ a high task percentage cannot conceal an unverified result.
124
+
125
+ ## Report and stop
126
+
127
+ Follow the ordering in the report contract: status, definitions, metrics,
128
+ completed work, open work, drift controls, limitations, and progress judgment.
129
+ Lead with whether the named goal is complete, progressing, at risk, blocked, or
130
+ not started, but put the glossary before the first detailed metric use.
131
+
132
+ Link to the exact retained collections, issues, pull requests, and promoted
133
+ commits. Distinguish evidence observed now from historical evidence retained by
134
+ the campaign. If required evidence is missing or incompatible, say
135
+ `unknown` or `not_computed` and identify what would resolve it.
@@ -0,0 +1,110 @@
1
+ # Assurance status report contract
2
+
3
+ Use this contract for a detailed report. Short status requests may compress
4
+ sections, but they retain the same evidence and comparison rules.
5
+
6
+ ## Evidence states
7
+
8
+ - **Proven:** Direct current or retained evidence satisfies the requirement.
9
+ - **Contradicted:** Direct evidence shows the requirement is not satisfied.
10
+ - **Incomplete:** Some required evidence exists, but the full requirement is not
11
+ demonstrated.
12
+ - **Missing:** No authoritative evidence was found.
13
+ - **Incomparable:** Values exist, but their definitions or populations do not
14
+ permit a numeric delta.
15
+
16
+ Never turn incomplete, missing, or incomparable evidence into zero, green, or
17
+ complete.
18
+
19
+ ## Required order
20
+
21
+ ### 1. Executive status
22
+
23
+ Name the goal, current disposition, as-of time and timezone, current promoted
24
+ revision, scope boundary, and progress method. Distinguish completion of the
25
+ named phase from progress of the larger program.
26
+
27
+ ### 2. Definitions
28
+
29
+ Define each project-specific term before the metrics table. Definitions cite the
30
+ active versioned contract. Prefer plain language, then state the exact counting
31
+ rule where it matters.
32
+
33
+ Examples of distinctions that must remain visible:
34
+
35
+ - localization identifies the correct place; it does not prove the explanation
36
+ or remedy is correct;
37
+ - actionability-field presence does not prove guidance correctness;
38
+ - safe refusal preserves uncertainty and does not count as an exact span;
39
+ - a controlled-corpus result does not estimate ecosystem-wide precision; and
40
+ - a closed ticket does not by itself prove its acceptance criteria.
41
+
42
+ ### 3. Metric progression
43
+
44
+ Use a table with these conceptual columns:
45
+
46
+ | Metric | Baseline | Intermediate | Current | Delta | Comparability | Evidence |
47
+ | --- | --- | --- | --- | --- | --- | --- |
48
+
49
+ Every ratio displays `matched/examined` beside the percentage. Each row retains
50
+ the metric definition version and population identity, either inline or in its
51
+ evidence link. Use `—` for a deliberately absent intermediate snapshot and
52
+ `not_computed: REASON` for an unavailable value.
53
+
54
+ Do not calculate a delta when:
55
+
56
+ - the definition version changed;
57
+ - the applicable population was redefined;
58
+ - the source or corpus identity cannot be proved;
59
+ - either value is not computed; or
60
+ - a producer or required capability changed without an accepted comparison.
61
+
62
+ When the population merely grows under the same contract, report both the count
63
+ change and the rate change. A rate decline with a larger numerator can be scope
64
+ growth rather than a product regression; explain which occurred.
65
+
66
+ ### 4. Completed work
67
+
68
+ Enumerate every in-scope ticket/task with title, repository, final state, delivery
69
+ PR or commit, and the evidence that proves acceptance. Group by workstream when
70
+ the list is long. Separately enumerate promotion PRs and exact merge commits.
71
+
72
+ ### 5. Open work
73
+
74
+ Enumerate unresolved items and assign exactly one disposition:
75
+
76
+ - **blocking:** prevents the named goal;
77
+ - **non-blocking:** retained limitation that does not prevent this goal;
78
+ - **downstream:** belongs to a later goal or phase;
79
+ - **excluded:** explicitly outside the user's scope; or
80
+ - **unknown:** relationship or impact is not proven.
81
+
82
+ Do not omit open work merely because the named phase is complete.
83
+
84
+ ### 6. Drift controls
85
+
86
+ Report the guard and its proof for each relevant drift class: repository,
87
+ submodule, tool/engine, executable bytes, package resolution, toolchain, workflow
88
+ action, container, schema, configuration, corpus, metric definition, evidence
89
+ overlay, and promotion topology. Distinguish a guard observed in code from a
90
+ mutation test proving it fails before governed execution.
91
+
92
+ ### 7. Limitations and judgment
93
+
94
+ State remaining evidence limitations, then answer whether the effort is moving
95
+ toward the goal and why. Use one of:
96
+
97
+ - **complete** — every requirement is proven and no in-scope work remains;
98
+ - **on track** — incomplete, with no current blocking contradiction;
99
+ - **at risk** — progress exists, but a named unresolved risk threatens the goal;
100
+ - **blocked** — a named blocker prevents meaningful progress; or
101
+ - **not started** — no implementation evidence exists.
102
+
103
+ Close with the next decision or evidence-gathering point. Do not suggest starting
104
+ explicitly excluded work.
105
+
106
+ ## Read-only rule
107
+
108
+ Producing the report does not authorize ticket comments, issue state changes,
109
+ branch updates, evidence regeneration, baseline updates, or new external
110
+ messages. Ask separately before any such mutation.
@@ -0,0 +1,30 @@
1
+ ---
2
+ name: spec-architecture-evaluation
3
+ description: Evaluate a repository's implemented architecture against its stated boundaries, quality goals, and operating scenarios, producing an evidence-backed SpecReview. Use for architecture reviews; do not use for general test-gap or code-style review.
4
+ ---
5
+
6
+ # Architecture Evaluation
7
+
8
+ Evaluate the architecture that exists, including its specifications and code. Do not infer health from diagrams, test counts, or a single aggregate score.
9
+
10
+ ## Evaluation
11
+
12
+ 1. Establish the scope and named quality goals from the repository's architecture decisions, requirements, and current implementation.
13
+ 2. Walk representative success, failure, recovery, and change scenarios across component boundaries. Follow data, control, and ownership; record the concrete files or artifacts that establish each claim.
14
+ 3. Check whether responsibilities have one clear owner, dependencies point in the intended direction, failure and recovery cross boundaries coherently, and measurement or policy code is separated from presentation and orchestration.
15
+ 4. For each problem, state what is wrong, where it occurs, why it matters in a named scenario, and the smallest credible repair. Distinguish a demonstrated defect from a risk that still needs measurement.
16
+ 5. Prefer a small number of supported findings. Do not invent a numeric architecture score or treat an unavailable metric as zero.
17
+
18
+ ## Output contract
19
+
20
+ Write one Quire-validated `SpecReview` under `reviews/YY-MM-DD-<slug>.md` with:
21
+
22
+ - `type: SpecReview`
23
+ - `analysis: architecture-evaluation`
24
+ - an exact `scope` and `review_set`
25
+ - a substantive `## Summary`
26
+ - a `## Findings` table with the module's required columns
27
+
28
+ Each finding must name evidence in `Refs` and contain enough location and causal detail to be actionable. If no defect is demonstrated, record a low-severity “No issues found” row and summarize the scenarios actually examined.
29
+
30
+ Validate the result with the repository's real `quire validate` command. This review is advisory evidence unless the repository separately declares it as a gate.