@sdd-method/author-cli 0.15.0 → 0.15.1

package/dist/lib/catalogue/build.js

@@ -90,7 +90,7 @@ export async function runCatalogueBuild(inputs, write) {
     const intendedRows = [];
     const rowsByCatalogue = modelFiles === null
         ? collected
-        : overlayModel(schema, viewOf(modelFiles, modelProblems), collected, findings, intendedWrites(open, agreedOrder(open)), intendedRows);
+        : withC4Rollups(overlayModel(schema, viewOf(modelFiles, modelProblems), collected, findings, intendedWrites(open, agreedOrder(open)), intendedRows));
     for (const p of modelProblems)
         findings.add("convention", `${p} (M-ADR 0230)`);
     // 3a. Normalise every keyed catalogue to PK-unique rows. Multi-source edge
@@ -1517,6 +1517,18 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     });
     return out;
 }
+/**
+ * The C4 roll-ups joined again over the catalogues the structural model settles (M-ADR 0159 §4.8, M-ADR 0230 §4.3).
+ * collectRows joins them over the sources, which can state an element an agreed open change adds; the overlay holds
+ * that element back until the change archives, and a roll-up row reaching it would be a current row referencing it.
+ */
+function withC4Rollups(rows) {
+    const c4Containers = rows.get("c4_containers") ?? [];
+    const containerEntityRows = buildC4ContainerEntity({ serviceEntityRows: rows.get("service_entity") ?? [], c4Containers });
+    rows.set("c4_container_entity", containerEntityRows);
+    rows.set("c4_system_entity", buildC4SystemEntity({ containerEntityRows, c4Containers }));
+    return rows;
+}
 const CONTEXT_CROSS_CUTTING = "cross-cutting";
 /**
  * Convention check (schema 2.21.0): where a screen carries `context` and the

package/dist/lib/validate/behaviour-store.js

@@ -86,6 +86,8 @@ const COMMIT_RE = /^[0-9a-f]{7,40}$/;
 // OpenSpec counts a task done when its box holds only `x`, either case, any spacing.
 const TASK_DONE_RE = /^\s*-\s*\[\s*[xX]\s*\]/m;
 const TARGET_HEADING_RE = /^##\s+(MODIFIED|REMOVED|RENAMED)\s+Requirements\b/m;
+// A tasks.md group headed by one word, `## <n>. <word>`, is that repository's work order (taskGroups).
+const GROUP_REPO = (repo) => `tasks.md has a work order for ${repo} and the record's work_orders do not; its evidence cannot be checked (a group heading of one word, \`## <n>. ${repo}\`, names the group's repository)`;
 async function exists(p) {
     try {
         await access(p);
@@ -516,6 +518,14 @@ export async function checkBehaviourStore(repo, options = {}) {
                 }
             }
         }
+        // The archive check reads a task group's repository from its heading; once the record declares work orders, a
+        // heading it would read as a repository the record lacks fails here, while the change can still be amended.
+        if (versionAtLeast(record?.schemaVersion, "1.1.0") && record?.status === "agreed" && record.workOrders.length > 0 && tasks !== null) {
+            const recorded = new Set(record.workOrders.map((w) => w.repo));
+            for (const g of taskGroups(tasks))
+                if (!recorded.has(g.repo))
+                    failures.push(`${record.file}: ${GROUP_REPO(g.repo)}`);
+        }
         // A test plan's kinds (M-ADR 0223 §4.4 as amended): changed and repaired scenarios go red then green, carried ones stay green.
         if (versionAtLeast(record?.schemaVersion, "1.1.0") && record?.status === "agreed") {
             const plan = await readText(join(repo, dir, "test-plan.md"));
@@ -717,7 +727,7 @@ export async function checkBehaviourStore(repo, options = {}) {
         const recorded = new Set(record.workOrders.map((w) => w.repo));
         for (const g of groups)
             if (!recorded.has(g.repo))
-                failures.push(`${record.file}: tasks.md has a work order for ${g.repo} and the record's work_orders do not; its evidence cannot be checked`);
+                failures.push(`${record.file}: ${GROUP_REPO(g.repo)}`);
         // Requirement names are unique within a feature, not across a change: a work order names `<feature>::<name>`,
         // or a bare name only one feature in the change has (schema 5.0.0). An ambiguous bare name implements nothing.
         const built = [];

package/dist/maintain-version.json

@@ -1,4 +1,4 @@
 {
-  "version": "0.16.0",
-  "built_against_sdd_cli": "5.2.0"
+  "version": "0.16.1",
+  "built_against_sdd_cli": "5.2.1"
 }

package/dist/verify-version.json

@@ -1,4 +1,4 @@
 {
-  "version": "5.2.0",
-  "built_against_sdd_cli": "5.2.0"
+  "version": "5.2.1",
+  "built_against_sdd_cli": "5.2.1"
 }

package/package.json

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