@sdd-method/maintain-cli 0.7.0 → 0.9.0

package/dist/lib/agent-harness.js

@@ -1,12 +1,12 @@
 /**
  * Agent-harness identifiers — the value space of `--agent-harness` on
- * `sdd-cli init`, `sdd-cli sync` and `context pull` per ADR 0141 §4.6.
+ * `sdd-cli init`, `sdd-cli sync` and `context pull` per M-ADR 0141 §4.6.
  *
  * Claude Code is the one supported harness (M-ADR 0220 §4.6) and the default. The GitHub Copilot
  * CLI value is retired: passing it fails, naming that record. Every SDD and code repository also
  * gets an AGENTS.md pointer to agent-instructions.md, with no flag; it is a pointer, not support
  * for another harness. Adopters binding any other harness implement the portable contracts
- * themselves (ADR 0141 §4.5).
+ * themselves (M-ADR 0141 §4.5).
  */
 export const AGENT_HARNESSES = ["claude-code"];
 export const DEFAULT_AGENT_HARNESS = "claude-code";

package/dist/lib/briefing/index.js

@@ -1,5 +1,5 @@
 /**
- * Public facade for the briefing layer (ADR 0148).
+ * Public facade for the briefing layer (M-ADR 0148).
  *
  * `agent-instructions.md` is the harness-neutral canonical briefing
  * (fully method-managed; sync overwrites unconditionally). Harness

package/dist/lib/briefing/render.js

@@ -1,5 +1,5 @@
 /**
- * Renderer for the briefing-layer templates per ADR 0148.
+ * Renderer for the briefing-layer templates per M-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,5 +1,5 @@
 /**
- * Variable resolution for the briefing layer per ADR 0148 §4.1.
+ * Variable resolution for the briefing layer per M-ADR 0148 §4.1.
  *
  * The four variables are sourced from target-repo state:
  *

package/dist/lib/bundle.js

@@ -64,7 +64,7 @@ export function parseManifest(raw) {
     const isForwardBaseInferred = isForwardBaseRaw === null ? isForwardBase(bundleName) : isForwardBaseRaw;
     // Forward bases must use a known bundle name; adopter packs may use
     // any string. This enforces the closed enum where it matters and
-    // opens it where ADR 0151 requires.
+    // opens it where M-ADR 0151 requires.
     if (isForwardBaseInferred && !isBundleName(bundleName)) {
         throw new Error(`Unknown bundle_name in manifest for forward base: ${JSON.stringify(bundleName)}`);
     }

package/dist/lib/catalogue/aggregate.js

@@ -161,7 +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 ADR 0134.
+    // See M-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
@@ -389,12 +389,12 @@ export async function runCatalogueAggregate(inputs, write) {
     // integration builds emit screen_feature rows carrying the bare `realises:`
     // slug when the feature lives in another SDD (the platform). Rewrite those
     // to the resolved platform feature id by matching the slug against every
-    // merged feature's slug. One slug vocabulary per capability (ADR 0177), so
+    // merged feature's slug. One slug vocabulary per capability (M-ADR 0177), so
     // a single match is authoritative; an ambiguous estate-wide match is refused
     // with a divergence finding (never guessed); no match is an orphan finding.
     rowsByCatalogue.set("screen_feature", resolveCrossSddScreenFeature(rowsByCatalogue.get("screen_feature") ?? [], rowsByCatalogue.get("features") ?? [], findings));
     // @rule aggregate-external-system-dedup
-    // 5b. Dedup c4_external_systems by id (ADR 0155). External systems are
+    // 5b. Dedup c4_external_systems by id (M-ADR 0155). External systems are
     // inherently shared references — the same external (e.g. ext-google-maps)
     // may be declared by multiple SDDs. This is the one narrowly-scoped
     // exception to the duplicate-PK rule: identical rows merge (first-seen
@@ -413,7 +413,7 @@ export async function runCatalogueAggregate(inputs, write) {
     // / domain ADRs are NOT deduped — a collision there is a genuine error.
     await dedupMethodScopedAdrs(rowsByCatalogue, findings, sddRootsById);
     // @rule aggregate-federated-reverse-metadata-enrichment
-    // 5c. Federated reverse-metadata enrichment (ADR 0163 P2). Both reference
+    // 5c. Federated reverse-metadata enrichment (M-ADR 0163 P2). Both reference
     // adopters centralise the service inventory in the platform-root, but for
     // reverse-method federations the per-service evidence (service-architecture.md)
     // lives one federation hop away, in member SDDs. The platform-root's own
@@ -598,7 +598,7 @@ export async function runCatalogueAggregate(inputs, write) {
         outDir,
     };
 }
-// ADR 0155: c4_external_systems rows dedup by id across SDDs rather than
+// M-ADR 0155: c4_external_systems rows dedup by id across SDDs rather than
 // failing the duplicate-PK check. First-seen row wins; a `source_sdd_id`
 // already stamped is preserved. Conflicting name/technology/description on
 // the same id emits a `convention` finding so authors can reconcile.
@@ -781,7 +781,7 @@ async function dedupMethodScopedAdrs(rowsByCatalogue, findings, sddRootsById) {
     }
     rowsByCatalogue.set("adrs", out);
 }
-// ADR 0163 P2: the reverse-derived metadata columns that a member SDD's
+// M-ADR 0163 P2: the reverse-derived metadata columns that a member SDD's
 // service-architecture.md can backfill onto a platform-root service row.
 const FEDERATED_META_COLS = [
     "runtime_type",
@@ -1259,7 +1259,7 @@ function featureSlugOf(row) {
  * the slug against every merged feature's recovered slug:
  *   - exactly one match  → rewrite feature_id (and the composite PK).
  *   - >1 match           → ambiguous; refuse (divergence finding), leave as-is
- *                          so the FK pass surfaces it. ADR 0177 guarantees one
+ *                          so the FK pass surfaces it. M-ADR 0177 guarantees one
  *                          slug per *capability*, not estate-wide, so cross-
  *                          capability slug clashes are possible and not guessed.
  *   - 0 matches          → orphan finding, leave as-is.

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

@@ -5,7 +5,7 @@
  * tiered vocabulary. This module resolves a declared value against the union
  * of:
  *   - the **method tier** — `unclassified` only, built into sdd-cli (mirrors
- *     how the ADR 0173/0176 method-tier scaffold archetypes are built in);
+ *     how the M-ADR 0173/0176 method-tier scaffold archetypes are built in);
  *   - the **reference-architecture / adopter bundle tiers** — seedless
  *     vocabulary files (`application-archetypes.yaml`) shipped in consumed
  *     bundles and extracted to the local bundle cache
@@ -13,7 +13,7 @@
  *   - an optional **adopter-local** extension file at
  *     `.sdd/application-archetypes.yaml` in the SDD repo.
  *
- * This deliberately does NOT reuse the ADR 0176 scaffold registry resolver
+ * This deliberately does NOT reuse the M-ADR 0176 scaffold registry resolver
  * (`scaffold/registry.ts`): that resolver is seed-oriented and drops any
  * entry with no `seeds[]`, whereas a classification archetype is seedless by
  * design. It DOES share the same bundle-cache distribution substrate — this

package/dist/lib/catalogue/archetype/maps/android.yaml

@@ -1,8 +1,8 @@
-# Default archetype map — android (ADR 0169 §4.2). Method-owned.
+# Default archetype map — android (M-ADR 0169 §4.2). Method-owned.
 #
 # Android View + Material toolkit. These names are industry-standard (Google/AndroidX/Material)
 # and identical across every Android app — never an adopter's bespoke vocabulary.
-# Resolution order (ADR 0169 §4.3): adopter overlay override -> by_token -> by_suffix_heuristic -> default.
+# Resolution order (M-ADR 0169 §4.3): adopter overlay override -> by_token -> by_suffix_heuristic -> default.
 # Selected per screen by `platform: android` frontmatter.
 
 map_version: "1.0.0"

package/dist/lib/catalogue/archetype/maps/swiftui.yaml

@@ -1,8 +1,8 @@
-# Default archetype map — swiftui (ADR 0169 §4.2). Method-owned.
+# Default archetype map — swiftui (M-ADR 0169 §4.2). Method-owned.
 #
 # Apple SwiftUI toolkit. Industry-standard Apple names, identical across every SwiftUI app —
 # never an adopter's bespoke vocabulary.
-# Resolution order (ADR 0169 §4.3): adopter overlay override -> by_token -> by_suffix_heuristic -> default.
+# Resolution order (M-ADR 0169 §4.3): adopter overlay override -> by_token -> by_suffix_heuristic -> default.
 # Selected per screen by `platform: swiftui` frontmatter.
 
 map_version: "1.0.0"

package/dist/lib/catalogue/archetype/maps/uikit.yaml

@@ -1,8 +1,8 @@
-# Default archetype map — uikit (ADR 0169 §4.2). Method-owned.
+# Default archetype map — uikit (M-ADR 0169 §4.2). Method-owned.
 #
 # Apple UIKit toolkit. Industry-standard Apple names (UI- prefixed), identical across every
 # UIKit app — never an adopter's bespoke vocabulary.
-# Resolution order (ADR 0169 §4.3): adopter overlay override -> by_token -> by_suffix_heuristic -> default.
+# Resolution order (M-ADR 0169 §4.3): adopter overlay override -> by_token -> by_suffix_heuristic -> default.
 # Selected per screen by `platform: uikit` frontmatter.
 
 map_version: "1.0.0"

package/dist/lib/catalogue/archetype/maps/web-generic.yaml

@@ -1,8 +1,8 @@
-# Default archetype map — web-generic (ADR 0169 §4.2). Method-owned.
+# Default archetype map — web-generic (M-ADR 0169 §4.2). Method-owned.
 #
 # Keys off component NAMES (which the builder already parses), not design-system source.
 # Vendor-standard / common-DS tokens ONLY — never an adopter's bespoke vocabulary.
-# Resolution order (ADR 0169 §4.3): adopter overlay override -> by_token -> by_suffix_heuristic -> default.
+# Resolution order (M-ADR 0169 §4.3): adopter overlay override -> by_token -> by_suffix_heuristic -> default.
 # Selected per screen by `platform: web-generic` (or web) frontmatter.
 
 map_version: "1.0.0"

package/dist/lib/catalogue/archetype/openui-archetype-vocabulary.yaml

@@ -1,12 +1,12 @@
-# OpenUI Archetype Vocabulary — method-owned (ADR 0169 §4.1)
+# OpenUI Archetype Vocabulary — method-owned (M-ADR 0169 §4.1)
 #
 # A closed, platform-tagged superset of visual archetypes. An archetype assigns a
 # component a VISUAL SHAPE + slots/orientation — never geometry or styling (stays inside
-# the compose-only boundary, ADR 0166 §3). Default archetype maps
+# the compose-only boundary, M-ADR 0166 §3). Default archetype maps
 # (archetype-maps/*.yaml) resolve adopter component NAMES to entries here; the
 # render-screen-wireframe skill lowers a resolved tree to SVG using `render`.
 #
-# `is_container` feeds ADR 0168 §4.1 isContainer when a resolved map is present.
+# `is_container` feeds M-ADR 0168 §4.1 isContainer when a resolved map is present.
 
 vocabulary_version: "1.0.0"
 

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

@@ -1,12 +1,12 @@
-// OpenUI archetype resolver (per ADR 0169).
+// OpenUI archetype resolver (per M-ADR 0169).
 //
 // Binds an adopter component NAME to a visual ARCHETYPE via a method-shipped
 // platform default map plus an optional adopter overlay. The binding is what
 // makes a shape-blind openui-lang block renderable as a wireframe, and it
-// supplies the container/leaf classification the ADR 0168 `screen-root-is-leaf`
+// supplies the container/leaf classification the M-ADR 0168 `screen-root-is-leaf`
 // check consumes (isContainerArchetype).
 //
-// Resolution order (ADR 0169 §4.3): adopter override -> default by_token (after
+// Resolution order (M-ADR 0169 §4.3): adopter override -> default by_token (after
 // stripping a vendor prefix) -> by_suffix_heuristic -> default (panel).
 //
 // The vocabulary + the four default maps are method-owned reference data,
@@ -74,7 +74,7 @@ export function resolveArchetype(name, platform, overlay) {
 }
 /**
  * Whether a component classifies as a container archetype for a platform.
- * Used by ADR 0168 §4.1 isContainer to refine the appears-with-children
+ * Used by M-ADR 0168 §4.1 isContainer to refine the appears-with-children
  * heuristic. Returns undefined when the platform has no map (caller falls back
  * to the heuristic) so an absent map never mis-classifies a known container.
  */

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

@@ -1,4 +1,4 @@
-// Deterministic structural-wireframe renderer (ADR 0169 §4.4).
+// Deterministic structural-wireframe renderer (M-ADR 0169 §4.4).
 //
 // Lowers a screen's openui-lang block to an SVG wireframe: parse the block into
 // a composition tree, resolve each node to a visual archetype, and lay it out

package/dist/lib/catalogue/build.js

@@ -1,7 +1,7 @@
 /**
  * Per-SDD catalogue builder — `sdd-cli catalogue build` orchestrator.
  *
- * Per ADR 0134 §4.6, the canonical builder reads method-defined declarative
+ * Per M-ADR 0134 §4.6, the canonical builder reads method-defined declarative
  * inputs and emits `catalogues/*.csv` matching the canonical schema.
  *
  * The orchestrator provides:
@@ -119,7 +119,7 @@ export async function runCatalogueBuild(inputs, write) {
     }
     // 5. Internal FK validation (external FKs logged as findings). Pass the
     // SDD profile so profile-external FKs (schema 2.23.0, e.g. an app/integration
-    // capability's platform-resident domain_id per ADR 0136) resolve at
+    // capability's platform-resident domain_id per M-ADR 0136) resolve at
     // aggregation instead of failing this local build.
     const { fk, enums } = await validateWithEngineToLog(schema, rowsByCatalogue, findings, { profile: manifest.profile });
     // 5b. Bound-enum validation (M-ADR 0203 §4.1): every column_enums-bound
@@ -172,7 +172,7 @@ export async function runCatalogueBuild(inputs, write) {
     // declared primary-key uniqueness — always a hard failure, like a dangling
     // internal FK. (The silent-union path is not a failure: it is the expected
     // outcome of two sources asserting the same fact.)
-    // Error-severity findings (e.g. the ADR 0168 screen-spec status gate) fail the
+    // Error-severity findings (e.g. the M-ADR 0168 screen-spec status gate) fail the
     // build by default, independent of --strict.
     const exitCode = !fk.internalPass || dedupe.conflicts.length > 0 || findings.errorCount() > 0 || strictFail
         ? 1
@@ -312,7 +312,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         })));
     }
     // 5. Services derived 1:1 from runtime-typed repositories.
-    // Forward `description` source (ADR 0163 P1): repo-config `description:`,
+    // Forward `description` source (M-ADR 0163 P1): repo-config `description:`,
     // parsed but previously dropped by the repositories builder.
     const repoDescriptions = new Map();
     const declaredServicesByRepo = new Map();
@@ -503,18 +503,18 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         contractIdByPath: mergedContractIdByPath,
     }));
     // 10. Repo edges — repo_capability, repo_contract (feature_repo empty
-    // here; populated by feature-grounding extractor below per ADR 0143).
+    // here; populated by feature-grounding extractor below per M-ADR 0143).
     const capabilityIdByPath = new Map();
     for (const cap of capabilities) {
         const sp = String(cap["spec_path"] ?? "");
         if (sp !== "")
             capabilityIdByPath.set(sp, String(cap["id"]));
     }
-    // Per ADR 0157, repo-edges has both forward-declared (additional_context,
+    // Per M-ADR 0157, repo-edges has both forward-declared (additional_context,
     // repo-config.contracts) and reverse-derived (capability_service ⋈
     // services.primary_repo_id, contracts.source_repo_id denorm) paths. Note
     // that the capability_feature ⋈ feature_repo path (Y) needs feature_repo
-    // populated, which the ADR 0143 extractor below (10a) does — but repo-edges
+    // populated, which the M-ADR 0143 extractor below (10a) does — but repo-edges
     // runs first. So Path Y picks up zero rows here; the second pass after
     // grounding extracts (below) appends the missing edges.
     const knownRepoIds = new Set(repos.map((r) => String(r["id"])));
@@ -558,7 +558,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         knownServiceIds: knownServiceIdsForExemption,
         allowedReasons: serviceExemptionReasons,
     }));
-    // 10a. Feature-grounding extractor per ADR 0143 (schema 2.5.0).
+    // 10a. Feature-grounding extractor per M-ADR 0143 (schema 2.5.0).
     // Walks docs/domains/*/design/*/feature-grounding.md (platform-profile)
     // or docs/design/integration/feature-grounding.md (integration-product)
     // and emits feature rows (source: feature-grounding) plus capability_feature,
@@ -588,7 +588,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         ]);
     }
     // feature_repo + feature_service edges are stored unconditionally —
-    // per ADR 0143 §2 they're grounding's unique contribution and must
+    // per M-ADR 0143 §2 they're grounding's unique contribution and must
     // 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
@@ -599,13 +599,13 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     ]);
     // feature_service starts here — earlier passes don't populate it.
     out.set("feature_service", grounding.featureServiceRows);
-    // 10b. Capability-spec extractor per ADR 0145 (schema 2.7.0).
+    // 10b. Capability-spec extractor per M-ADR 0145 (schema 2.7.0).
     // Walks docs/domains/*/product/*.md (platform-profile only) and emits
     // feature rows (source: capability-spec) plus capability_feature,
     // feature_repo, feature_service edges from the
     // `## Feature Grounding (code-path trace)` table. Runs after the
     // feature-grounding extractor so precedence (feature-grounding wins
-    // on id collision) is enforced. Reuses ADR 0143's alias map for
+    // on id collision) is enforced. Reuses M-ADR 0143's alias map for
     // service / repo resolution.
     const existingFeatureIdsAfterGrounding = new Set((out.get("features") ?? []).map((r) => String(r["id"])));
     const capabilitySpec = await buildCapabilitySpec({
@@ -629,7 +629,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         ]);
     }
     // feature_repo + feature_service edges are stored unconditionally —
-    // per ADR 0145 they're capability-spec's unique contribution and must
+    // per M-ADR 0145 they're capability-spec's unique contribution and must
     // 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
@@ -714,7 +714,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
             out.set("feature_repo", [...existingFeatureRepo, ...derived]);
         }
     }
-    // 10b-bis. Second pass on repo_capability Path Y (per ADR 0157 §4.3) —
+    // 10b-bis. Second pass on repo_capability Path Y (per M-ADR 0157 §4.3) —
     // capability_feature ⋈ feature_repo. The initial repo-edges pass (step 10)
     // ran before the feature-grounding extractor populated feature_repo, so
     // Path Y picked up zero rows there. Now that feature_repo is fully built,
@@ -821,7 +821,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         }
     }
     // 11. Events + service_event + capability_event.
-    // Per ADR 0156 (schema 2.12.0), events ingest from both the forward-method
+    // Per M-ADR 0156 (schema 2.12.0), events ingest from both the forward-method
     // avsc path and the reverse-method `event-catalog.yaml` path. YAML wins on
     // name/domain/publisher/transport; avsc augments schema_path/version.
     // service_event edges populate from both repo-config events.produces/consumes
@@ -863,7 +863,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     // repos/<service>/docs/service-architecture.md External Interfaces table.
     // The consumes-emission path is gated on an adopter-supplied
     // .sdd/service-contract-aliases.yaml mapping interface display text to
-    // canonical contract names. Pattern documented in ADR 0147.
+    // canonical contract names. Pattern documented in M-ADR 0147.
     const exposesRows = buildServiceContract({
         findings,
         configs: reposResult.configs,
@@ -900,7 +900,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
             }
         }
     }
-    // 12-bis. Second pass on repo_contract Path X (per ADR 0157 §4.2 amendment) —
+    // 12-bis. Second pass on repo_contract Path X (per M-ADR 0157 §4.2 amendment) —
     // service_contract ⋈ services.primary_repo_id. The initial repo-edges pass
     // (step 10) ran before service_contract was built, so Path X picked up zero
     // rows there. Now that service_contract is fully populated, derive the
@@ -947,9 +947,9 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         featureServiceRows: out.get("feature_service") ?? [],
         serviceContractRows: out.get("service_contract") ?? [],
     }));
-    // 12a-bis. feature_event — derived edge per schema 2.15.0 / ADR 0161.
+    // 12a-bis. feature_event — derived edge per schema 2.15.0 / M-ADR 0161.
     // Pure join of feature_service ⋈ service_event; no authored shape. Mirrors
-    // ADR 0160's capability_event derived path one rung lower in the hierarchy.
+    // M-ADR 0160's capability_event derived path one rung lower in the hierarchy.
     out.set("feature_event", buildFeatureEvent({
         knownFeatureIds: featureIdsAfterAllSources,
         knownEventIds,
@@ -957,7 +957,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         serviceEventRows: out.get("service_event") ?? [],
     }));
     // 12b. domain_models + capability_domain_model + feature_domain_model
-    // per schema 2.4.0 / ADR 0142. Platform-profile only — non-platform
+    // per schema 2.4.0 / M-ADR 0142. Platform-profile only — non-platform
     // builds emit headers-only. domain_models runs first; the edges depend
     // on its known-id set.
     const domainModels = await buildDomainModels({
@@ -984,8 +984,8 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         capabilityDomainModelRows: out.get("capability_domain_model") ?? [],
     }));
     // 13. App-product profile builders (personas, journeys, persona/journey
-    // edges, product-edges). Per ADR 0134, app-product SDDs emit these
-    // catalogues; other profiles emit zero rows. Per ADR 0136, product_*
+    // edges, product-edges). Per M-ADR 0134, app-product SDDs emit these
+    // catalogues; other profiles emit zero rows. Per M-ADR 0136, product_*
     // edges' capability_id and service_id are external FKs validated by
     // the aggregator, not here.
     const featureIdByPath = featuresResult.idByPath;
@@ -1024,12 +1024,12 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         featureIdByPath,
         featureIdBySlug,
     }));
-    // UI screens family (per ADR 0166). Application-product profile; the walker
+    // UI screens family (per M-ADR 0166). Application-product profile; the walker
     // reads `screens/*.md` screen-spec artefacts (frontmatter + ```openui-lang
     // block) and emits the six catalogues. Other profiles have no screens/ dir →
     // empty. FK resolution uses the feature + persona id maps already built.
-    // Optional adopter-tunable screen-validation parameters (ADR 0168 §4.5 /
-    // ADR 0169 §4.3); absent → method defaults (the vocabulary-free checks run).
+    // Optional adopter-tunable screen-validation parameters (M-ADR 0168 §4.5 /
+    // M-ADR 0169 §4.3); absent → method defaults (the vocabulary-free checks run).
     const screenValidation = await loadScreenValidationConfig(sddPath);
     const screensResult = await buildScreens({
         sddPath,
@@ -1091,7 +1091,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     });
     out.set("scaffolds", scaffoldsResult.scaffolds);
     out.set("scaffold_items", scaffoldsResult.scaffoldItems);
-    // Screen↔capability context cross-check (ADR 0170 §4.6, schema 2.21.0):
+    // Screen↔capability context cross-check (M-ADR 0170 §4.6, schema 2.21.0):
     // a screen's `context:` should equal the context of the capability it
     // realises (screen → screen_feature → feature.capability_id →
     // capability.context). Convention finding, never an FK failure — the
@@ -1203,7 +1203,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         c4ContainerRows: c4Containers,
     });
     out.set("c4_components", c4Components);
-    // 15b. C4 L1 context elements (ADR 0155): external systems + the
+    // 15b. C4 L1 context elements (M-ADR 0155): external systems + the
     // persona→system and system→external edges, extracted from System_Ext /
     // Person / Rel macros on the L1/L2 diagrams. (The rows were computed at
     // step 7, where capability_service consults them — see above.)
@@ -1274,7 +1274,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     });
     out.set("glossary_items", glossaryResult.rows);
     const knownGlossaryIds = new Set(glossaryResult.rows.map((r) => String(r["id"])));
-    // Per ADR 0158 (schema 2.12.0), the glossary-xref builder ingests from
+    // Per M-ADR 0158 (schema 2.12.0), the glossary-xref builder ingests from
     // five walkers and emits two catalogues: glossary_xref (term-to-term
     // relations) and entity_glossary (new sibling — data-model entity to
     // canonical term mappings).
@@ -1291,7 +1291,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     // Backfill canonical_term_id + aliases onto glossary_items from the xref
     // edges (same alignment manifest, resolved downstream).
     out.set("glossary_items", backfillGlossaryRelations(glossaryResult.rows, xref.glossaryXref));
-    // 17. Data-model entities + service_entity + C4 roll-ups per ADR 0159
+    // 17. Data-model entities + service_entity + C4 roll-ups per M-ADR 0159
     // (schema 2.13.0). Four new catalogues, five walkers:
     //
     //   - entities-manifest: forward path, reads models[].entities[] from
@@ -1322,7 +1322,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         knownGlossaryIds,
     });
     // Forward wins on attribute conflicts (matches per-adopter authoring intent
-    // per ADR 0159 §4.4). Reverse rows seed the map; forward overwrites.
+    // per M-ADR 0159 §4.4). Reverse rows seed the map; forward overwrites.
     const entitiesById = new Map();
     for (const r of entitiesFromMermaid)
         entitiesById.set(String(r["id"]), r);
@@ -1330,9 +1330,9 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         entitiesById.set(String(r["id"]), r);
     const entityRows = [...entitiesById.values()];
     out.set("entities", entityRows);
-    // Per ADR 0159 §4.9: now that entities.csv exists, append entity_glossary
+    // Per M-ADR 0159 §4.9: now that entities.csv exists, append entity_glossary
     // rows for the reverse-method side. The forward-method emission via
-    // glossary-xref's models[].entities[] walker (ADR 0158) is already in
+    // glossary-xref's models[].entities[] walker (M-ADR 0158) is already in
     // xref.entityGlossary; here we extend with rows derived from
     // entities-mermaid's slug-matched glossary_term FKs.
     const existingEntityGlossaryPks = new Set(xref.entityGlossary.map((r) => String(r["id"])));
@@ -1370,7 +1370,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         if (!entityIdBySlug.has(slug))
             entityIdBySlug.set(slug, id);
     }
-    // ADR 0164: backfill entities.persistence_kind from the Data Store Mapping
+    // M-ADR 0164: backfill entities.persistence_kind from the Data Store Mapping
     // Store column (reverse-only; forward store-less tables leave it empty).
     const enrichedEntityRows = await enrichEntityPersistenceKind({
         sddPath,
@@ -1466,7 +1466,7 @@ function checkScreenCapabilityContext(args) {
         if (sCtx !== cCtx) {
             args.findings.add("convention", `screen-capability context mismatch: screen "${screenId}" ` +
                 `(context=${sCtx}) realises capability "${capId}" ` +
-                `(context=${cCtx}) — a seam screen or a mistag (ADR 0170 §4.6)`);
+                `(context=${cCtx}) — a seam screen or a mistag (M-ADR 0170 §4.6)`);
         }
     }
 }

package/dist/lib/catalogue/builders/adr-supersedes.js

@@ -2,11 +2,11 @@
 // ADR pair where either side declares the relationship:
 //   - the superseding ADR's `Supersedes:` text references a known ADR id, or
 //   - the superseded ADR's `Superseded By:` text references a known ADR id
-//     (the ADR 0174 §4.5 lazy-migration case: distributed reference ADRs are
+//     (the M-ADR 0174 §4.5 lazy-migration case: distributed reference ADRs are
 //     adopter-agnostic and cannot name adopter ADR numbers, so only the
 //     superseded local copy carries the link — including the cross-repo
 //     `<repo>#9000` form, whose number resolves locally once the bundle that
-//     ships ADR 9000 is pinned).
+//     ships RA-ADR 9000 is pinned).
 //
 // Only rows where BOTH endpoints resolve to known ADR ids are emitted —
 // the canonical schema's FKs on this edge are required+internal.
@@ -14,7 +14,7 @@
 // Also computes the inverse (`superseded_by_id`) backfill values that the
 // orchestrator stitches into adrs.csv after this builder runs.
 const ADR_REF_RE = /\bADR[\s\-_]?(\d{3,4})\b/gi;
-// `Superseded By:` additionally accepts the ADR 0140 cross-repo reference
+// `Superseded By:` additionally accepts the M-ADR 0140 cross-repo reference
 // form `<repo>#9000` — the lazy-migration case, where the superseding
 // record lives in a distributed bundle. Procedural citations of the
 // migration rule itself ("per sdd-method#0174 §4.5") are stripped first

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

@@ -8,7 +8,7 @@
 //     platform-foundational 0001-0099 band per M-ADR 0140)
 //   - docs/domains/<domain>/architecture/adr/ADR XXXX: Title.md
 //
-// Per ADR 0136 the method-scope ADRs are owned by the platform-root in
+// Per M-ADR 0136 the method-scope ADRs are owned by the platform-root in
 // the federation chain (the highest-up SDD that holds them via the seed-
 // file distribution). App and integration profile SDDs skip emission of
 // method-scope ADRs so the aggregated catalogue carries each method ADR
@@ -64,7 +64,7 @@ export async function buildAdrs(inputs) {
         const relPath = relative(inputs.sddPath, file);
         const { domainId, scope } = scopeFromPath(relPath);
         if ((scope === "method" || scope === "platform") && !ownsMethodScope) {
-            // Per ADR 0136: method- and platform-scope ADRs are emitted only by
+            // Per M-ADR 0136: method- and platform-scope ADRs are emitted only by
             // the SDD that owns the platform scope (platform-profile in
             // adopting ecosystems). App and integration SDDs hold seed-file
             // copies on disk but do not contribute them to the federated
@@ -100,7 +100,7 @@ export async function buildAdrs(inputs) {
         });
     }
     if (methodScopeSkipCount > 0) {
-        inputs.findings.add("coverage", `${methodScopeSkipCount} method/platform-scope ADR(s) skipped — emitted by ecosystem root only per ADR 0136`);
+        inputs.findings.add("coverage", `${methodScopeSkipCount} method/platform-scope ADR(s) skipped — emitted by ecosystem root only per M-ADR 0136`);
     }
     const rows = parsed.map((a) => ({
         id: a.id,

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

@@ -24,7 +24,7 @@ import { join, sep } from "node:path";
 const L2_BASENAME = "c4-l2-container.mermaid.md";
 // Boundary opener: `System_Boundary(id, "name") {` or `Container_Boundary(...)`.
 const BOUNDARY_OPEN_RE = /^(System_Boundary|Container_Boundary)\s*\(\s*\w+/;
-// C4-PlantUML container entries inside boundaries. Per ADR 0155 the
+// C4-PlantUML container entries inside boundaries. Per M-ADR 0155 the
 // canonical c4_container_type is Application | Data Store only:
 //   Container(id, "name", "tech", "desc")       → Application
 //   ContainerDb(id, "name", "tech", "desc")     → Data Store
@@ -159,7 +159,7 @@ async function collectL2Files(sddPath) {
     // Lives at the SDD docs/ root; the system is the SDD itself (one
     // c4_systems row per SDD), so the boundary in the L2 is the product
     // boundary. domain_id is left empty — federated app/integration
-    // products do not have a primary domain per ADR 0136.
+    // products do not have a primary domain per M-ADR 0136.
     const productRel = join("docs", L2_BASENAME);
     const productAbs = join(sddPath, productRel);
     if (await isFile(productAbs)) {

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