@sdd-method/maintain-cli 0.3.0 → 0.4.0

package/dist/lib/briefing/render.js

@@ -1,6 +1,5 @@
 /**
- * Renderer for the briefing-layer templates per ADR 0148 + Phase 4 of
- * `adopt-agent-instructions-briefing-layer.md`.
+ * Renderer for the briefing-layer templates per ADR 0148.
  *
  * Templates ship via the method baseline bundle and land at
  * `<target>/orchestration/templates/briefing/...` after sync's

package/dist/lib/briefing/variables.js

@@ -1,6 +1,5 @@
 /**
- * Variable resolution for the briefing layer per ADR 0148 §4.1 + the
- * Phase 4 setup notes in `adopt-agent-instructions-briefing-layer.md`.
+ * Variable resolution for the briefing layer per ADR 0148 §4.1.
  *
  * The four variables are sourced from target-repo state:
  *

package/dist/lib/catalogue/aggregate.js

@@ -161,8 +161,7 @@ export async function runCatalogueAggregate(inputs, write) {
     // capability_service.service_id, emitting one row per resolved
     // (consuming-product, platform-capability) pair. Per-SDD builders
     // emit nothing for this catalogue; the aggregator owns it entirely.
-    // See content/plans/v0-9-0-cohort-sweep-derived-bundle.md
-    // §"Cross-SDD platform-capability-edge" + ADR 0134.
+    // See ADR 0134.
     const crossSddRows = deriveCrossSddPlatformCapability(rowsByCatalogue.get("product_platform_dependencies") ?? [], rowsByCatalogue.get("capability_service") ?? [], findings, rowsByCatalogue.get("capabilities") ?? []);
     rowsByCatalogue.set("cross_sdd_platform_capability", crossSddRows);
     // @rule aggregate-feature-integration-support
@@ -184,8 +183,8 @@ export async function runCatalogueAggregate(inputs, write) {
     // The same roots, additionally reachable by DIRECTORY BASENAME. An author who
     // writes a `platform/<name>/...` contract path is reading that name off the
     // filesystem, so it is the directory — which is routinely not the sdd_id (one
-    // estate declares `customer-platform` in a directory named
-    // `sdd-customer-platform`). Kept separate from sddRootsById on purpose: the
+    // estate declares `loyalty-platform` in a directory named
+    // `sdd-loyalty-platform`). Kept separate from sddRootsById on purpose: the
     // try-every-root pass must iterate each root ONCE, or a root reachable under two
     // names would count as two hits and report a false ambiguity.
     const sddRootAliases = new Map(sddRootsById);
@@ -714,7 +713,7 @@ export function dedupExternalSystems(rowsByCatalogue, findings) {
 // adopter-AUTHORED platform/domain ADRs untouched — a collision there is a genuine
 // error and MUST still fail the duplicate-PK check. Mirrors dedupExternalSystems.
 //
-// WHAT COUNTS AS METHOD-DISTRIBUTED (M-ADR 0208 / gov F-E): a row whose doc_path is
+// WHAT COUNTS AS METHOD-DISTRIBUTED (M-ADR 0208): a row whose doc_path is
 // BUNDLE-MANAGED in the contributing SDD's method-baseline.lock. Provenance, not
 // path prefix. The earlier test `startsWith("docs/method/adr/")` was a proxy for
 // the same property and it failed the first time two platform-roots aggregated:
@@ -1384,7 +1383,7 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
     const exts = rowsByCatalogue.get("c4_external_systems") ?? [];
     const containers = rowsByCatalogue.get("c4_containers") ?? [];
     const deps = rowsByCatalogue.get("system_external_dependency") ?? [];
-    // Camel humps split BEFORE lowercasing (F11a): most SDD ids are
+    // Camel humps split BEFORE lowercasing: most SDD ids are
     // hyphenated, and `posGatewayFramework` must be able to declare
     // `pos-gateway-framework`.
     const norm = (s) => s
@@ -1400,7 +1399,7 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
         .filter((s) => String(s["product_id"] ?? "") !== "")
         .map((s) => [String(s["product_id"]), String(s["id"])]));
     // Name index — names ambiguous across systems are excluded from matching
-    // (post-F7 duplicates are themselves a finding).
+    // (duplicate system names are themselves a finding).
     const systemsByName = new Map();
     for (const s of systems) {
         const key = compact(String(s["name"] ?? ""));
@@ -1412,7 +1411,7 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
         else
             systemsByName.set(key, [String(s["id"])]);
     }
-    // Container indexes (F11b): keys (names + slug aliases) are confident
+    // Container indexes: keys (names + slug aliases) are confident
     // only within the DECLARING SDD's own system; across the estate, only a
     // full display-name match counts, and only when it is unique — a
     // diagram-local alias like `emailService` must never bind to an
@@ -1497,7 +1496,7 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
     }
     const containerNameById = new Map(containers.map((c) => [String(c["id"]), String(c["name"] ?? "")]));
     const containerSystemById = new Map(containers.map((c) => [String(c["id"]), String(c["system_id"] ?? "")]));
-    // F12: containers follow the SAME precedence as systems — declared id
+    // Containers follow the SAME precedence as systems — declared id
     // first, corroborated by the display name; the name alone only as a
     // unique fallback. 0.73.0 inverted this (name-equality only, declared id
     // discarded) and traded two false positives for five silent true
@@ -1552,11 +1551,11 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
         }
         return null;
     };
-    // F11a/F12 corroboration: a declared-id hit converts (or binds) only when
+    // Corroboration: a declared-id hit converts (or binds) only when
     // the display name agrees with the target — diagram entry ids are
     // conventionally local, and an old mnemonic that happens to equal an
     // estate id must not convert silently. Comparison is TOKEN-level, not
-    // substring (F12): "Stockroom Service" must not corroborate `stock`
+    // substring: "Stockroom Service" must not corroborate `stock`
     // (shared prefix, different entity), while "Engine (telematics
     // processor)" must corroborate a container named "Engine" (a richer
     // label must not defeat the match) and three-letter names like "OMS"
@@ -1593,7 +1592,7 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
     const corroborates = (ext, sysId) => corroboratesLabel(String(ext["name"] ?? ""), nameBysystem.get(sysId) ?? "", sddById.get(sysId) ?? "");
     // A bracketed qualifier ("Email Service [unknown]") is the author
     // declaring uncertainty — it must never be rendered as a confident
-    // referent (F11b/F12): held, with the uncertainty as the stated reason.
+    // referent: held, with the uncertainty as the stated reason.
     const isUncertainLabel = (name) => /\[[^\]]*\]/.test(name);
     const keptExts = [];
     const dropExtIds = new Map();
@@ -1609,7 +1608,7 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
     let containerConverted = 0;
     let containerEdgesRewritten = 0;
     let systemFallbackEdges = 0;
-    // (F17) edges per candidate, split by whether the member build resolved
+    // Edges per candidate, split by whether the member build resolved
     // the Rel's non-external endpoint to a local container — the datum that
     // decides whether a container-bound candidate can convert without
     // destroying an edge.
@@ -1650,24 +1649,24 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
                 continue;
             }
             if (sys.method === "declared" && !corroborates(ext, sys.id)) {
-                // F11a: declared-id hit without name corroboration — a collision
+                // Declared-id hit without name corroboration — a collision
                 // between a diagram-local mnemonic and an estate id, not a
                 // reference. Kept external, loudly.
                 uncorroboratedKept++;
                 outcomeByExtId.set(extId, "uncorroborated hold");
                 keptExts.push(ext);
                 findings.add("convention", `c4_external_systems: "${extId}" declared_id resolves to internal system "${sys.id}" ` +
-                    `but the display name does not corroborate — kept external; align the entry id or name to convert (M-ADR 0189 §4.2 / F11a)`);
+                    `but the display name does not corroborate — kept external; align the entry id or name to convert (M-ADR 0189 §4.2)`);
                 continue;
             }
             if (isUncertainLabel(String(ext["name"] ?? ""))) {
-                // Declared uncertainty never converts (F12) — held with the
+                // Declared uncertainty never converts — held with the
                 // uncertainty as the stated reason.
                 uncertainHolds++;
                 outcomeByExtId.set(extId, "uncertain hold");
                 keptExts.push(ext);
                 findings.add("coverage", `c4_external_systems: "${extId}" resolves to internal system "${sys.id}" but the label declares uncertainty — ` +
-                    `held, not converted; resolve the uncertainty to convert (M-ADR 0189 §4.4 / F12)`);
+                    `held, not converted; resolve the uncertainty to convert (M-ADR 0189 §4.4)`);
                 continue;
             }
             // Internal reference — convert.
@@ -1692,7 +1691,7 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
                 uncorroboratedKept++;
                 findings.add("convention", `c4_external_systems: "${extId}"${declaredBy !== "" ? ` (declared by ${declaredBy})` : ""} ` +
                     `declared_id matches internal container "${containerRes.containerId}" but the display name does not corroborate — ` +
-                    `no referent asserted; align the entry id or name to bind (M-ADR 0189 §4.2 / F12)`);
+                    `no referent asserted; align the entry id or name to bind (M-ADR 0189 §4.2)`);
                 keptExts.push(ext);
                 continue;
             }
@@ -1701,7 +1700,7 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
                 // (already marked as an outcome above)
                 findings.add("coverage", `c4_external_systems: "${extId}"${declaredBy !== "" ? ` (declared by ${declaredBy})` : ""} ` +
                     `matches internal container "${containerRes.containerId}" but the label declares uncertainty — ` +
-                    `held, not asserted; resolve the uncertainty to bind (M-ADR 0189 §4.4 / F12)`);
+                    `held, not asserted; resolve the uncertainty to bind (M-ADR 0189 §4.4)`);
                 keptExts.push(ext);
                 continue;
             }
@@ -1709,17 +1708,17 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
                 ambiguousHolds++;
                 findings.add("coverage", `c4_external_systems: "${extId}"${declaredBy !== "" ? ` (declared by ${declaredBy})` : ""} ` +
                     `name-matches ${containerRes.candidates.length} internal containers [${containerRes.candidates.join(", ")}] — ` +
-                    `ambiguous tier contradiction, no referent asserted, row kept (M-ADR 0189 §4.4 / F11b)`);
+                    `ambiguous tier contradiction, no referent asserted, row kept (M-ADR 0189 §4.4)`);
             }
             else {
-                // F17: a bound candidate CONVERTS — its edges rewrite onto
+                // A bound candidate CONVERTS — its edges rewrite onto
                 // container_dependency where the from-endpoint is known. Only a
                 // candidate with unconvertible edges is kept, with the
                 // contradiction finding stating exactly what blocks it. No edge
                 // is ever destroyed to make a build quieter.
                 containerTargetByExtId.set(extId, containerRes.containerId);
                 const bucket = edgesByExtId.get(extId);
-                // F24 (F17's residue): a stuck edge whose from-SYSTEM differs from
+                // A stuck edge whose from-SYSTEM differs from
                 // the target container's owning system is a correct C4 L1 edge —
                 // it rewrites onto system_system_dependency (from-system → owning
                 // system). Only a stuck edge WITHIN the owning system truly blocks
@@ -1736,13 +1735,13 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
                 tierContradictions++;
                 findings.add("coverage", `c4_external_systems: "${extId}"${declaredBy !== "" ? ` (declared by ${declaredBy})` : ""} ` +
                     `resolves to ${containerRes.kind === "own" ? "its declarer's own" : "an"} internal container "${containerRes.containerId}" — ` +
-                    `tier contradiction, row kept: ${trulyStuck} same-system dependency edge(s) have no member-resolved from-container and would be L1 self-edges (M-ADR 0189 §4.4 / F17/F24)`);
+                    `tier contradiction, row kept: ${trulyStuck} same-system dependency edge(s) have no member-resolved from-container and would be L1 self-edges (M-ADR 0189 §4.4)`);
             }
         }
         keptExts.push(ext);
     }
     // Rewrite dependency edges whose external endpoint converted — to a
-    // system (§4.4) or, one tier down, to a container (F17).
+    // system (§4.4) or, one tier down, to a container.
     const keptDeps = [];
     const newEdges = new Map();
     const newContainerEdges = new Map();
@@ -1753,7 +1752,7 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
         if (containerTarget !== undefined) {
             const fromContainer = String(dep["from_container_id"] ?? "");
             if (fromContainer === "") {
-                // F24: no member-resolved from-container. Across systems this is a
+                // No member-resolved from-container. Across systems this is a
                 // correct C4 L1 edge — from-system → the container's owning system.
                 // Within the owning system it would be an L1 self-edge: kept, and
                 // its candidate row was kept for it.
@@ -1782,7 +1781,7 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
             }
             if (fromContainer === containerTarget) {
                 findings.add("coverage", `container_dependency: refused self-edge ${fromContainer} → ${containerTarget} ` +
-                    `(external declaration resolved to the declaring container itself; M-ADR 0189 §4.4 / F17)`);
+                    `(external declaration resolved to the declaring container itself; M-ADR 0189 §4.4)`);
                 continue;
             }
             const cid = `${fromContainer}__${containerTarget}`;
@@ -1829,13 +1828,13 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
         }
         edgesRewritten++;
     }
-    // §4.6 (WS15): exemptions vs outcomes, then the coverage predicate.
+    // §4.6: exemptions vs outcomes, then the coverage predicate.
     // An exemption on a CONVERTED candidate contradicts the adjudication —
     // reported and dropped (it would also dangle). A kept candidate with no
-    // outcome and no exemption is the silent bucket L4 lived in: reported
+    // outcome and no exemption is a silent bucket: reported
     // unverified, one finding per candidate, retired by declared identity
     // or by an asserted exemption.
-    // F15: the builder docstring — "each row retires exactly one unverified
+    // The builder docstring — "each row retires exactly one unverified
     // finding, and nothing else" — is enforced here, not assumed. A kept
     // exemption MUST retire exactly one unverified finding; one that retires
     // nothing (its candidate converted, or already has an adjudication
@@ -1857,17 +1856,17 @@ export function adjudicateExternalSystems(rowsByCatalogue, findings) {
         const containerDrop = containerDroppedByExtId.get(target);
         if (containerDrop !== undefined) {
             findings.add("convention", `external_system_exemption: "${target}" is asserted genuinely external but adjudication resolved it to ` +
-                `internal container "${containerDrop}" — contradiction; exemption dropped (M-ADR 0189 §4.6 / F17)`);
+                `internal container "${containerDrop}" — contradiction; exemption dropped (M-ADR 0189 §4.6)`);
             continue;
         }
         const outcome = outcomeByExtId.get(target);
         if (outcome !== undefined) {
             findings.add("convention", `external_system_exemption: "${target}" retires nothing — the candidate already has an adjudication ` +
-                `outcome (${outcome}); exemption dropped (M-ADR 0189 §4.6 / F15)`);
+                `outcome (${outcome}); exemption dropped (M-ADR 0189 §4.6)`);
             continue;
         }
         if (!keptExtIds.has(target)) {
-            findings.add("convention", `external_system_exemption: "${target}" names no kept external-system candidate — exemption dropped (M-ADR 0189 §4.6 / F15)`);
+            findings.add("convention", `external_system_exemption: "${target}" names no kept external-system candidate — exemption dropped (M-ADR 0189 §4.6)`);
             continue;
         }
         keptExemptions.push(ex);
@@ -2221,7 +2220,7 @@ async function fileExists(absPath) {
  *
  * ASYNC shared-stream dependencies (M-ADR 0192) — a dependency whose
  * `contract_type` is in the async set (`event`/`event-stream`/`stream`) — have
- * no single realiser service and carry an empty `target_service_id`. The F18
+ * no single realiser service and carry an empty `target_service_id`. The
  * synchronous realiser-join does not apply to them: instead they resolve via
  * the capability leg (`target_capability_id` against any `capability_service`
  * row for that capability) and emit the (consuming-product, platform-capability)
@@ -2309,7 +2308,7 @@ export function deriveCrossSddPlatformCapability(productPlatformDeps, capability
         if (consumingProductId === "")
             continue;
         // M-ADR 0192: an async shared-stream dependency has no realiser service.
-        // The F18 pair-join cannot apply — resolve via the capability leg and emit
+        // The pair-join cannot apply — resolve via the capability leg and emit
         // the (consuming-product, platform-capability) edge with an empty service.
         if (isAsyncContractType(contractType)) {
             if (targetCapabilityId === "")
@@ -2351,7 +2350,7 @@ export function deriveCrossSddPlatformCapability(productPlatformDeps, capability
             findings.add("orphan", `cross_sdd_platform_capability: ${consumingSddId}/${consumingProductId} declares target_service_id="${targetServiceId}" but no capability_service row resolves it ecosystem-wide`);
             continue;
         }
-        // F18: validate the declared PAIR, not each column alone. Both columns
+        // Validate the declared PAIR, not each column alone. Both columns
         // resolving independently while no capability_service row binds them
         // is a false pairing accepted in silence — the evidence table for the
         // pair exists and was never consulted.
@@ -2364,7 +2363,7 @@ export function deriveCrossSddPlatformCapability(productPlatformDeps, capability
                     .join(", ");
                 findings.add("divergence", `product_platform_dependencies: ${consumingSddId}/${consumingProductId} declares the pair ` +
                     `(target_capability_id="${declaredCapability}", target_service_id="${targetServiceId}") but no ` +
-                    `capability_service row binds them — the service resolves to [${actual}] (F18)`);
+                    `capability_service row binds them — the service resolves to [${actual}]`);
             }
         }
         for (const match of matches) {

package/dist/lib/catalogue/application-archetype/expectations.js

@@ -101,7 +101,7 @@ export function checkDataPlaneOverlayAtAggregation(inputs) {
                 findings,
             });
         }
-        // Conformance GATE (M-ADR 0191 §4.3 WS4): each archetype-expected tag must be
+        // Conformance GATE (M-ADR 0191 §4.3): each archetype-expected tag must be
         // declared covered OR deviated; an uncovered, undeviated tag is a
         // deviation-visible finding. Satisfied tags are silent.
         if (term.conformanceExpectations !== undefined && term.conformanceExpectations.length > 0) {

package/dist/lib/catalogue/archetype/wireframe.js

@@ -343,7 +343,7 @@ function humaniseName(name, prefixes) {
     let s = name;
     for (const p of prefixes) {
         // Strip only at a PascalCase boundary (next char uppercase) so a short prefix
-        // like "St" peels "StLayout" → "Layout" but never "Status" → "atus".
+        // like "Ui" peels "UiLayout" → "Layout" but never "Uint" → "nt".
         if (s.length > p.length && s.startsWith(p) && /[A-Z]/.test(s.charAt(p.length))) {
             s = s.slice(p.length);
             break;

package/dist/lib/catalogue/build.js

@@ -4,8 +4,7 @@
  * Per ADR 0134 §4.6, the canonical builder reads method-defined declarative
  * inputs and emits `catalogues/*.csv` matching the canonical schema.
  *
- * This is Phase 1 of the canonical-builder implementation per
- * adopt-canonical-catalogue-builder.md Step F. Phase 1 ships:
+ * The orchestrator provides:
  *   - manifest loading + schema-version compat check,
  *   - schema loading,
  *   - headers-only emission for every catalogue declared in the schema,
@@ -13,9 +12,9 @@
  *   - findings + row-count reporting.
  *
  * Per-source discoverers (domains, repos, services, capabilities, features,
- * etc.) land in subsequent phases. Until then the builder produces a valid
- * but empty `catalogues/` directory — useful as a smoke test that the
- * infrastructure works end-to-end on any SDD repo.
+ * etc.) live in `builders/`. With none of their inputs present the builder
+ * still produces a valid but empty `catalogues/` directory — useful as a
+ * smoke test that the infrastructure works end-to-end on any SDD repo.
  */
 import { checkCapabilityServicePopulation } from "./population-checks.js";
 import { basename, join, relative, resolve } from "node:path";
@@ -73,8 +72,7 @@ export async function runCatalogueBuild(inputs, write) {
     // more than one walker; each walker's own seen-set only dedupes intra-walker.
     // This union-dedupes identical rows across sources and hard-fails the build
     // on same-PK/different-payload, so the per-SDD catalogue is set-correct over
-    // its declared PK before aggregation ever sees it. See
-    // `coordination/feature-edge-cross-source-duplicate-coordination.md`.
+    // its declared PK before aggregation ever sees it.
     const dedupe = dedupeKeyedTables(schema, rowsByCatalogue, findings);
     // 3b. Population collapse, before anything is overwritten. A whole score family can
     // vanish while its catalogue keeps other rows: one estate's 71 traceability-manifest
@@ -293,7 +291,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     // is the mistake M-ADR 0191 §4.1 / the 0.92.1 membership move corrected.
     out.set("application_data_plane_bindings", buildApplicationDataPlaneBindings({ manifest, findings }));
     out.set("application_data_plane_deviations", buildApplicationDataPlaneDeviations({ manifest, findings }));
-    // Conformance coverage (M-ADR 0191 §4.3 WS4) — the product's declared coverage
+    // Conformance coverage (M-ADR 0191 §4.3) — the product's declared coverage
     // of / deviations from its archetype's conformance expectations. The
     // conformance GATE that reads these runs at aggregation tier (like the binding
     // overlay), where the reference-architecture `conformance` tags resolve.
@@ -389,8 +387,8 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     // Slug → capability-id aliases for feature-grounding path resolution.
     // The grounding walker derives a capability slug from the design dir
     // name (docs/domains/<dom>/design/<slug>/), but a capability's declared
-    // id may legitimately differ from its path slug — e.g. design/alerts-rules
-    // maps to id "alerts-rules-engine". Map each capability's spec +
+    // id may legitimately differ from its path slug — e.g. design/gift-card-rules
+    // maps to id "gift-card-rules-engine". Map each capability's spec +
     // feature-directory basename to its id so the walker resolves these
     // without forcing a directory rename. Only non-identity, non-colliding
     // slugs are aliased (first manifest wins).
@@ -412,7 +410,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     const knownServiceIds = new Set(services.map((s) => String(s["id"])));
     // C4 L1 external systems are built here (rather than at step 15b) so the
     // capability_service builder can categorise unresolved `services[].id`
-    // findings — an id naming a known external system (authzed, workos, …) is
+    // findings — an id naming a known external system (an auth provider, an identity SaaS, …) is
     // a convention finding, not an orphan. The rows are emitted at their usual
     // place in step 15b; only the computation is hoisted.
     const c4External = await buildC4ExternalSystems({
@@ -593,8 +591,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     // emit even when every grounding row collides on feature id with an
     // earlier source (`feature-tree` / `feature-spec`). Pre-0.30.2 the
     // conditional above gated feature_repo on the row emission, dropping
-    // the edges in the all-collide case. Fixed per
-    // `coordination/feature-grounding-collision-edges-coordination.md`.
+    // the edges in the all-collide case. Fixed.
     out.set("feature_repo", [
         ...(out.get("feature_repo") ?? []),
         ...grounding.featureRepoRows,
@@ -635,8 +632,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     // emit even when every capability-spec row collides on feature id with an
     // earlier source. Pre-fix the conditional above gated these edges on the
     // row emission, dropping them in the all-collide case (same two-level bug
-    // feature-grounding had pre-0.30.2). Fixed per
-    // `coordination/capability-spec-collision-edges-coordination.md`.
+    // feature-grounding had pre-0.30.2). Fixed.
     out.set("feature_repo", [
         ...(out.get("feature_repo") ?? []),
         ...capabilitySpec.featureRepoRows,
@@ -646,10 +642,9 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         ...capabilitySpec.featureServiceRows,
     ]);
     // 10b-ter. feature_service — application-product Feature Services table.
-    // WS0c (catalogue-coverage-invariants.md) found this table authored and
-    // unread: 12 SDDs carry a populated `## Feature Services` table in
-    // feature-tree.md, 155 declared rows / 385 feature×service pairs, 0
-    // emitted, because the two extractors above only ever walk
+    // A coverage audit found this table authored and unread: 12 SDDs carry a
+    // populated `## Feature Services` table in feature-tree.md, 155 declared
+    // rows / 385 feature×service pairs, 0 emitted, because the two extractors above only ever walk
     // feature-grounding.md / capability-spec paths (platform / integration
     // profiles). Runs last so knownFeatureIds reflects every prior source.
     // No `source` column exists on feature_service (schema has none), so rows
@@ -1157,8 +1152,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     // declared (repo-config depends_on) and derived (per-component sharedLibraries).
     out.set("repo_dependency", await buildRepoDependencies({ sddPath, configs: reposResult.configs, knownRepoIds: knownRepoIdsFinal, findings }));
     // 15. C4 systems + containers + components (L1 + L2 + L3). The L3 walker
-    // shipped per `coordination/c4-l3-walker-and-path-convention-coordination.md`
-    // (method governance, 2026-05-29) — forward-method authoring path reading
+    // is the forward-method authoring path reading
     // `c4-l3-*.mermaid.md` files alongside the L2 layout. The earlier Path-B
     // deferral assumed reverse-method code-walking; this walker is the
     // forward-method analogue, granularity-agnostic (per-container or
@@ -1218,7 +1212,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         externalIdByEntryId: c4External.idByEntryId,
         containerIdByEntryId,
     }));
-    // container_dependency member tier (F19): the C4-correct authoring —
+    // container_dependency member tier: the C4-correct authoring —
     // Rel(container_a, container_b) — emits its edge here; the aggregator's
     // adjudication leg merges rather than being the only source.
     out.set("container_dependency", await buildContainerDependency({
@@ -1228,7 +1222,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         containerIdByEntryId,
         externalIdByEntryId: c4External.idByEntryId,
     }));
-    // persona_container per M-ADR 0189 F26 §3 (schema 2.34.0) — the
+    // persona_container per M-ADR 0189 (schema 2.34.0) — the
     // L2-granularity companion to persona_c4system.
     out.set("persona_container", await buildPersonaContainer({
         sddPath,

package/dist/lib/catalogue/builders/application-conformance-coverage.js

@@ -1,4 +1,4 @@
-// application_conformance_coverage builder (M-ADR 0191 §4.3 overlay, WS4).
+// application_conformance_coverage builder (M-ADR 0191 §4.3 overlay).
 //
 // Emits one row per conformance tag the product declares about its archetype's
 // conformance expectations: `status=covered` (its suite exercises the tag) or

package/dist/lib/catalogue/builders/c4-components.js

@@ -4,9 +4,8 @@
 //   - docs/platform/diagrams/c4-l3-*.mermaid.md
 //   - docs/c4-l3-*.mermaid.md (per-product, application/integration SDDs)
 //
-// Mirrors c4-containers.ts at one level down. Source convention per
-// `coordination/c4-l3-walker-and-path-convention-coordination.md`
-// (method governance, 2026-05-29). The walker is granularity-agnostic — both
+// Mirrors c4-containers.ts at one level down, reading the method's
+// `c4-l3-*.mermaid.md` source convention. The walker is granularity-agnostic — both
 // per-container files (one `Container_Boundary` block per file) and
 // per-domain rollup files (multiple `Container_Boundary` blocks per file)
 // produce identical row output. Adopters pick the file shape that suits
@@ -44,8 +43,8 @@ export async function buildC4Components(inputs) {
         return [];
     // Index containers by suffix-after-system-prefix for slug-of-name matching.
     // c4_containers.id shape per c4-containers.ts:93 is `{systemId}-{slug}`.
-    // The suffix-match lets us resolve `Container_Boundary(_, "Asset Twin")`
-    // (slug = "asset-twin") to `{anything}-asset-twin`.
+    // The suffix-match lets us resolve `Container_Boundary(_, "Asset Register")`
+    // (slug = "asset-register") to `{anything}-asset-register`.
     const containerBySuffix = new Map();
     for (const row of inputs.c4ContainerRows) {
         const id = String(row["id"] ?? "");

package/dist/lib/catalogue/builders/c4-containers.js

@@ -76,7 +76,7 @@ export async function buildC4Containers(inputs) {
             }
             const collapsed = rowById.get(id);
             if (collapsed !== undefined) {
-                // F21: dedup-by-id is first-seen and was SILENT — two containers
+                // Dedup-by-id is first-seen and was SILENT — two containers
                 // sharing a display name collapse into one row, and every edge
                 // referencing either binds to the merge. When their technology
                 // strings flatly contradict, that is two different things wearing
@@ -85,7 +85,7 @@ export async function buildC4Containers(inputs) {
                     inputs.findings.add("convention", `c4_containers: two containers share the display name "${entry.name}" with contradictory ` +
                         `technologies ("${String(collapsed["technology"])}" vs "${entry.technology}") — collapsed ` +
                         `into one row "${id}" — either different referents wearing one name (rename one) ` +
-                        `or a misused technology field on a shared reference (correct it) (F21)`);
+                        `or a misused technology field on a shared reference (correct it)`);
                 }
                 continue;
             }
@@ -218,7 +218,7 @@ function slugify(s) {
         .replace(/^-+|-+$/g, "");
 }
 /**
- * F21: two technology strings flatly contradict when both are present and
+ * Two technology strings flatly contradict when both are present and
  * share no token — ".NET 6 (in Kestrel)" vs "Java" needs no NLP. Absent or
  * overlapping strings are NOT a contradiction (silence, not a guess).
  */

package/dist/lib/catalogue/builders/c4-external-systems.js

@@ -134,7 +134,7 @@ function parseExternals(content) {
 /**
  * Every C4 diagram file an SDD can carry (all L1 candidates incl.
  * domain-scoped, plus every L2), scope-tagged. Shared with
- * system-external-dependency (F11c: that builder kept a private,
+ * system-external-dependency (that builder kept a private,
  * pre-0.30.1-ordered copy MISSING the domain-scoped path — the fourth
  * divergent copy of this list, and a silent drop inside adjudication:
  * a Rel in a domain-scoped L1 was never harvested, so a converted

package/dist/lib/catalogue/builders/c4-l1-candidates.js

@@ -5,7 +5,7 @@
 // Under federation a sibling SDD typically carries a syndicated copy of the
 // platform-root's L1 at `docs/platform/diagrams/c4-l1-context.mermaid.md`
 // for cross-reference, AND may author its own L1. The sibling's own L1 must
-// outrank the syndicated copy — and, per F7/WS8, the syndicated copy must
+// outrank the syndicated copy — and the syndicated copy must
 // not source a sibling's identity AT ALL: on two measured estates roughly
 // half of all systems carried the platform's name and description because
 // the fallback fired for every sibling that authored no own L1. A sibling

package/dist/lib/catalogue/builders/capabilities.js

@@ -146,12 +146,12 @@ export async function buildCapabilities(inputs) {
         if (specRel) {
             usedSpecPaths.add(specRel);
             const specAbs = join(inputs.sddPath, specRel);
-            // F22: an emitted spec_path must exist — a dangling path silently
+            // An emitted spec_path must exist — a dangling path silently
             // produced an empty name/description while the column pointed at
             // nothing. The row still emits (the capability is declared); the
             // dangle is loud.
             if (!(await fileExists(specAbs))) {
-                inputs.findings.add("coverage", `${m.relPath}: capability "${cap.id}" declares capability_spec "${specRel}" which does not exist — name/description left empty, spec_path emitted dangling (F22)`);
+                inputs.findings.add("coverage", `${m.relPath}: capability "${cap.id}" declares capability_spec "${specRel}" which does not exist — name/description left empty, spec_path emitted dangling`);
             }
             // M-ADR 0211 §4.2 — the manifest is a declaration and its row is correct. The finding
             // fires ONLY on a CONTRADICTION between two declaration surfaces: this manifest

package/dist/lib/catalogue/builders/capability-edges.js

@@ -5,7 +5,7 @@
 // canonical schema declares capability_id and the target column as
 // required FKs — so each builder skips entries whose target doesn't
 // resolve in the known-target set passed in.
-// capability_service is the exception (F4, schema 2.29.0): its service_id
+// capability_service is the exception (schema 2.29.0): its service_id
 // FK is external, and an entry marked `owner_sdd:` declares a cross-SDD
 // reference — the edge is emitted despite not resolving locally and is
 // validated hard at aggregation against the owning sibling's rows.
@@ -40,7 +40,7 @@ export function buildCapabilityService(inputs) {
             if (!inputs.knownServiceIds.has(sid)) {
                 // Never drop silently (61 missing edges sat invisible in the field
                 // until a manual sweep). Resolution order:
-                //  - `owner_sdd:` marked (F4, schema 2.29.0) — a DECLARED cross-SDD
+                //  - `owner_sdd:` marked (schema 2.29.0) — a DECLARED cross-SDD
                 //    reference (e.g. the service moved to a sibling at a carve).
                 //    Emit the edge; the external FK logs it and aggregation
                 //    validates it hard against the sibling's rows.
@@ -174,7 +174,7 @@ export function buildCapabilityContract(inputs) {
             const contractId = resolveContractPath(path, inputs.contractIdByPath);
             if (contractId === "") {
                 // Never drop silently. This guard dropped every unresolvable entry with no
-                // trace until WS2 of the coverage-invariants work measured it: 62 of 188
+                // trace until it was measured: 62 of 188
                 // declared entries across two estates, and NOT ONE of them dangling — every
                 // one named a real artefact. So the resolution failure is the interesting
                 // fact, and the reader needs it.
@@ -236,7 +236,7 @@ function resolveContractPath(path, index) {
     const direct = index.get(cleaned);
     if (direct !== undefined)
         return direct;
-    // Suffix: last two parts (e.g. "asset/asset-twin.yaml")
+    // Suffix: last two parts (e.g. "asset/asset-register.yaml")
     const parts = cleaned.split(sep);
     if (parts.length >= 2) {
         const suffix = parts.slice(-2).join("/");

package/dist/lib/catalogue/builders/capability-spec-walker.js

@@ -6,7 +6,7 @@
  *
  *     | Feature | Implementation | Grounding Doc |
  *     |---|---|---|
- *     | `alerts-module` | `alerts` Vuex module + `src/components/alerts` | docs/.../feature-grounding.md |
+ *     | `banners-module` | `banners` store module + `src/components/banners` | docs/.../feature-grounding.md |
  *
  * Path convention (per ADR 0145 §4.3):
  *   - platform-profile: `docs/domains/<dom>/product/<capability>.md`
@@ -67,8 +67,8 @@ export async function findCapabilitySpecFiles(sddPath) {
  * Resolve the capability id from a capability spec file's absolute
  * path. Returns the filename stem (`.md` stripped).
  *
- *   docs/domains/applications/product/alerts-and-notifications.md
- *     → "alerts-and-notifications"
+ *   docs/domains/storefront/product/banners-and-toasts.md
+ *     → "banners-and-toasts"
  */
 export function capabilityIdFromSpecPath(absPath, sddPath) {
     const rel = relative(sddPath, absPath);