@sdd-method/author-cli 0.2.0 → 0.3.0

package/dist/lib/catalogue/ext-id.js

@@ -12,12 +12,12 @@
 // carries (`name`), so the old→new map is a build artefact, not an authored
 // migration: `sdd-cli catalogue migration-map` emits it, and the exemption
 // loader consults it during the cut window (an authored exemption keyed by
-// a mapped old id is regenerable, NOT drift — the F30 rule at schema scale).
+// a mapped old id is regenerable, NOT drift — the regenerability rule at schema scale).
 /**
  * Normalise a declared diagram entry id to slug form. Camel humps split
- * BEFORE lowercasing (the F11a rule, matching the aggregator's resolver):
- * most SDD ids are hyphenated, and `bvfmGatewayFramework` must derive the
- * same identity the adjudicator resolves for it (`bvfm-gateway-framework`).
+ * BEFORE lowercasing (matching the aggregator's resolver):
+ * most SDD ids are hyphenated, and `posGatewayFramework` must derive the
+ * same identity the adjudicator resolves for it (`pos-gateway-framework`).
  */
 export function normaliseEntryId(entryId) {
     return entryId

package/dist/lib/catalogue/feature-grounding-aliases-loader.js

@@ -14,7 +14,7 @@
  *       AuthHandler: example-service-api
  *       web-ui: example-web-ui
  *     repo_aliases:
- *       camera-bff: global-camera-bff
+ *       stock-bff: northwind-stock-bff
  *
  * Either block is optional. Empty / missing file = no aliases (every
  * reference must resolve directly against the canonical id).

package/dist/lib/catalogue/finding-identity.js

@@ -1,6 +1,6 @@
 /**
  * Finding IDENTITY — the stable key a findings baseline is compared on, per
- * M-ADR 0132 §4.3 as amended, delivering the ruling recorded at ledger §3p.
+ * M-ADR 0132 §4.3 as amended.
  *
  * THE PROBLEM THIS EXISTS FOR, measured rather than asserted. A findings
  * baseline stores whole `[finding]` lines, so improving a message invalidates
@@ -17,7 +17,7 @@
  * files, 74 non-empty, 1,677 body lines — that works for 1,434 lines (85.5%)
  * and fails for 243 (14.5%), which embed their subject in prose:
  *
- *   [finding] orphan: repo integration-calamp resolves to no capability ...
+ *   [finding] orphan: repo integration-acme resolves to no capability ...
  *
  * One renderer template, all orphan class, spread across 62 repos. Recovering
  * identity there means teaching the comparator the renderer's message
@@ -30,7 +30,7 @@
  * baseline is reviewed by people and a side-channel nobody sees is a side
  * channel nobody maintains:
  *
- *   [finding] orphan (repo:integration-calamp): repo integration-calamp ...
+ *   [finding] orphan (repo:integration-acme): repo integration-acme ...
  *   [finding] divergence (docs/domains/asset/product/x.traceability.yaml): ...
  *
  * A finding with no declared subject renders EXACTLY as it does today. That is

package/dist/lib/catalogue/freshness.js

@@ -1,6 +1,6 @@
 /**
  * `catalogue build --check`: are the committed catalogues what the committed specs build to?
- * (M-ADR 0218 §5, bead sdm-jts.6.)
+ * (M-ADR 0218 §5.)
  *
  * Builds into a temporary directory and compares, so it writes nothing into the SDD. Only what
  * the build PRODUCES is compared: a hand-written file that happens to sit in catalogues/ (a

package/dist/lib/catalogue/manifest-loader.js

@@ -123,7 +123,7 @@ const DataPlaneSchema = z.object({
     bindings: z.array(DataPlaneBindingSchema),
     deviations: z.array(DataPlaneDeviationSchema).optional(),
 });
-// Conformance coverage (M-ADR 0191 §4.3, second overlay element — WS4). An
+// Conformance coverage (M-ADR 0191 §4.3, second overlay element). An
 // application-product asserts which of its archetype's conformance expectations
 // its own conformance suite exercises (`coverage`), and declares a rationale for
 // any expected tag it deliberately does not cover (`deviations`). The method
@@ -249,7 +249,7 @@ const ManifestSchema = z.object({
     // optional declared deviations from the archetype default, each carrying a
     // rationale so the mismatch is sanctioned variance, not silent drift.
     data_plane: DataPlaneSchema.optional(),
-    // Conformance coverage declaration (M-ADR 0191 §4.3 WS4, sdd-manifest-schema
+    // Conformance coverage declaration (M-ADR 0191 §4.3, sdd-manifest-schema
     // 1.5.0). Which archetype conformance expectations the product's suite
     // exercises, plus rationales for any it deliberately does not.
     conformance: ConformanceSchema.optional(),

package/dist/lib/catalogue/scaffold-delta.js

@@ -216,7 +216,7 @@ export async function runScaffoldDelta(session, options) {
 }
 /**
  * The delta's DEFECT classes are gate-acting (`divergence`), PROMOTED by a
- * recorded governance act after the M-ADR 0207 §4.9 pilot completed with no
+ * recorded method act after the M-ADR 0207 §4.9 pilot completed with no
  * surprise in any gated figure (2026-08-08) — the deliberate later act the
  * scores-coverage precedent reserves, performed. `scaffold-stale` stays
  * `coverage` with its staleness family: a stale anchor is a re-declare

package/dist/lib/catalogue/schema-compat.js

@@ -1,8 +1,7 @@
 /**
  * Per-schema compatibility ranges declared by this sdd-cli build.
  *
- * Per resolution of adopt-canonical-catalogue-builder.md §7.5, the three
- * sdd-method-distributed schemas version independently. The CLI declares
+ * The three sdd-method-distributed schemas version independently. The CLI declares
  * the version range it accepts for each and fails fast at read time on
  * out-of-range manifests.
  *

package/dist/lib/catalogue/screen-validation-loader.js

@@ -15,7 +15,7 @@
  *       - Divider
  *     archetype_overlays:               # per-platform overlay (ADR 0169 §4.3)
  *       web-generic:
- *         strip_prefixes: [Mdc, Mde]    # render-only: stripped when humanising labels
+ *         strip_prefixes: [Nwc, Nwe]    # render-only: stripped when humanising labels
  *         overrides:
  *           VBespokeGrid: grid
  *       swiftui:

package/dist/lib/catalogue/staleness-verdicts.js

@@ -1,5 +1,5 @@
-// Staleness VERDICTS — the second half of M-ADR 0205 §4.5's staleness scope
-// (ledger §3o): "staleness meaning corpus_ref older than the target's last
+// Staleness VERDICTS — the second half of M-ADR 0205 §4.5's staleness scope:
+// "staleness meaning corpus_ref older than the target's last
 // content change". The scores-coverage predicate computes each row's BASIS;
 // this module computes the VERDICT the basis supports. A stale score is worse
 // than a missing one, because it reads as coverage — the predicate otherwise

package/dist/lib/catalogue/traceability-loader.js

@@ -262,8 +262,7 @@ function extractContracts(raw) {
     // entries used to raise disappeared — the declarations became invisible
     // to row emission and to finding emission at once. The builder had been
     // taught the object form (contracts.ts) while its only feeder had not:
-    // the F36 shape again, one surface ahead of the pipeline that supplies
-    // it. `spicedb` was likewise never extracted, so `.zed` declarations
+    // a builder one surface ahead of the pipeline that supplies it. `spicedb` was likewise never extracted, so `.zed` declarations
     // never reached any builder even as bare strings.
     const arr = (key) => {
         const v = o[key];
@@ -282,7 +281,7 @@ function extractContracts(raw) {
     const graphql = arr("graphql");
     // `provenance` (3.5.0) MUST be extracted here or the builder that reads it
     // sees nothing — this function reconstructs the block key-by-key rather than
-    // passing the parsed object through, which is precisely the F36 shape the
+    // passing the parsed object through, which is precisely the shape the
     // comment above records. It was re-committed once during 3.5.0's own
     // implementation: the builder was taught to read provenance while this feeder
     // still dropped it, and only an end-to-end catalogue build caught it, because

package/dist/lib/conformance/index.js

@@ -19,7 +19,7 @@ const markdownProviderSignals = async (path, spec) => {
     const out = new Set();
     // `section` (ADR 0180 delta-pilot extension) scopes the scan to one heading block and accepts a plain
     // "Field" header, so a check can read ONE entity table inside a multi-table data-model doc (e.g.
-    // data-model.mermaid.md "### Collection: feature") without duplicating the field list into a bespoke
+    // data-model.mermaid.md "### Collection: orders") without duplicating the field list into a bespoke
     // surface file. With no `section` the behaviour is byte-for-byte the legacy one (whole file, strict
     // header, no `*` stripping) — existing gateway bindings are unaffected.
     const section = spec?.section;
@@ -35,7 +35,7 @@ const markdownProviderSignals = async (path, spec) => {
     for (const raw of (await readFile(path, "utf-8")).split("\n")) {
         const s = raw.trim();
         if (section && s.startsWith("#")) {
-            // strip leading #'s and any markdown code/emphasis in the title (`### Collection: ` + "`feature`")
+            // strip leading #'s and any markdown code/emphasis in the title (`### Collection: ` + "`orders`")
             inSection = s.replace(/^#+\s*/, "").replace(/[`*]/g, "").includes(section);
             inTable = false;
             continue;
@@ -61,7 +61,7 @@ const markdownProviderSignals = async (path, spec) => {
             if (!sig || sig === "—" || sig.startsWith("Computed") || sig.startsWith("MB "))
                 continue;
             sig = sig.replace(/\([^)]*\)/g, "").replace(/\[\]/g, "").trim(); // drop inline "(...)" notes + array markers
-            // Range shorthand: `datacoldTemp1..6` / `setpointTemp1..3` -> one declared name per index.
+            // Range shorthand: `sensor1..6` / `zone1..3` -> one declared name per index.
             const range = sig.match(/^(.*?)(\d+)\.\.(\d+)$/);
             if (range?.[1] !== undefined) {
                 const base = range[1];
@@ -369,7 +369,7 @@ const REGISTRY = {
 function norm(s, mode) {
     if (mode === "leaf") {
         // Match a nested/dotted declared path against a leaf code identifier: take the last dotted
-        // segment, drop array markers, then lower-nosep. `statusInfo.truStatus` ~ `truStatus`.
+        // segment, drop array markers, then lower-nosep. `order.status.code` ~ `code`.
         const leaf = s.split(".").pop() ?? s;
         return leaf.replace(/\[\]/g, "").replace(/[-_./ ]/g, "").toLowerCase();
     }
@@ -474,7 +474,28 @@ function printHuman(r, out) {
             out(`      - ${m}\n`);
     }
 }
-function printReconcile(chk, r, out) {
+/**
+ * Where the regenerated `produces` entries live: the spec's schema_dir, else the directory the binding's own
+ * declared entries already use (so a regenerated block keeps the adopter's layout), else `events`.
+ */
+async function reconcileSchemaDir(targetRepo, rc) {
+    if (rc.schema_dir)
+        return rc.schema_dir.replace(/\/+$/, "");
+    const path = isAbsolute(rc.binding) ? rc.binding : resolve(targetRepo, rc.binding);
+    try {
+        const doc = parseYaml(await readFile(path, "utf-8"));
+        for (const p of doc?.events?.produces ?? []) {
+            const s = p?.schema;
+            if (typeof s === "string" && s.includes("/"))
+                return s.slice(0, s.lastIndexOf("/"));
+        }
+    }
+    catch {
+        /* an unreadable binding falls through to the default */
+    }
+    return "events";
+}
+function printReconcile(chk, r, schemaDir, out) {
     if (!chk.reconcile || r.target !== "binding-vs-reality")
         return;
     const rc = chk.reconcile;
@@ -486,7 +507,7 @@ function printReconcile(chk, r, out) {
     out(`${rc.block.split(".")[0]}:\n`);
     out(`  produces:  # ${full.length} schemas (was ${r.declared} declared)\n`);
     for (const name of full)
-        out(`    - schema: party/events/${name}.avsc\n`);
+        out(`    - schema: ${schemaDir}/${name}.avsc\n`);
     if (r.declaredNotObserved.length) {
         out(`  # DROP (dangling — no such schema in code/contracts): ${r.declaredNotObserved.join(", ")}\n`);
     }
@@ -546,8 +567,8 @@ export async function runConformance(opts, stdout = (line) => process.stdout.wri
             printHuman(r, stdout);
             if (opts.reconcile) {
                 const chk = reconcileByline.get(r.id);
-                if (chk)
-                    printReconcile(chk, r, stdout);
+                if (chk?.reconcile)
+                    printReconcile(chk, r, await reconcileSchemaDir(opts.targetRepo, chk.reconcile), stdout);
             }
         }
         for (const id of skipped)

package/dist/lib/lock-file.js

@@ -215,7 +215,7 @@ function parseVersioned(raw) {
             // a YAML reader parses 113 of 325 entries in one real lock as MAPPINGS
             // rather than strings — silently, with no error. Quoting on write is the
             // fix; reading both forms ships first so no lock can be written that an
-            // older reader cannot parse. See method-open-items §3l.
+            // older reader cannot parse.
             const entry = stripQuotes(line.slice("      - ".length));
             const withDigest = DIGEST_ENTRY_RE.exec(entry);
             if (withDigest) {

package/dist/lib/package-version.js

@@ -83,7 +83,7 @@ export function getVerifyCliVersion() {
 }
 /**
  * The @sdd-method/maintain-cli version released WITH this sdd-cli. The managed CI workflow's
- * catalogue freshness step installs exactly this version (M-ADR 0218 §5; ruled 2026-10-15, sdm-jts.6).
+ * catalogue freshness step installs exactly this version (M-ADR 0218 §5).
  * Read the same way as the verify version, for the same reason (dist/ copy, never scripts/ live).
  */
 export function getMaintainCliVersion() {

package/dist/lib/snapshot/manifest.js

@@ -82,7 +82,7 @@ export async function readManifest(areaRoot, id) {
     }
     if (!Array.isArray(raw.members))
         problems.push("members must be a list");
-    // A hand-written revision of digits only (`50834756022`) parses as a NUMBER, and
+    // A hand-written revision of digits only (`12345678901`) parses as a NUMBER, and
     // a strict comparison with the folder's string suffix then calls an unchanged
     // member changed. Identity fields are strings, whatever YAML made of them.
     for (const m of raw.members ?? []) {

package/dist/lib/snapshot/targets.js

@@ -88,7 +88,7 @@ export function routeFinding(f, artefacts, shared = new Set()) {
     return [...targets.values()].sort((a, b) => (a.grain === b.grain ? a.artefact.localeCompare(b.artefact) : a.grain === "file" ? -1 : 1));
 }
 /**
- * Artefacts that mention a changed file by BASENAME only (`CollectorActor.java:49`) —
+ * Artefacts that mention a changed file by BASENAME only (`OrderHandler.java:49`) —
  * too ambiguous to route, too likely to matter to drop silently. Reported, not routed.
  */
 export function basenameOnly(f, artefacts, routed) {

package/dist/lib/validate/index.js

@@ -54,7 +54,7 @@ export async function runValidate(opts, stdout = (line) => process.stdout.write(
 // passed" with none were previously the same line (M-ADR 0200 §4.3). The
 // exit code is deliberately unchanged — the defect is the claim, not the
 // gating; whether an unexecutable validator should FAIL is the open design
-// question (post-3.0.0-followons.md A2), not this one.
+// question, not this one.
 function verdict(summary, selected) {
     if (summary.exitCode !== 0)
         return fail("One or more validators failed");

package/dist/lib/validate/plan.js

@@ -1,5 +1,5 @@
 /**
- * The method-managed validation job, as DATA (bead sdm-dd6.2; Dagger ruling sdm-s48, 2026-10-15).
+ * The method-managed validation job, as DATA (M-ADR 0219).
  *
  * One ordered plan per profile: every default validator, the platform's script-only checks, then the
  * advisory catalogue freshness check. Every executor renders or runs THIS: the GitHub workflow

package/dist/lib/validate/yaml-parse.js

@@ -10,7 +10,7 @@
 // with it certifies exactly the corruption a line-surgery transformer
 // produces. `yaml` v2 refuses duplicate keys (DUPLICATE_KEY) and the other
 // malformations a lenient parse glosses — e.g. a `: ` inside an unquoted
-// scalar (`path: (none — tel: URL)`), which no pattern rule catches.
+// scalar (`path: (none — see: docs)`), which no pattern rule catches.
 //
 // Scope: the YAML files git TRACKS (`*.yaml`, `*.yml`) — the repo's sources,
 // not build output or dependencies. Outside a git work tree there is no

package/dist/maintain-version.json

@@ -1,4 +1,4 @@
 {
-  "version": "0.3.0",
-  "built_against_sdd_cli": "1.44.0"
+  "version": "0.4.0",
+  "built_against_sdd_cli": "1.45.0"
 }

package/dist/verbs/plan.js

@@ -5,9 +5,9 @@ export function registerPlan(program) {
         .command("plan")
         .description("Scaffold a plan markdown file from a method-distributed template. Currently supports --pilot for pilot-kickoff plans; future subcommands may add --initiative / --migration.")
         .option("--pilot", "scaffold a pilot-kickoff plan (requires --service, --capability, --domain)", false)
-        .option("--service <name>", "service / pilot name, e.g. customer-management")
-        .option("--capability <name>", "capability under test, e.g. organization-management")
-        .option("--domain <name>", "domain the capability belongs to, e.g. party")
+        .option("--service <name>", "service / pilot name, e.g. order-service")
+        .option("--capability <name>", "capability under test, e.g. order-management")
+        .option("--domain <name>", "domain the capability belongs to, e.g. orders")
         .option("--workspace-root <path>", "SDD root (defaults to cwd)", resolvePathOption)
         .option("--output <path>", "destination file (defaults to content/product/plans/{service}-pilot-kickoff.md)")
         .option("--dry-run", "print rendered output to stdout without writing", false)

package/dist/verify-version.json

@@ -1,4 +1,4 @@
 {
-  "version": "1.3.0",
-  "built_against_sdd_cli": "1.44.0"
+  "version": "1.4.0",
+  "built_against_sdd_cli": "1.45.0"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@sdd-method/author-cli",
-  "version": "0.2.0",
-  "sddCliVersion": "1.44.0",
+  "version": "0.3.0",
+  "sddCliVersion": "1.45.0",
   "description": "Re-author one SDD's content — scaffold, plan, contracts, conformance, api-surface, snapshots, briefings, catalogue check — plus every read-only verify verb. Ships only the code those verbs reach; it cannot sync the baseline or rebuild the catalogues. Maintenance is in @sdd-method/maintain-cli, administration in @sdd-method/sdd-cli.",
   "license": "Apache-2.0",
   "type": "module",