@sdd-method/author-cli 0.7.0 → 0.9.0

package/dist/lib/catalogue/builders/c4-entity-rollups.js

@@ -1,4 +1,4 @@
-// Phase 3 C4-to-entity roll-up walkers per ADR 0159 §4.8.
+// Phase 3 C4-to-entity roll-up walkers per M-ADR 0159 §4.8.
 // Both are pure transitive joins over already-FK-enforced inputs.
 //
 // buildC4ContainerEntity:

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

@@ -1,5 +1,5 @@
 // C4 external software systems discoverer — emits `c4_external_systems.csv`
-// rows (per ADR 0155). External systems are C4 L1 peers the ecosystem
+// rows (per M-ADR 0155). External systems are C4 L1 peers the ecosystem
 // integrates with but does not own; they are rendered `System_Ext(...)` on
 // L1/L2 diagrams (and occasionally `Container_Ext(...)` for an external
 // system's container). They are NOT c4_containers (not inside your system)
@@ -12,7 +12,7 @@
 // (schema 3.0.0, M-ADR 0203 §4.2) — so identity is the author's declared
 // assertion, the same identity the aggregator adjudicates (M-ADR 0189
 // §4.2). The same declared identity across SDDs collapses to one row at
-// aggregation (the dedup-by-PK exception to ADR 0134). Two entries whose
+// aggregation (the dedup-by-PK exception to M-ADR 0134). Two entries whose
 // DISPLAY NAMES agree but whose entry ids differ are two rows — the
 // same-entity-two-labels case made visible instead of silently merged;
 // the 2.x name-slug ids map to these via the ext-id migration map.

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

@@ -1,6 +1,6 @@
 // C4 L1 systems discoverer — emits at most one `c4_systems.csv` row.
 //
-// Per ADR 0134's federation model, each SDD emits its OWN c4_systems
+// Per M-ADR 0134's federation model, each SDD emits its OWN c4_systems
 // row when its manifest category is architectural. Categories map to
 // the c4_system_kind enum (canonical-schema.yaml):
 //   platform-root        → platform

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

@@ -2,7 +2,7 @@
 // traceability YAMLs (authoritative) plus capability spec files
 // (fallback for specs not covered by a traceability).
 //
-// Per ADR 0134 and the catalogue-builder-specification §"Inputs":
+// Per M-ADR 0134 and the catalogue-builder-specification §"Inputs":
 //   - Authoritative source: docs/domains/<domain>/product/<cap>.traceability.yaml
 //     declares capability.id (canonical), domain, capability_spec, runway.
 //   - Fallback: capability spec markdown files at

package/dist/lib/catalogue/builders/capability-domain-model.js

@@ -14,7 +14,7 @@
 // Domain model ids follow the `{domain_id}-data-model` convention from
 // the domain-models builder.
 //
-// Added in schema 2.4.0 per ADR 0142.
+// Added in schema 2.4.0 per M-ADR 0142.
 export function buildCapabilityDomainModel(inputs) {
     if (inputs.manifest.profile !== "platform-profile") {
         return [];

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

@@ -1,5 +1,5 @@
 /**
- * Walker for capability spec markdown files per ADR 0145 (schema 2.7.0).
+ * Walker for capability spec markdown files per M-ADR 0145 (schema 2.7.0).
  *
  * Reads `## Feature Grounding (code-path trace)` markdown tables of the
  * canonical shape:
@@ -8,7 +8,7 @@
  *     |---|---|---|
  *     | `banners-module` | `banners` store module + `src/components/banners` | docs/.../feature-grounding.md |
  *
- * Path convention (per ADR 0145 §4.3):
+ * Path convention (per M-ADR 0145 §4.3):
  *   - platform-profile: `docs/domains/<dom>/product/<capability>.md`
  *
  * Capability id resolves from the filename stem. Tolerant of column

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

@@ -1,5 +1,5 @@
 /**
- * Capability-spec feature extractor per ADR 0145 (schema 2.7.0).
+ * Capability-spec feature extractor per M-ADR 0145 (schema 2.7.0).
  *
  * Walks `docs/domains/<dom>/product/<capability>.md` (platform-profile),
  * parses the `## Feature Grounding (code-path trace)` markdown table,
@@ -12,7 +12,7 @@
  *   - `feature_service.csv` rows derived from class names / file
  *     basenames / route fragments in the Implementation column,
  *     resolved via `services.csv` + the optional per-SDD alias map
- *     introduced by ADR 0143.
+ *     introduced by M-ADR 0143.
  *
  * Resolution is best-effort and never breaks FK validation — only
  * confidently-resolved rows are emitted. Unresolved CAPABILITY ids emit
@@ -25,7 +25,7 @@
  * coverage finding per row plus one summary line (M-ADR 0143 §4.4 as
  * amended); it measures resolution coverage, never correctness.
  *
- * Precedence per ADR 0145 §4.7: feature-tree, feature-spec, and
+ * Precedence per M-ADR 0145 §4.7: feature-tree, feature-spec, and
  * feature-grounding rows win on id collision (they are more specific
  * sources); capability-spec rows are skipped with a divergence finding
  * when their id is already taken.
@@ -105,7 +105,7 @@ export async function buildCapabilitySpec(inputs) {
             // When the earlier source DID also emit the edge, the ids are identical
             // (`${cap}__${feature}` in every emitter) and keyed-table dedup unions
             // them — dedup rows, keep edges. feature_repo / feature_service remain
-            // this source's unique contribution (ADR 0145) as before.
+            // this source's unique contribution (M-ADR 0145) as before.
             if (seenFeatures.has(featureId)) {
                 // Same one-check-two-meanings split as feature-grounding.ts: a hit on
                 // an id seeded from an EARLIER SOURCE is the documented precedence rule

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

@@ -8,7 +8,7 @@
 //     - openapi/*.yaml → rest
 //     - proto/*.proto  → rpc
 //     - avro/*.avsc    → event
-//   - service_id and source_repo_id are nullable; per ADR 0110 the real
+//   - service_id and source_repo_id are nullable; per M-ADR 0110 the real
 //     contract sources may live in sibling contracts-* repos. The
 //     canonical builder leaves these empty by default; an OpenAPI
 //     `x-source-repo` extension is honoured as a hint when present
@@ -64,7 +64,7 @@ export async function buildContracts(inputs) {
     const idByPath = new Map();
     const seen = new Set();
     // Contract deprecation source (schema 2.22.0): BASELINE.md deprecation-
-    // runway entries per ADR 0073 §4.8 — the same source
+    // runway entries per M-ADR 0073 §4.8 — the same source
     // validate-deprecation-runway.sh enforces. Absent file = no deprecations.
     const deprecatedPaths = await readBaselineDeprecations(inputs.sddPath, inputs.findings);
     const discovered = [];
@@ -173,7 +173,7 @@ export async function buildContracts(inputs) {
 /**
  * Read deprecated contract paths from BASELINE.md at the SDD root.
  *
- * Shape per ADR 0073 §4.8 (the deprecation-runway gate's source):
+ * Shape per M-ADR 0073 §4.8 (the deprecation-runway gate's source):
  *   contracts:
  *     openapi: [ { path, status, sunset_date? }, ... ]
  *     proto:   [ ... ]

package/dist/lib/catalogue/builders/data-store-mapping.js

@@ -2,7 +2,7 @@
 // that reverse-method adopters author in
 // `docs/domains/<domain>/architecture/data-model.mermaid.md`.
 //
-// Extracted so two consumers share one parser (ADR 0164):
+// Extracted so two consumers share one parser (M-ADR 0164):
 //   - service-entity-tables.ts — emits service_entity edges from the
 //     Entity + Owning Service columns (relation=owns).
 //   - entity-persistence.ts — backfills entities.persistence_kind from the
@@ -70,7 +70,7 @@ export function collectTableLines(lines, startIdx) {
     }
     return null;
 }
-// ADR 0164: map a Data Store Mapping `Store` cell (a physical engine such as
+// M-ADR 0164: map a Data Store Mapping `Store` cell (a physical engine such as
 // "MySQL (orders-db)", "MongoDB", "DynamoDB", "Kinesis") to the canonical
 // `entities.persistence_kind` classification. This mirrors the services
 // builder's deriveLanguage (a normalised token derived from a raw cell) —

package/dist/lib/catalogue/builders/domain-models.js

@@ -21,7 +21,7 @@
 // is the declarative source) and the reverse check is silent unless the
 // paths disagree, in which case a `[finding] divergence` is emitted.
 //
-// Added in schema 2.4.0 per ADR 0142.
+// Added in schema 2.4.0 per M-ADR 0142.
 import { readdir, readFile, stat } from "node:fs/promises";
 import { join } from "node:path";
 import { extractFileEvidenceClass } from "./evidence-class.js";
@@ -83,7 +83,7 @@ export async function buildDomainModels(inputs) {
     }
     // Step 4: Emit rows sorted by id for determinism. `evidence_class` reads
     // from the model file's leading ```yaml fence (`evidence-class:`) per the
-    // documentation-reverse anchor convention (ADR 0175); absent file or
+    // documentation-reverse anchor convention (M-ADR 0175); absent file or
     // declaration → "".
     const rows = [];
     for (const [domainId, model] of declaredByDomain) {

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

@@ -1,6 +1,6 @@
 // Domain discoverer — emits `domains.csv` rows from `docs/domains/<slug>/`.
 //
-// Per ADR 0134 and catalogue-builder-specification.md:
+// Per M-ADR 0134 and catalogue-builder-specification.md:
 //   - Domains are method-defined: each subdirectory under docs/domains/
 //     is one domain, named by its slug.
 //   - method_profile reflects the SDD's profile (the domain belongs to
@@ -8,7 +8,7 @@
 //   - repo_count is computed by the build orchestrator after repositories
 //     are discovered, since this builder runs first.
 //
-// Per ADR 0136 ("App and Integration Products Do Not Belong to a Primary
+// Per M-ADR 0136 ("App and Integration Products Do Not Belong to a Primary
 // Domain"), only platform-profile SDDs own domains. Application-product
 // and integration-product SDDs may have a `docs/domains/<umbrella>/`
 // subdirectory as a structural-organisation convention (where their
@@ -27,7 +27,7 @@ import { readdir, readFile, stat } from "node:fs/promises";
 import { join } from "node:path";
 const DOMAINS_DIR_REL = join("docs", "domains");
 export async function buildDomains(inputs) {
-    // Per ADR 0136: only platform-profile SDDs own domains. Non-platform
+    // Per M-ADR 0136: only platform-profile SDDs own domains. Non-platform
     // SDDs return an empty list to avoid duplicate-PK collisions at
     // aggregation against the canonical platform-profile contribution.
     if (inputs.manifest.profile !== "platform-profile") {

package/dist/lib/catalogue/builders/entities-manifest.js

@@ -1,23 +1,23 @@
-// Forward-method walker for the entities catalogue per ADR 0159 §4.2.
+// Forward-method walker for the entities catalogue per M-ADR 0159 §4.2.
 // Reads `models[].entities[]` from `docs/platform/reference/glossary-alignment-manifest.yaml`.
 //
-// Same input file ADR 0158's entity_glossary walker reads — this walker
+// Same input file M-ADR 0158's entity_glossary walker reads — this walker
 // promotes the entity entries to first-class entity rows; entity_glossary
 // continues to emit a separate edge per (domain, entity, glossary_term).
 //
-// **Profile-gated to platform-profile only (per ADR 0159 §4.2 amendment,
+// **Profile-gated to platform-profile only (per M-ADR 0159 §4.2 amendment,
 // schema 2.13.0 patch).** The manifest is platform-owned ecosystem-wide
 // content; adopters who syndicate it to sibling application-product /
 // integration-product SDDs would otherwise see siblings re-emit the entire
 // entity registry locally with unresolved-domain PKs, then collide en masse
 // at aggregation. Profile-gating mirrors the precedent set by
-// domain-models.ts per ADR 0142 (same scope, same syndication shape).
+// domain-models.ts per M-ADR 0142 (same scope, same syndication shape).
 //
-// Behaviour (ADR 0159 acceptance):
+// Behaviour (M-ADR 0159 acceptance):
 // - For each models[] entry, derive domain_id from its `domain` field.
 //   `platform-wide` and other non-canonical hints map to empty domain_id
 //   and the entity PK uses the `_platform-wide-{slug}` sentinel prefix
-//   (per ADR 0159 §4.2 amendment, schema 2.13.0 patch). The underscore
+//   (per M-ADR 0159 §4.2 amendment, schema 2.13.0 patch). The underscore
 //   prefix is unreachable via entitySlug (slugify strips underscores), so
 //   the sentinel can't collide with any real domain id including
 //   ecosystem-named domains. A [finding] convention surfaces the choice.
@@ -37,7 +37,7 @@ const MANIFEST_REL_PATH = join("docs", "platform", "reference", "glossary-alignm
 const NON_CANONICAL_DOMAINS = new Set(["platform-wide", "", "platform_wide"]);
 const PLATFORM_WIDE_PK_PREFIX = "_platform-wide";
 export async function buildEntitiesFromManifest(inputs) {
-    // Profile gate per ADR 0159 §4.2 amendment: only platform-profile SDDs
+    // Profile gate per M-ADR 0159 §4.2 amendment: only platform-profile SDDs
     // read the manifest. Sibling profiles (application-product, integration-
     // product, support-repo, organisation) emit 0 rows even when the file is
     // present via syndication.
@@ -114,7 +114,7 @@ export async function buildEntitiesFromManifest(inputs) {
                 glossary_term: glossaryTerm,
                 notes: noteParts.join(";"),
                 // The glossary-alignment manifest's entities[] shape has no evidence
-                // slot — manifest-sourced rows stay empty (ADR 0175; schema 2.20.0).
+                // slot — manifest-sourced rows stay empty (M-ADR 0175; schema 2.20.0).
                 evidence_class: "",
                 source_sdd_id: "",
             };

package/dist/lib/catalogue/builders/entities-mermaid.js

@@ -1,8 +1,8 @@
-// Reverse-method walker for the entities catalogue per ADR 0159 §4.3.
+// Reverse-method walker for the entities catalogue per M-ADR 0159 §4.3.
 // Parses `erDiagram` blocks in `docs/domains/{domain}/architecture/data-model.mermaid.md`
 // (or whatever file domain_models.csv references for that domain).
 //
-// Prototype findings (per ADR 0159 — mermaid authoring quirks):
+// Prototype findings (per M-ADR 0159 — mermaid authoring quirks):
 // - Multi-erDiagram-per-file is the norm (asset has 7 blocks; identity has 4).
 //   Walker merges entities across all `erDiagram` fences in the file.
 // - Naming style varies within a single file: UPPER_SNAKE_CASE, PascalCase,
@@ -43,7 +43,7 @@ export async function buildEntitiesFromMermaid(inputs) {
         }
         const parsed = parseFile(text, dm, inputs.findings);
         // File-level evidence class (leading ```yaml fence's `evidence-class:`,
-        // per the documentation-reverse anchor convention / ADR 0175). Every
+        // per the documentation-reverse anchor convention / M-ADR 0175). Every
         // entity extracted from this file inherits it; absence → "".
         const fileEvidenceClass = extractFileEvidenceClass(text);
         // Within-file dedup by id is enforced inside parseFile via seen-set;
@@ -168,7 +168,7 @@ function resolveGlossaryTermBySlug(entityName, domainId, knownGlossaryIds) {
         if (id === slug || id.endsWith(`-${slug}`))
             return id;
     }
-    // ADR 0165 follow-on: the glossary builder collapses multi-word term slugs
+    // M-ADR 0165 follow-on: the glossary builder collapses multi-word term slugs
     // (BASKET_MESSAGE → "...-basketmessage"), while entitySlug
     // hyphenates ("basket-message"), so multi-word terms miss the suffix
     // match above. Reconcile boundary-insensitively (compare hyphen-stripped

package/dist/lib/catalogue/builders/entity-persistence.js

@@ -1,4 +1,4 @@
-// ADR 0164: backfill `entities.persistence_kind` from the reverse-method
+// M-ADR 0164: backfill `entities.persistence_kind` from the reverse-method
 // `## Data Store Mapping` table's `Store` column.
 //
 // persistence_kind is a reverse-only column (the services parity arc, ADR

package/dist/lib/catalogue/builders/entity-slug.js

@@ -1,5 +1,5 @@
 // Entity-aware slug helper used by the data-model-entity walkers
-// (entities-manifest, entities-mermaid, service-entity-tables) per ADR 0159 §4.6.
+// (entities-manifest, entities-mermaid, service-entity-tables) per M-ADR 0159 §4.6.
 //
 // Differs from the base `slugify` in events / capabilities / contracts: adds
 // an ALLCAPS-then-Pascal split rule so naming-style variation across
@@ -19,7 +19,7 @@
 // (`POS_TERMINAL_CONFIG`), breaking ~50% of expected service_entity
 // edges in one reference estate.
 //
-// Acronym-run rule (ADR 0164 wave-2 follow-on): the first replace requires the
+// Acronym-run rule (M-ADR 0164 wave-2 follow-on): the first replace requires the
 // leading uppercase run to be >=2 chars (`[A-Z]{2,}`). A *single* leading
 // capital before a capitalised word is NOT split off, so a PascalCase form
 // reconciles with its boundary-free UPPER_SNAKE form:
@@ -34,7 +34,7 @@
 //
 // Kept local to the entity walkers to avoid affecting events / contracts /
 // capability id generation. Promote to a shared module only if a fourth
-// walker needs it (per ADR 0159 §4.6 deferred decision).
+// walker needs it (per M-ADR 0159 §4.6 deferred decision).
 export function entitySlug(s) {
     return s
         .replace(/([A-Z]{2,})([A-Z][a-z])/g, "$1-$2")

package/dist/lib/catalogue/builders/event-catalog-walker.js

@@ -1,5 +1,5 @@
 // Walker for `docs/domains/<domain>/contracts/events/event-catalog.yaml` —
-// the reverse-method canonical source for events per ADR 0156.
+// the reverse-method canonical source for events per M-ADR 0156.
 //
 // One file per domain. Each `events[]` entry encodes the event's name,
 // publisher_service_id, transport, schema_path, version, and consumers[].
@@ -8,7 +8,7 @@
 //
 // Merges with the avsc-sourced forward path in events.ts: YAML wins on
 // name/domain/publisher/transport/consumers; avsc augments schema_path/
-// version when the YAML row leaves them null. See ADR 0156 §4 and the
+// version when the YAML row leaves them null. See M-ADR 0156 §4 and the
 // metamodel's §"Event sources" subsection for the precedence rules.
 import { readdir, readFile } from "node:fs/promises";
 import { join } from "node:path";
@@ -69,7 +69,7 @@ export async function walkEventCatalogs(inputs) {
         if (!Array.isArray(events))
             continue;
         // File-level evidence-class fallback for events that don't declare
-        // their own (ADR 0175). Both key spellings accepted.
+        // their own (M-ADR 0175). Both key spellings accepted.
         const fileEvidenceClass = String(rawObj["evidence_class"] ?? rawObj["evidence-class"] ?? "").trim();
         // Track slugs derived within this domain so we can flag duplicates.
         const slugsInDomain = new Set();
@@ -80,7 +80,7 @@ export async function walkEventCatalogs(inputs) {
             const explicitId = String(e["id"] ?? "").trim();
             const name = String(e["name"] ?? "").trim();
             // Derive id: explicit id wins when present (allows future override);
-            // otherwise slug from name, per ADR 0156: "derive `id` from `name`
+            // otherwise slug from name, per M-ADR 0156: "derive `id` from `name`
             // (slugged)". Some adopters' authoring uses
             // `name:` only (no `id:` field).
             let id;
@@ -117,7 +117,7 @@ export async function walkEventCatalogs(inputs) {
                 }
             }
             if (transport !== "" && !RECOMMENDED_TRANSPORTS.has(transport)) {
-                inputs.findings.add("convention", `docs/domains/${domain}/contracts/events/event-catalog.yaml: event ${id} transport "${transport}" outside recommended set (per ADR 0156)`);
+                inputs.findings.add("convention", `docs/domains/${domain}/contracts/events/event-catalog.yaml: event ${id} transport "${transport}" outside recommended set (per M-ADR 0156)`);
             }
             if (byId.has(id)) {
                 inputs.findings.add("divergence", `event ${id} declared in multiple event-catalog.yaml files — first-seen kept`);
@@ -158,7 +158,7 @@ function slugify(s) {
 }
 /**
  * Merge a YAML-parsed event with the equivalent avsc-derived row. YAML wins
- * on name/domain/publisher/transport per ADR 0156 §4.1; avsc augments
+ * on name/domain/publisher/transport per M-ADR 0156 §4.1; avsc augments
  * schema_path/version only when the YAML row leaves them empty.
  *
  * Returns a fresh CatalogueRow ready to write into events.csv.

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

@@ -1,6 +1,6 @@
 // service_event + capability_event edge builders.
 //
-// service_event sources (per ADR 0156):
+// service_event sources (per M-ADR 0156):
 //   - Forward-method canonical: repo-config `events.produces[].schema`
 //     (role=publishes) and `events.consumes[].schema` (role=consumes).
 //     Each schema is resolved against the contracts.avro index → event id.
@@ -12,7 +12,7 @@
 // (for code-gen / validation) that consumers commonly declare too. Only
 // the events block + event-catalog.yaml are authoritative for edges.
 //
-// capability_event sources (per ADR 0160, schema 2.14.0):
+// capability_event sources (per M-ADR 0160, schema 2.14.0):
 //   - Forward shape A — `traceability.events[{id, role}]` (legacy
 //     aspirational shape; unauthored across observed adopters, kept for
 //     compatibility). Emits with source=authored.
@@ -23,7 +23,7 @@
 //     fire `[finding] orphan`. Emits with source=authored.
 //   - Derived — `capability_service ⋈ service_event` join on service_id.
 //     Zero-authoring associative path; emits role from service_event.
-//     Per ADR 0160, the over-attribution fan-out is intrinsic to services
+//     Per M-ADR 0160, the over-attribution fan-out is intrinsic to services
 //     that own multiple primary capabilities, so a role filter has no
 //     useful effect (verified on a real corpus: 144 → 144 with primary
 //     filter). The `source=derived` column distinguishes these from
@@ -31,7 +31,7 @@
 //   - Merge by PK `{capability_id}__{event_id}__{role}`: authored wins;
 //     conflicting authored sources fire `[finding] divergence`.
 //
-// feature_event sources (per ADR 0161, schema 2.15.0):
+// feature_event sources (per M-ADR 0161, schema 2.15.0):
 //   - Derived only — `feature_service ⋈ service_event` join on service_id.
 //     Completes the capability/feature/service trio of materialised event
 //     edges. There is no authored shape; the authored signal lives at the
@@ -177,7 +177,7 @@ export function buildCapabilityEvent(inputs) {
         }
     }
     // ---- Derived: capability_service ⋈ service_event --------------------
-    // Pure associative coupling. Per ADR 0160, no role filter — Phase Pre
+    // Pure associative coupling. Per M-ADR 0160, no role filter — Phase Pre
     // verified that role=primary filtering gives no reduction in practice
     // (services that emit events legitimately own multiple primary caps).
     // Provenance distinguishes derived from authored for governance queries.
@@ -230,7 +230,7 @@ export function buildCapabilityEvent(inputs) {
     return [...authored.values(), ...derived];
 }
 export function buildFeatureEvent(inputs) {
-    // Derived-only edge per ADR 0161. Mirrors capability_event's derived path
+    // Derived-only edge per M-ADR 0161. Mirrors capability_event's derived path
     // one rung lower in the hierarchy. PK uses three components so the same
     // feature can hold both publishes + consumes rows for the same event.
     const rows = [];

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

@@ -1,5 +1,5 @@
 // Events discoverer — emits `events.csv` from two canonical sources per
-// ADR 0156 (multi-source ingestion):
+// M-ADR 0156 (multi-source ingestion):
 //
 //   Forward-method canonical: `contracts/avro/*.avsc` files (existing path).
 //     The avsc id becomes the event id; publisher_service_id reads from
@@ -15,7 +15,7 @@
 //   - Events declared only in avsc → forward-only row (existing behaviour)
 //   - Events declared only in YAML → reverse-only row (new)
 //
-// Transport: open string per ADR 0156 (no hardcoded default). When the
+// Transport: open string per M-ADR 0156 (no hardcoded default). When the
 // source is avsc-only with no `repo-config.events` declaration, transport
 // may be empty.
 import { sep } from "node:path";
@@ -70,7 +70,7 @@ export async function buildEvents(inputs) {
             transport: "",
             schema_path: specPath,
             version: String(c["version"] ?? ""),
-            // avsc has no evidence slot — avsc-only events stay empty (ADR 0175).
+            // avsc has no evidence slot — avsc-only events stay empty (M-ADR 0175).
             evidence_class: "",
             source_sdd_id: "",
         });

package/dist/lib/catalogue/builders/evidence-class.js

@@ -1,5 +1,5 @@
 // File-level evidence-class extraction for data-model markdown, per the
-// documentation-reverse anchor convention (ADR 0175 / sdd-method
+// documentation-reverse anchor convention (M-ADR 0175 / sdd-method
 // `docs/method/methods/reverse/documentation-reverse-anchor-schema.md`).
 //
 // Documentation-reversed data models open with a fenced ```yaml block near

package/dist/lib/catalogue/builders/feature-domain-model.js

@@ -11,7 +11,7 @@
 // model, both pairs are emitted. If multiple capabilities link to the
 // SAME domain model, the duplicate is silently dropped.
 //
-// Added in schema 2.4.0 per ADR 0142.
+// Added in schema 2.4.0 per M-ADR 0142.
 export function buildFeatureDomainModel(inputs) {
     if (inputs.manifest.profile !== "platform-profile") {
         return [];

package/dist/lib/catalogue/builders/feature-grounding-walker.js

@@ -1,5 +1,5 @@
 /**
- * Walker for `feature-grounding.md` files per ADR 0143 (schema 2.5.0).
+ * Walker for `feature-grounding.md` files per M-ADR 0143 (schema 2.5.0).
  *
  * Reads markdown tables of the canonical shape:
  *
@@ -7,7 +7,7 @@
  *     |---|---|---|---|---|---|
  *     | `oauth2-login` | ... | BFF `GET /login` | `AuthHandler.handle...()` | Token | `auth-handler.ts` |
  *
- * Path conventions (per ADR 0143 §4.3):
+ * Path conventions (per M-ADR 0143 §4.3):
  *   - platform-profile: `docs/domains/<dom>/design/<capability>/feature-grounding.md`
  *   - integration-product: `docs/design/integration/feature-grounding.md`
  *

package/dist/lib/catalogue/builders/feature-grounding.js

@@ -1,5 +1,5 @@
 /**
- * Feature-grounding extractor per ADR 0143 (schema 2.5.0).
+ * Feature-grounding extractor per M-ADR 0143 (schema 2.5.0).
  *
  * Walks `docs/domains/<dom>/design/<capability>/feature-grounding.md`
  * (platform-profile) and `docs/design/integration/feature-grounding.md`
@@ -19,7 +19,7 @@
  * findings but never break FK validation — only confidently-resolved
  * rows are emitted.
  *
- * Precedence per ADR 0143 §4.4: feature-tree and feature-spec rows
+ * Precedence per M-ADR 0143 §4.4: feature-tree and feature-spec rows
  * win on id collision; grounding rows are skipped with a divergence
  * finding.
  */
@@ -105,7 +105,7 @@ export async function buildFeatureGrounding(inputs) {
             // capability_feature row on the spec source path.
             //
             // feature_repo and feature_service edges: emit unconditionally per
-            // ADR 0143 §2 (these are the source's unique contribution; nothing
+            // M-ADR 0143 §2 (these are the source's unique contribution; nothing
             // else carries per-row code-mapping). Pre-0.30.2 the collision skip
             // dropped these edges too — bug fixed.
             if (featureRowCollides) {
@@ -114,7 +114,7 @@ export async function buildFeatureGrounding(inputs) {
                 //
                 // `seenFeatures` is seeded from earlier sources AND grows during this
                 // walk, so a hit means either:
-                //   - an earlier SOURCE emitted this id. That is ADR 0143 §2's
+                //   - an earlier SOURCE emitted this id. That is M-ADR 0143 §2's
                 //     documented precedence rule working exactly as specified: the
                 //     grounding pass re-declares ids that feature-tree/feature-spec
                 //     already own. It happens for essentially every grounded feature,
@@ -133,7 +133,7 @@ export async function buildFeatureGrounding(inputs) {
                 // of 1,545 accepted ones, so the whole category was unusable as a
                 // signal and unbaselineable as a backlog.
                 if (fromEarlierSource.has(featureId)) {
-                    inputs.findings.add("inferred", `${relPath}:${row.lineNumber}: feature id "${featureId}" already emitted by an earlier source (feature-tree / feature-spec wins for the row; feature_repo + feature_service edges still emitted per ADR 0143 §2)`);
+                    inputs.findings.add("inferred", `${relPath}:${row.lineNumber}: feature id "${featureId}" already emitted by an earlier source (feature-tree / feature-spec wins for the row; feature_repo + feature_service edges still emitted per M-ADR 0143 §2)`);
                 }
                 else {
                     inputs.findings.add("divergence", `${relPath}:${row.lineNumber}: feature id "${featureId}" already emitted by another file in this same feature-grounding pass — two files under one capability declare the same slug (first occurrence wins)`);

package/dist/lib/catalogue/builders/feature-subscription-channels.js

@@ -46,7 +46,7 @@ export async function buildFeatureSubscriptionChannels(inputs) {
         const relPath = relative(inputs.sddPath, file);
         // The per-design-dir `feature-grounding-evidence.yaml` is this builder's
         // dedicated contract — read/parse failures are its findings. The
-        // per-domain `<domain>-feature-grounding.yaml` files (ADR 0164) are
+        // per-domain `<domain>-feature-grounding.yaml` files (M-ADR 0164) are
         // primarily authored for other tooling and only opportunistically scanned
         // for a `feature_subscription_channels:` key; they may not be strict YAML,
         // so their read/parse failures are skipped silently (not this builder's
@@ -77,7 +77,7 @@ export async function buildFeatureSubscriptionChannels(inputs) {
             continue;
         // Per-feature subscription_channels live under `features:` (per-design-dir
         // layout) or a top-level `feature_subscription_channels:` list (per-domain
-        // layout, ADR 0164). Both are lists of { feature_slug, subscription_channels }.
+        // layout, M-ADR 0164). Both are lists of { feature_slug, subscription_channels }.
         const obj = parsed;
         const featureEntries = [];
         if (Array.isArray(obj["features"]))
@@ -192,7 +192,7 @@ async function walk(root, current, out) {
         if (e.isDirectory()) {
             // Check whether this is the reverse-evidence dir; if so, look for the file directly.
             if (e.name === "reverse-evidence") {
-                // Two reverse-evidence layouts are read (ADR 0164):
+                // Two reverse-evidence layouts are read (M-ADR 0164):
                 //   - per-design-dir: `reverse-evidence/feature-grounding-evidence.yaml`
                 //     (features: → per-feature subscription_channels:).
                 //   - per-domain: `reverse-evidence/<domain>-feature-grounding.yaml`

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

@@ -30,7 +30,7 @@
 import { readdir, readFile } from "node:fs/promises";
 import { basename, join, relative, sep } from "node:path";
 import { featureGroupId, findFeatureTreeFile, walkFeatureTree, } from "./feature-tree-walker.js";
-// ADR 0165: the standard, cross-SDD-comparable `features.maturity` vocabulary
+// M-ADR 0165: the standard, cross-SDD-comparable `features.maturity` vocabulary
 // (canonical-schema §features). Feature-tree `[runway: X]` markers whose value
 // is in this set ARE the maturity signal — wire them to `maturity` (comparable)
 // while `runway` keeps the full marker (adopter-owned, incl. non-standard values

package/dist/lib/catalogue/builders/glossary-xref.js

@@ -1,7 +1,7 @@
 // glossary_xref + entity_glossary edge builders — emit cross-domain glossary
 // relationships from `docs/platform/reference/glossary-alignment-manifest.yaml`.
 //
-// Per ADR 0158 (Glossary Cross-Reference Multi-Source Ingestion, schema 2.12.0),
+// Per M-ADR 0158 (Glossary Cross-Reference Multi-Source Ingestion, schema 2.12.0),
 // the builder ingests from FIVE walkers:
 //
 //   1. Forward declared pair-form (existing).
@@ -42,7 +42,7 @@ import { join } from "node:path";
 import { parse as parseYaml } from "yaml";
 const MANIFEST_REL_PATH = join("docs", "platform", "reference", "glossary-alignment-manifest.yaml");
 export async function buildGlossaryXref(inputs) {
-    // Profile gate per ADR 0158 §amendment: the manifest is platform-owned;
+    // Profile gate per M-ADR 0158 §amendment: the manifest is platform-owned;
     // sibling SDDs that syndicate it for documentation accessibility should
     // not re-emit rows. Mirrors the entities-manifest profile gate.
     if (inputs.profile !== "platform-profile") {
@@ -292,7 +292,7 @@ export async function buildGlossaryXref(inputs) {
                                 status: winner,
                             });
                         }
-                        inputs.findings.add("divergence", `${MANIFEST_REL_PATH}: entity ${name} in domain ${domain} has conflicting statuses across models (${existingStatus} vs ${status}) — keeping ${winner} (per ADR 0158)`);
+                        inputs.findings.add("divergence", `${MANIFEST_REL_PATH}: entity ${name} in domain ${domain} has conflicting statuses across models (${existingStatus} vs ${status}) — keeping ${winner} (per M-ADR 0158)`);
                         continue;
                     }
                     const row = {
@@ -321,7 +321,7 @@ export async function buildGlossaryXref(inputs) {
             || "cross_domain_terms" in obj
             || "models" in obj;
         if (!hasAnyKnownKey) {
-            inputs.findings.add("convention", `${MANIFEST_REL_PATH}: present but no recognised top-level keys (aliases/conflicts/cross_domain_terms/models) — emitting 0 xref rows (per ADR 0158)`);
+            inputs.findings.add("convention", `${MANIFEST_REL_PATH}: present but no recognised top-level keys (aliases/conflicts/cross_domain_terms/models) — emitting 0 xref rows (per M-ADR 0158)`);
         }
     }
     return { glossaryXref: xrefRows, entityGlossary: entityRows };

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

@@ -1,10 +1,10 @@
 // Integrations discoverer — emits `integrations.csv` rows from an
 // integration-product SDD's `integration-manifest.yaml`.
 //
-// Per ADR 0134 federation: each integration-provider SDD owns one row
+// Per M-ADR 0134 federation: each integration-provider SDD owns one row
 // in the granular integrations.csv. The aggregator merges siblings.
 //
-// Per ADR 0144 (schema 2.6.0): if the manifest declares an optional
+// Per M-ADR 0144 (schema 2.6.0): if the manifest declares an optional
 // `sub_integrations:` array (multi-provider monolith pattern), emit
 // one additional row per entry with parent_product_id set to the
 // SDD's integrationId. The umbrella SDD row stays unchanged.
@@ -29,7 +29,7 @@
 //   doc_path = SDD's doc_path
 //   repo_count = 0 (repo ownership stays with the umbrella)
 //
-// domain_id is always empty per ADR 0136.
+// domain_id is always empty per M-ADR 0136.
 import { readFile } from "node:fs/promises";
 import { join } from "node:path";
 import { parse as parseYaml } from "yaml";
@@ -111,7 +111,7 @@ export async function buildIntegrations(inputs) {
             source_sdd_id: "",
         },
     ];
-    // Per ADR 0144 (schema 2.6.0): emit one row per sub_integration with
+    // Per M-ADR 0144 (schema 2.6.0): emit one row per sub_integration with
     // parent_product_id = the umbrella SDD's id.
     const subs = parsed.data.sub_integrations ?? [];
     const seenSubIds = new Set([id]); // umbrella id is reserved

package/dist/lib/catalogue/builders/persona-c4system.js

@@ -1,5 +1,5 @@
 // persona_c4system edge builder — emits one row per `Person(...)` actor on
-// the L1 context diagram that maps to a known persona (per ADR 0155). This
+// the L1 context diagram that maps to a known persona (per M-ADR 0155). This
 // captures the C4 "Person uses System" relationship; the C4 Person
 // abstraction reuses the existing Persona entity rather than a parallel one.
 //