@ybotok/loam 0.2.0-alpha.4 → 0.2.0-alpha.6

package/dist/commands/validate/fleet/views/fleet-project.js

@@ -0,0 +1,217 @@
+/**
+ * `c4.fleet-project-invalid` — the one thing no per-document grade can see:
+ * every document loam reads is clean, and the project the RENDERER builds out of
+ * them is not.
+ *
+ * loam grades a fleet document by document, and that is deliberate: a service's
+ * model is graded on its own merits, and one broken model must not blank the
+ * fleet. The renderer has no such rule. Point `npx likec4 start` at the docs
+ * root and it merges every `.likec4` the root project reads into ONE model — the
+ * map, every extending model, and every `.likec4` sitting beside one — so a
+ * declaration made in two of those documents is a duplicate there and nowhere
+ * else. Measured at the 1.59.2 pin: a tags-only `specification { tag req-X }` in
+ * an extending model is legal, and the SAME tag declared in a second extending
+ * model is a duplicate blamed on both files. Two services, two clean grades, and
+ * a renderer that draws nothing.
+ *
+ * So this is one extra load, and it is the renderer's reading rather than
+ * loam's. What it reports is the SET DIFFERENCE: an error already reported where
+ * loam grades that document — the map's own parse, a per-service project's
+ * `c4.invalid`, a service flow project's use-case failure — is not repeated
+ * here, because the fix is one file either way and N copies of one cascade is
+ * the report. What is left over is exactly the class above: errors that exist
+ * only because these documents were merged.
+ *
+ * WHICH DOCUMENTS ARE IN IT is `./root-documents.ts`'s question, and it is a
+ * walk of the docs root rather than a list of the shapes loam knows about: a
+ * `.likec4` in a SUBSYSTEM directory — the parent of service directories — was
+ * in none of the three roots this used to merge, and went unreported while the
+ * renderer refused the whole project over it (verification 2026-09-04, R2). That
+ * module also carries why the generated `architecture/subsystems.likec4`,
+ * every standalone service directory and `features/` stay out.
+ *
+ * `--all` ONLY, and only when at least one model extends the map, the map itself
+ * parses, and the root `exclude` does not hide it. A single-target run has not
+ * enumerated the fleet, so it cannot build the project at all; a fleet whose
+ * models all stand alone has no such project (every one of them is excluded from
+ * the root); and a map that does not parse would report its own cascade here
+ * under a second code while `landscape.invalid` already names the file.
+ *
+ * THE LAST OF THOSE GATES IS THE CASCADE RULE, the one `permissions.invalid` and
+ * `capability.invalid` already state: a grade that resolves against a
+ * document nobody loaded is not a diagnosis. `architectureProjectDocuments`
+ * keeps the map whatever the root `exclude` says — that floor is what stopped
+ * loam asserting a fleet's map declares nothing — but this load has no such
+ * floor ON PURPOSE, because its whole claim is to read what the renderer reads.
+ * So an entry covering `architecture/landscape.likec4` leaves every extending
+ * model in the project with its `extend <fqn>` resolving against nothing:
+ * measured on `examples/docs` with `architecture/*.likec4` in the list, one
+ * authored line came back as 161 warnings under this code. `landscape.excluded`
+ * (`./projects.ts`) is the one finding that names the cause, and it says the
+ * fleet project is not graded until the entry goes. The fact arrives as
+ * `mapExcluded` rather than being re-read here, so the two can never disagree
+ * about which state they are in.
+ *
+ * WHY A WARNING. Nothing loam concludes changes: every model still parses where
+ * loam reads it, every binding still resolves, the spine is unaffected. What is
+ * broken is the picture, which is what `service.likec4-config-missing` and its
+ * three siblings in `./projects.ts` also grade, at the same severity.
+ */
+import { existsSync } from "node:fs";
+import { relative, resolve, sep } from "node:path";
+import { errorText } from "../../../../core/c4/likec4.js";
+import { asLoadedDoc, loadProject } from "../../../../core/c4/project/load.js";
+import { FleetContext } from "../../../../core/fleet-context.js";
+import { inOrder } from "../../../../core/kernel/concurrency.js";
+import { servicePathsAt } from "../../../../core/repo/paths.js";
+import { readServiceFlows } from "../../../../core/usecases/service/flows.js";
+import { rootProjectDocuments } from "./root-documents.js";
+export async function fleetProjectFindings(check) {
+    // A map that did not parse is `landscape.invalid`'s, and this load would only
+    // repeat its cascade under a second code.
+    if (check.architecture.errors.length > 0)
+        return { kind: "skipped" };
+    // A map the root `exclude` hides is `landscape.excluded`'s, for the same
+    // reason one line up — see the banner's cascade-rule paragraph. The view-id
+    // census goes with it: `clean` is a claim about a project that parsed, and
+    // there is none.
+    if (check.mapExcluded)
+        return { kind: "skipped" };
+    const shapeOf = (entry) => {
+        const model = servicePathsAt(entry.dir).model;
+        return existsSync(model) ? (check.shapes.get(resolve(model)) ?? null) : null;
+    };
+    const extending = check.entries.filter((entry) => shapeOf(entry) === "extending");
+    if (extending.length === 0)
+        return { kind: "skipped" };
+    const paths = extending.map((entry) => servicePathsAt(entry.dir));
+    // The TREE, not three roots. `./root-documents.ts` carries what comes out of
+    // it and why; the standalone directories are handed in because their shape is
+    // this run's memo and re-reading every model here would be a second scanner.
+    const documents = await rootProjectDocuments(check.docsDir, check.entries.filter((entry) => shapeOf(entry) === "standalone").map((entry) => entry.dir));
+    const project = await loadProject(check.docsDir, documents);
+    if (project.clean) {
+        // The census `subsystem.view-id-collision` needs and could not have until
+        // now: an extending model's authored view ids live in the SAME flat
+        // namespace as the map's, because both documents are in this project. The
+        // claims arrive docs-relative, which is the spelling `viewIdFindings` takes.
+        return { kind: "clean", viewIds: project.viewIds };
+    }
+    const reported = await alreadyReported(check, paths);
+    const findings = [];
+    for (const err of asLoadedDoc(project).errors) {
+        if (reported.has(errorKey(err)))
+            continue;
+        const owner = extending.find((entry) => err.sourceFsPath !== undefined && err.sourceFsPath.startsWith(`${entry.dir}${sep}`));
+        const file = err.sourceFsPath === undefined ? null : relative(check.docsDir, err.sourceFsPath).split(/[\\/]/).join("/");
+        findings.push({
+            severity: "warn",
+            code: "c4.fleet-project-invalid",
+            ...(owner === undefined ? {} : { subject: owner.id }),
+            // The file the error is IN, never the map by default: `locations[0].path`
+            // was `architecture/landscape.likec4` on every one of these, so a reader
+            // acting on the payload opened a document that was not the one at fault
+            // (verification 2026-09-04, D10). Absent when LikeC4 declined to attribute
+            // the error to a document at all — a location loam cannot spell is left
+            // unspelled rather than guessed.
+            ...(file === null ? {} : { locations: [{ path: file, role: "primary" }] }),
+            details: [file === null ? errorText(err) : `${file}: ${errorText(err)}`],
+            message: `fleet project: ${file ?? "the merged project"}: ${errorText(err)} — each document reads clean where ` +
+                "loam grades it, but the renderer merges every `.likec4` the root project reads except the generated " +
+                "subsystems.likec4 — the map, every extending model and every `.likec4` beside one — into ONE project, " +
+                `and that project does not parse. ${remedy(err.message)}`,
+        });
+    }
+    return { kind: "invalid", findings };
+}
+/**
+ * The tail that names WHICH failure this is.
+ *
+ * It used to say "a tag or an element declared in two of those documents is
+ * declared twice there" for every error, including the ones that are not a
+ * double declaration at all (verification 2026-09-04, D10) — an unresolved
+ * reference sent its reader hunting for a second declaration that does not
+ * exist. LikeC4's own wording is the evidence, matched loosely on purpose: an
+ * unrecognised message falls to the third arm, which asserts nothing beyond
+ * where to look.
+ */
+function remedy(message) {
+    if (/duplicat|already (declared|defined)|declared (more than once|twice)/i.test(message)) {
+        return ("A tag or an element declared in two of those documents is declared twice there; declare it once " +
+            "(the map, or the one service that owns it)");
+    }
+    if (/could not resolve|unresolved|unknown/i.test(message)) {
+        return ("A name resolves against ALL of those documents here, so a reference the renderer cannot place is one " +
+            "no document in the project declares; declare it where the reader can see it, or drop the reference");
+    }
+    return "Open the file and line named above — every reader who points a renderer at the docs root sees this";
+}
+/**
+ * Every parse error this run has ALREADY reported against one of these
+ * documents, keyed so the merged project's copy can be recognised.
+ *
+ * Two sources, and both are loads the run made anyway or would make: each
+ * extending model's own per-service project (`c4.invalid` on the service
+ * target) and, where nothing was wrong there, each service's FLOW project
+ * (`readServiceFlows` — the use-case grade names the file). The flow read goes
+ * through that function rather than a second `loadProject` here so the OPT-IN
+ * gate is the same one: a broken sibling that nothing tagged is loaded by
+ * neither, which is exactly why the merged project has to report it.
+ *
+ * Computed only when the merged project actually failed, which is why it is a
+ * function rather than an input: on a healthy fleet this whole file costs one
+ * load and nothing else.
+ *
+ * THE FLOW PROJECTS ARE PARSED AGAIN by `validateService` later in the same run,
+ * and that is accepted rather than unnoticed: it happens only on the path where
+ * the merged project already failed, so a healthy fleet pays nothing, and the
+ * `ServiceModel` half above IS the run's memo. If that path ever becomes hot,
+ * the follow-up is to memoise the flow scan on `FleetContext` beside the
+ * per-service projects — not to hand the scan in here, which would make this
+ * grade depend on an argument the caller has no reason to have loaded.
+ */
+async function alreadyReported(check, paths) {
+    // Both sets reach the same documents through `architectureProjectDocuments`,
+    // which now drops what the root `exclude` covers exactly as the merged load's
+    // own walk does — so a document out of one is out of both, and the generated
+    // `subsystems.likec4` is out of all of them without being remembered twice.
+    //
+    // Pooled rather than awaited one at a time: each entry is an independent
+    // LikeC4 workspace over one service's own documents, which is exactly the
+    // work `inOrder` rations — and a serial loop here made the ONE path that
+    // already costs a fleet its whole set of flow projects pay for them in
+    // sequence.
+    const perService = await inOrder(paths, async (service) => {
+        const model = await check.fleet.serviceModel(check.docsDir, service);
+        const errors = [...model.doc.errors];
+        if (errors.length > 0 || model.mapUnreadable)
+            return errors;
+        // `model.project` is non-null here by construction — these are extending
+        // models whose own load came back clean, which is the arm that carries it —
+        // and the guard is the compiler's rather than an assertion: a null would
+        // mean grading a flow against a document that did not load.
+        if (model.project === null)
+            return [];
+        const flows = await readServiceFlows({
+            paths: service,
+            model: model.doc,
+            known: check.known,
+            extending: { docsDir: check.docsDir, project: model.project },
+        });
+        return flows.kind === "unreadable" ? flows.errors : [];
+    });
+    return new Set(perService.flat().map(errorKey));
+}
+/**
+ * One error's identity across two loads of overlapping document sets: the real
+ * file, the line, and the message.
+ *
+ * There is no id to join on — LikeC4 mints diagnostics per parse — and the
+ * message has to be part of the key: two DIFFERENT problems on one line of one
+ * file are two errors, and collapsing them would let a merged-project-only
+ * failure hide behind a per-service one that happens to share a line.
+ */
+function errorKey(err) {
+    return JSON.stringify([err.sourceFsPath ?? "", err.line ?? -1, err.message]);
+}
+//# sourceMappingURL=fleet-project.js.map

package/dist/commands/validate/fleet/views/fleet-project.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"fleet-project.js","sourceRoot":"","sources":["../../../../../src/commands/validate/fleet/views/fleet-project.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA0DG;AACH,OAAO,EAAE,UAAU,EAAE,MAAM,SAAS,CAAC;AACrC,OAAO,EAAE,QAAQ,EAAE,OAAO,EAAE,GAAG,EAAE,MAAM,WAAW,CAAC;AACnD,OAAO,EAAE,SAAS,EAAoC,MAAM,+BAA+B,CAAC;AAC5F,OAAO,EAAE,WAAW,EAAE,WAAW,EAAE,MAAM,qCAAqC,CAAC;AAG/E,OAAO,EAAE,YAAY,EAAE,MAAM,mCAAmC,CAAC;AACjE,OAAO,EAAE,OAAO,EAAE,MAAM,wCAAwC,CAAC;AAGjE,OAAO,EAAE,cAAc,EAAqB,MAAM,gCAAgC,CAAC;AAEnF,OAAO,EAAE,gBAAgB,EAAE,MAAM,4CAA4C,CAAC;AAE9E,OAAO,EAAE,oBAAoB,EAAE,MAAM,qBAAqB,CAAC;AA+C3D,MAAM,CAAC,KAAK,UAAU,oBAAoB,CAAC,KAAwB;IACjE,8EAA8E;IAC9E,0CAA0C;IAC1C,IAAI,KAAK,CAAC,YAAY,CAAC,MAAM,CAAC,MAAM,GAAG,CAAC;QAAE,OAAO,EAAE,IAAI,EAAE,SAAS,EAAE,CAAC;IACrE,yEAAyE;IACzE,4EAA4E;IAC5E,2EAA2E;IAC3E,iBAAiB;IACjB,IAAI,KAAK,CAAC,WAAW;QAAE,OAAO,EAAE,IAAI,EAAE,SAAS,EAAE,CAAC;IAClD,MAAM,OAAO,GAAG,CAAC,KAAmB,EAAqB,EAAE;QACzD,MAAM,KAAK,GAAG,cAAc,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,KAAK,CAAC;QAC9C,OAAO,UAAU,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,MAAM,CAAC,GAAG,CAAC,OAAO,CAAC,KAAK,CAAC,CAAC,IAAI,IAAI,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC;IAC/E,CAAC,CAAC;IACF,MAAM,SAAS,GAAG,KAAK,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,OAAO,CAAC,KAAK,CAAC,KAAK,WAAW,CAAC,CAAC;IAClF,IAAI,SAAS,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,EAAE,IAAI,EAAE,SAAS,EAAE,CAAC;IAEvD,MAAM,KAAK,GAAG,SAAS,CAAC,GAAG,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,cAAc,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC;IAClE,6EAA6E;IAC7E,8EAA8E;IAC9E,6EAA6E;IAC7E,MAAM,SAAS,GAAG,MAAM,oBAAoB,CAC1C,KAAK,CAAC,OAAO,EACb,KAAK,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,OAAO,CAAC,KAAK,CAAC,KAAK,YAAY,CAAC,CAAC,GAAG,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,GAAG,CAAC,CAC3F,CAAC;IACF,MAAM,OAAO,GAAG,MAAM,WAAW,CAAC,KAAK,CAAC,OAAO,EAAE,SAAS,CAAC,CAAC;IAE5D,IAAI,OAAO,CAAC,KAAK,EAAE,CAAC;QAClB,0EAA0E;QAC1E,oEAAoE;QACpE,0EAA0E;QAC1E,6EAA6E;QAC7E,OAAO,EAAE,IAAI,EAAE,OAAO,EAAE,OAAO,EAAE,OAAO,CAAC,OAAO,EAAE,CAAC;IACrD,CAAC;IAED,MAAM,QAAQ,GAAG,MAAM,eAAe,CAAC,KAAK,EAAE,KAAK,CAAC,CAAC;IACrD,MAAM,QAAQ,GAAc,EAAE,CAAC;IAC/B,KAAK,MAAM,GAAG,IAAI,WAAW,CAAC,OAAO,CAAC,CAAC,MAAM,EAAE,CAAC;QAC9C,IAAI,QAAQ,CAAC,GAAG,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC;YAAE,SAAS;QAC1C,MAAM,KAAK,GAAG,SAAS,CAAC,IAAI,CAC1B,CAAC,KAAK,EAAE,EAAE,CAAC,GAAG,CAAC,YAAY,KAAK,SAAS,IAAI,GAAG,CAAC,YAAY,CAAC,UAAU,CAAC,GAAG,KAAK,CAAC,GAAG,GAAG,GAAG,EAAE,CAAC,CAC/F,CAAC;QACF,MAAM,IAAI,GACR,GAAG,CAAC,YAAY,KAAK,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,QAAQ,CAAC,KAAK,CAAC,OAAO,EAAE,GAAG,CAAC,YAAY,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;QAC7G,QAAQ,CAAC,IAAI,CAAC;YACZ,QAAQ,EAAE,MAAM;YAChB,IAAI,EAAE,0BAA0B;YAChC,GAAG,CAAC,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,OAAO,EAAE,KAAK,CAAC,EAAE,EAAE,CAAC;YACrD,0EAA0E;YAC1E,yEAAyE;YACzE,wEAAwE;YACxE,2EAA2E;YAC3E,wEAAwE;YACxE,iCAAiC;YACjC,GAAG,CAAC,IAAI,KAAK,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,SAAS,EAAE,CAAC,EAAE,IAAI,EAAE,IAAI,EAAE,IAAI,EAAE,SAAkB,EAAE,CAAC,EAAE,CAAC;YACnF,OAAO,EAAE,CAAC,IAAI,KAAK,IAAI,CAAC,CAAC,CAAC,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,IAAI,KAAK,SAAS,CAAC,GAAG,CAAC,EAAE,CAAC;YACxE,OAAO,EACL,kBAAkB,IAAI,IAAI,oBAAoB,KAAK,SAAS,CAAC,GAAG,CAAC,qCAAqC;gBACtG,sGAAsG;gBACtG,wGAAwG;gBACxG,oCAAoC,MAAM,CAAC,GAAG,CAAC,OAAO,CAAC,EAAE;SAC5D,CAAC,CAAC;IACL,CAAC;IACD,OAAO,EAAE,IAAI,EAAE,SAAS,EAAE,QAAQ,EAAE,CAAC;AACvC,CAAC;AAED;;;;;;;;;;GAUG;AACH,SAAS,MAAM,CAAC,OAAe;IAC7B,IAAI,sEAAsE,CAAC,IAAI,CAAC,OAAO,CAAC,EAAE,CAAC;QACzF,OAAO,CACL,kGAAkG;YAClG,4CAA4C,CAC7C,CAAC;IACJ,CAAC;IACD,IAAI,uCAAuC,CAAC,IAAI,CAAC,OAAO,CAAC,EAAE,CAAC;QAC1D,OAAO,CACL,uGAAuG;YACvG,oGAAoG,CACrG,CAAC;IACJ,CAAC;IACD,OAAO,oGAAoG,CAAC;AAC9G,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,KAAK,UAAU,eAAe,CAC5B,KAAwB,EACxB,KAA8B;IAE9B,6EAA6E;IAC7E,8EAA8E;IAC9E,6EAA6E;IAC7E,4EAA4E;IAC5E,EAAE;IACF,yEAAyE;IACzE,0EAA0E;IAC1E,yEAAyE;IACzE,uEAAuE;IACvE,YAAY;IACZ,MAAM,UAAU,GAAG,MAAM,OAAO,CAAC,KAAK,EAAE,KAAK,EAAE,OAAO,EAAE,EAAE;QACxD,MAAM,KAAK,GAAG,MAAM,KAAK,CAAC,KAAK,CAAC,YAAY,CAAC,KAAK,CAAC,OAAO,EAAE,OAAO,CAAC,CAAC;QACrE,MAAM,MAAM,GAAG,CAAC,GAAG,KAAK,CAAC,GAAG,CAAC,MAAM,CAAC,CAAC;QACrC,IAAI,MAAM,CAAC,MAAM,GAAG,CAAC,IAAI,KAAK,CAAC,aAAa;YAAE,OAAO,MAAM,CAAC;QAC5D,yEAAyE;QACzE,4EAA4E;QAC5E,yEAAyE;QACzE,4DAA4D;QAC5D,IAAI,KAAK,CAAC,OAAO,KAAK,IAAI;YAAE,OAAO,EAAE,CAAC;QACtC,MAAM,KAAK,GAAG,MAAM,gBAAgB,CAAC;YACnC,KAAK,EAAE,OAAO;YACd,KAAK,EAAE,KAAK,CAAC,GAAG;YAChB,KAAK,EAAE,KAAK,CAAC,KAAK;YAClB,SAAS,EAAE,EAAE,OAAO,EAAE,KAAK,CAAC,OAAO,EAAE,OAAO,EAAE,KAAK,CAAC,OAAO,EAAE;SAC9D,CAAC,CAAC;QACH,OAAO,KAAK,CAAC,IAAI,KAAK,YAAY,CAAC,CAAC,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,CAAC;IACzD,CAAC,CAAC,CAAC;IACH,OAAO,IAAI,GAAG,CAAC,UAAU,CAAC,IAAI,EAAE,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAC,CAAC;AAClD,CAAC;AAED;;;;;;;;GAQG;AACH,SAAS,QAAQ,CAAC,GAAgB;IAChC,OAAO,IAAI,CAAC,SAAS,CAAC,CAAC,GAAG,CAAC,YAAY,IAAI,EAAE,EAAE,GAAG,CAAC,IAAI,IAAI,CAAC,CAAC,EAAE,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC;AAC/E,CAAC","sourcesContent":["/**\n * `c4.fleet-project-invalid` — the one thing no per-document grade can see:\n * every document loam reads is clean, and the project the RENDERER builds out of\n * them is not.\n *\n * loam grades a fleet document by document, and that is deliberate: a service's\n * model is graded on its own merits, and one broken model must not blank the\n * fleet. The renderer has no such rule. Point `npx likec4 start` at the docs\n * root and it merges every `.likec4` the root project reads into ONE model — the\n * map, every extending model, and every `.likec4` sitting beside one — so a\n * declaration made in two of those documents is a duplicate there and nowhere\n * else. Measured at the 1.59.2 pin: a tags-only `specification { tag req-X }` in\n * an extending model is legal, and the SAME tag declared in a second extending\n * model is a duplicate blamed on both files. Two services, two clean grades, and\n * a renderer that draws nothing.\n *\n * So this is one extra load, and it is the renderer's reading rather than\n * loam's. What it reports is the SET DIFFERENCE: an error already reported where\n * loam grades that document — the map's own parse, a per-service project's\n * `c4.invalid`, a service flow project's use-case failure — is not repeated\n * here, because the fix is one file either way and N copies of one cascade is\n * the report. What is left over is exactly the class above: errors that exist\n * only because these documents were merged.\n *\n * WHICH DOCUMENTS ARE IN IT is `./root-documents.ts`'s question, and it is a\n * walk of the docs root rather than a list of the shapes loam knows about: a\n * `.likec4` in a SUBSYSTEM directory — the parent of service directories — was\n * in none of the three roots this used to merge, and went unreported while the\n * renderer refused the whole project over it (verification 2026-09-04, R2). That\n * module also carries why the generated `architecture/subsystems.likec4`,\n * every standalone service directory and `features/` stay out.\n *\n * `--all` ONLY, and only when at least one model extends the map, the map itself\n * parses, and the root `exclude` does not hide it. A single-target run has not\n * enumerated the fleet, so it cannot build the project at all; a fleet whose\n * models all stand alone has no such project (every one of them is excluded from\n * the root); and a map that does not parse would report its own cascade here\n * under a second code while `landscape.invalid` already names the file.\n *\n * THE LAST OF THOSE GATES IS THE CASCADE RULE, the one `permissions.invalid` and\n * `capability.invalid` already state: a grade that resolves against a\n * document nobody loaded is not a diagnosis. `architectureProjectDocuments`\n * keeps the map whatever the root `exclude` says — that floor is what stopped\n * loam asserting a fleet's map declares nothing — but this load has no such\n * floor ON PURPOSE, because its whole claim is to read what the renderer reads.\n * So an entry covering `architecture/landscape.likec4` leaves every extending\n * model in the project with its `extend <fqn>` resolving against nothing:\n * measured on `examples/docs` with `architecture/*.likec4` in the list, one\n * authored line came back as 161 warnings under this code. `landscape.excluded`\n * (`./projects.ts`) is the one finding that names the cause, and it says the\n * fleet project is not graded until the entry goes. The fact arrives as\n * `mapExcluded` rather than being re-read here, so the two can never disagree\n * about which state they are in.\n *\n * WHY A WARNING. Nothing loam concludes changes: every model still parses where\n * loam reads it, every binding still resolves, the spine is unaffected. What is\n * broken is the picture, which is what `service.likec4-config-missing` and its\n * three siblings in `./projects.ts` also grade, at the same severity.\n */\nimport { existsSync } from \"node:fs\";\nimport { relative, resolve, sep } from \"node:path\";\nimport { errorText, type LikeC4Error, type LoadedDoc } from \"../../../../core/c4/likec4.js\";\nimport { asLoadedDoc, loadProject } from \"../../../../core/c4/project/load.js\";\nimport type { ViewIdClaim } from \"../../../../core/c4/parsed/view-ids.js\";\nimport type { ModelShape } from \"../../../../core/c4/service-model/shape.js\";\nimport { FleetContext } from \"../../../../core/fleet-context.js\";\nimport { inOrder } from \"../../../../core/kernel/concurrency.js\";\nimport type { DocsDir } from \"../../../../core/kernel/ids/dirs.js\";\nimport type { ServiceEntry } from \"../../../../core/repo/entries.js\";\nimport { servicePathsAt, type ServicePaths } from \"../../../../core/repo/paths.js\";\nimport type { FleetTree } from \"../../../../core/repo/tree/walk.js\";\nimport { readServiceFlows } from \"../../../../core/usecases/service/flows.js\";\nimport type { Finding } from \"../../../../core/vocabulary/report.js\";\nimport { rootProjectDocuments } from \"./root-documents.js\";\n\nexport interface FleetProjectCheck {\n  docsDir: DocsDir;\n  /** The FULL enumeration — the project the renderer builds holds every model, not a narrowed run's subset. */\n  entries: readonly ServiceEntry[];\n  /** Each model's shape, keyed by resolved path (`FleetContext.modelShapes`). */\n  shapes: ReadonlyMap<string, ModelShape>;\n  /** The run's read index: the per-service projects it already parsed are half of the set difference. */\n  fleet: FleetContext;\n  /** The map parsed ALONE — the gate, and the other half of the difference. */\n  architecture: LoadedDoc;\n  /**\n   * Whether the root `exclude` hides the map itself — `landscape.excluded`'s own\n   * condition, computed once in `./projects.ts` and carried here rather than\n   * re-derived. It is a GATE, for the reason the banner's cascade-rule paragraph\n   * gives: this load has no floor under the map, so the entry that hides it\n   * turns one authored line into an unresolved reference in every extending\n   * model.\n   */\n  mapExcluded: boolean;\n  /** The walked tree, for the view-id census this load makes answerable. */\n  tree: FleetTree;\n  /** Every service directory that exists — the flow scan's resolver evidence. */\n  known: ReadonlySet<string>;\n}\n\n/**\n * What the merged load found, as three answers rather than one list — because\n * the caller has a second question to ask of it and the answers are mutually\n * exclusive.\n *\n * `skipped` is \"there is no such project, or loam declines to read one\": no model\n * extends the map, the map does not parse, the root `exclude` hides the map\n * (`landscape.excluded` names that entry and this grade stands down behind it),\n * or the run has no fleet index. `clean` carries the view-id\n * CENSUS, which is the only thing a caller may take from a project that parsed —\n * and the reason this is not just an empty finding list: an empty list and a\n * clean census are the same thing to `.length`, and one of them licenses\n * `subsystem.view-id-collision` to be graded over every extending model's\n * authored ids while the other does not.\n */\nexport type FleetProjectGrade =\n  | { kind: \"skipped\" }\n  | { kind: \"invalid\"; findings: Finding[] }\n  | { kind: \"clean\"; viewIds: ViewIdClaim[] };\n\nexport async function fleetProjectFindings(check: FleetProjectCheck): Promise<FleetProjectGrade> {\n  // A map that did not parse is `landscape.invalid`'s, and this load would only\n  // repeat its cascade under a second code.\n  if (check.architecture.errors.length > 0) return { kind: \"skipped\" };\n  // A map the root `exclude` hides is `landscape.excluded`'s, for the same\n  // reason one line up — see the banner's cascade-rule paragraph. The view-id\n  // census goes with it: `clean` is a claim about a project that parsed, and\n  // there is none.\n  if (check.mapExcluded) return { kind: \"skipped\" };\n  const shapeOf = (entry: ServiceEntry): ModelShape | null => {\n    const model = servicePathsAt(entry.dir).model;\n    return existsSync(model) ? (check.shapes.get(resolve(model)) ?? null) : null;\n  };\n  const extending = check.entries.filter((entry) => shapeOf(entry) === \"extending\");\n  if (extending.length === 0) return { kind: \"skipped\" };\n\n  const paths = extending.map((entry) => servicePathsAt(entry.dir));\n  // The TREE, not three roots. `./root-documents.ts` carries what comes out of\n  // it and why; the standalone directories are handed in because their shape is\n  // this run's memo and re-reading every model here would be a second scanner.\n  const documents = await rootProjectDocuments(\n    check.docsDir,\n    check.entries.filter((entry) => shapeOf(entry) === \"standalone\").map((entry) => entry.dir),\n  );\n  const project = await loadProject(check.docsDir, documents);\n\n  if (project.clean) {\n    // The census `subsystem.view-id-collision` needs and could not have until\n    // now: an extending model's authored view ids live in the SAME flat\n    // namespace as the map's, because both documents are in this project. The\n    // claims arrive docs-relative, which is the spelling `viewIdFindings` takes.\n    return { kind: \"clean\", viewIds: project.viewIds };\n  }\n\n  const reported = await alreadyReported(check, paths);\n  const findings: Finding[] = [];\n  for (const err of asLoadedDoc(project).errors) {\n    if (reported.has(errorKey(err))) continue;\n    const owner = extending.find(\n      (entry) => err.sourceFsPath !== undefined && err.sourceFsPath.startsWith(`${entry.dir}${sep}`),\n    );\n    const file =\n      err.sourceFsPath === undefined ? null : relative(check.docsDir, err.sourceFsPath).split(/[\\\\/]/).join(\"/\");\n    findings.push({\n      severity: \"warn\",\n      code: \"c4.fleet-project-invalid\",\n      ...(owner === undefined ? {} : { subject: owner.id }),\n      // The file the error is IN, never the map by default: `locations[0].path`\n      // was `architecture/landscape.likec4` on every one of these, so a reader\n      // acting on the payload opened a document that was not the one at fault\n      // (verification 2026-09-04, D10). Absent when LikeC4 declined to attribute\n      // the error to a document at all — a location loam cannot spell is left\n      // unspelled rather than guessed.\n      ...(file === null ? {} : { locations: [{ path: file, role: \"primary\" as const }] }),\n      details: [file === null ? errorText(err) : `${file}: ${errorText(err)}`],\n      message:\n        `fleet project: ${file ?? \"the merged project\"}: ${errorText(err)} — each document reads clean where ` +\n        \"loam grades it, but the renderer merges every `.likec4` the root project reads except the generated \" +\n        \"subsystems.likec4 — the map, every extending model and every `.likec4` beside one — into ONE project, \" +\n        `and that project does not parse. ${remedy(err.message)}`,\n    });\n  }\n  return { kind: \"invalid\", findings };\n}\n\n/**\n * The tail that names WHICH failure this is.\n *\n * It used to say \"a tag or an element declared in two of those documents is\n * declared twice there\" for every error, including the ones that are not a\n * double declaration at all (verification 2026-09-04, D10) — an unresolved\n * reference sent its reader hunting for a second declaration that does not\n * exist. LikeC4's own wording is the evidence, matched loosely on purpose: an\n * unrecognised message falls to the third arm, which asserts nothing beyond\n * where to look.\n */\nfunction remedy(message: string): string {\n  if (/duplicat|already (declared|defined)|declared (more than once|twice)/i.test(message)) {\n    return (\n      \"A tag or an element declared in two of those documents is declared twice there; declare it once \" +\n      \"(the map, or the one service that owns it)\"\n    );\n  }\n  if (/could not resolve|unresolved|unknown/i.test(message)) {\n    return (\n      \"A name resolves against ALL of those documents here, so a reference the renderer cannot place is one \" +\n      \"no document in the project declares; declare it where the reader can see it, or drop the reference\"\n    );\n  }\n  return \"Open the file and line named above — every reader who points a renderer at the docs root sees this\";\n}\n\n/**\n * Every parse error this run has ALREADY reported against one of these\n * documents, keyed so the merged project's copy can be recognised.\n *\n * Two sources, and both are loads the run made anyway or would make: each\n * extending model's own per-service project (`c4.invalid` on the service\n * target) and, where nothing was wrong there, each service's FLOW project\n * (`readServiceFlows` — the use-case grade names the file). The flow read goes\n * through that function rather than a second `loadProject` here so the OPT-IN\n * gate is the same one: a broken sibling that nothing tagged is loaded by\n * neither, which is exactly why the merged project has to report it.\n *\n * Computed only when the merged project actually failed, which is why it is a\n * function rather than an input: on a healthy fleet this whole file costs one\n * load and nothing else.\n *\n * THE FLOW PROJECTS ARE PARSED AGAIN by `validateService` later in the same run,\n * and that is accepted rather than unnoticed: it happens only on the path where\n * the merged project already failed, so a healthy fleet pays nothing, and the\n * `ServiceModel` half above IS the run's memo. If that path ever becomes hot,\n * the follow-up is to memoise the flow scan on `FleetContext` beside the\n * per-service projects — not to hand the scan in here, which would make this\n * grade depend on an argument the caller has no reason to have loaded.\n */\nasync function alreadyReported(\n  check: FleetProjectCheck,\n  paths: readonly ServicePaths[],\n): Promise<ReadonlySet<string>> {\n  // Both sets reach the same documents through `architectureProjectDocuments`,\n  // which now drops what the root `exclude` covers exactly as the merged load's\n  // own walk does — so a document out of one is out of both, and the generated\n  // `subsystems.likec4` is out of all of them without being remembered twice.\n  //\n  // Pooled rather than awaited one at a time: each entry is an independent\n  // LikeC4 workspace over one service's own documents, which is exactly the\n  // work `inOrder` rations — and a serial loop here made the ONE path that\n  // already costs a fleet its whole set of flow projects pay for them in\n  // sequence.\n  const perService = await inOrder(paths, async (service) => {\n    const model = await check.fleet.serviceModel(check.docsDir, service);\n    const errors = [...model.doc.errors];\n    if (errors.length > 0 || model.mapUnreadable) return errors;\n    // `model.project` is non-null here by construction — these are extending\n    // models whose own load came back clean, which is the arm that carries it —\n    // and the guard is the compiler's rather than an assertion: a null would\n    // mean grading a flow against a document that did not load.\n    if (model.project === null) return [];\n    const flows = await readServiceFlows({\n      paths: service,\n      model: model.doc,\n      known: check.known,\n      extending: { docsDir: check.docsDir, project: model.project },\n    });\n    return flows.kind === \"unreadable\" ? flows.errors : [];\n  });\n  return new Set(perService.flat().map(errorKey));\n}\n\n/**\n * One error's identity across two loads of overlapping document sets: the real\n * file, the line, and the message.\n *\n * There is no id to join on — LikeC4 mints diagnostics per parse — and the\n * message has to be part of the key: two DIFFERENT problems on one line of one\n * file are two errors, and collapsing them would let a merged-project-only\n * failure hide behind a per-service one that happens to share a line.\n */\nfunction errorKey(err: LikeC4Error): string {\n  return JSON.stringify([err.sourceFsPath ?? \"\", err.line ?? -1, err.message]);\n}\n"]}

package/dist/commands/validate/fleet/views/ids.js

@@ -1,10 +1,10 @@
 import { SUBSYSTEM_VIEW_PREFIX, subsystemViewId } from "../../../../core/repo/tree/render/views.js";
 /**
- * `authored` is every view id the `architecture/` project claims, each with the
- * file that claims it — static views included, because a static view claims an
- * id exactly as firmly as a dynamic one. Absent (the document did not parse, or
- * an older loader did not read them) is treated as "nothing to compare", never
- * as "nothing collides".
+ * `authored` is every view id the project claims, each with the DOCS-RELATIVE
+ * path of the file that claims it — static views included, because a static view
+ * claims an id exactly as firmly as a dynamic one. Absent (the document did not
+ * parse, or an older loader did not read them) is treated as "nothing to
+ * compare", never as "nothing collides".
  */
 export function viewIdFindings(authored, tree) {
     if (authored === undefined || authored.length === 0)
@@ -32,11 +32,15 @@ export function viewIdFindings(authored, tree) {
             // the one the report's target fallback gets wrong: it files this under
             // the landscape, which is exactly the file a reader must NOT rename the
             // view in when the claim came from a document of their own.
-            locations: [{ path: `architecture/${file}`, role: "primary" }],
-            message: `subsystems: architecture/${file} declares \`view ${id}\`, which is the id loam generates ` +
+            locations: [{ path: file, role: "primary" }],
+            message: `subsystems: ${file} declares \`view ${id}\`, which is the id loam generates ` +
                 `into architecture/subsystems.likec4 for services/${owner}/ — LikeC4 merges both files into one project, ` +
-                `so it refuses the whole architecture/ project and renders nothing. ` +
-                `Rename the view in architecture/${file}; ids beginning \`${SUBSYSTEM_VIEW_PREFIX}\` are loam's ` +
+                // The ROOT project, not `architecture/`: the claimant may be a model's
+                // own view now (an extending model is a document of the root project),
+                // and telling that author the `architecture/` project is refused sends
+                // them to look for the breakage in a directory they never touched.
+                `so it refuses the whole root project and renders nothing. ` +
+                `Rename the view in ${file}; ids beginning \`${SUBSYSTEM_VIEW_PREFIX}\` are loam's ` +
                 "to mint, and architecture/subsystems.likec4 is generated (`loam subsystem sync`) and must never be hand-edited.",
         });
     }

package/dist/commands/validate/fleet/views/ids.js.map

@@ -1 +1 @@
-{"version":3,"file":"ids.js","sourceRoot":"","sources":["../../../../../src/commands/validate/fleet/views/ids.ts"],"names":[],"mappings":"AAsCA,OAAO,EAAE,qBAAqB,EAAE,eAAe,EAAE,MAAM,4CAA4C,CAAC;AAIpG;;;;;;GAMG;AACH,MAAM,UAAU,cAAc,CAAC,QAAmC,EAAE,IAAe;IACjF,IAAI,QAAQ,KAAK,SAAS,IAAI,QAAQ,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,EAAE,CAAC;IAC/D,MAAM,SAAS,GAAG,IAAI,GAAG,CAAC,IAAI,CAAC,UAAU,CAAC,GAAG,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,CAAC,eAAe,CAAC,GAAG,CAAC,EAAE,GAAG,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC;IACpG,MAAM,QAAQ,GAAc,EAAE,CAAC;IAC/B,2EAA2E;IAC3E,8EAA8E;IAC9E,+EAA+E;IAC/E,2EAA2E;IAC3E,iDAAiD;IACjD,MAAM,SAAS,GAAG,IAAI,GAAG,EAAkB,CAAC;IAC5C,KAAK,MAAM,KAAK,IAAI,QAAQ;QAAE,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAC;YAAE,SAAS,CAAC,GAAG,CAAC,KAAK,CAAC,EAAE,EAAE,KAAK,CAAC,UAAU,CAAC,CAAC;IACtG,KAAK,MAAM,CAAC,EAAE,EAAE,IAAI,CAAC,IAAI,CAAC,GAAG,SAAS,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;QAC7E,MAAM,KAAK,GAAG,SAAS,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;QAChC,IAAI,KAAK,KAAK,SAAS;YAAE,SAAS;QAClC,QAAQ,CAAC,IAAI,CAAC;YACZ,QAAQ,EAAE,OAAO;YACjB,IAAI,EAAE,6BAA6B;YACnC,OAAO,EAAE,EAAE;YACX,wEAAwE;YACxE,uEAAuE;YACvE,wEAAwE;YACxE,4DAA4D;YAC5D,SAAS,EAAE,CAAC,EAAE,IAAI,EAAE,gBAAgB,IAAI,EAAE,EAAE,IAAI,EAAE,SAAkB,EAAE,CAAC;YACvE,OAAO,EACL,4BAA4B,IAAI,oBAAoB,EAAE,qCAAqC;gBAC3F,oDAAoD,KAAK,iDAAiD;gBAC1G,qEAAqE;gBACrE,mCAAmC,IAAI,qBAAqB,qBAAqB,gBAAgB;gBACjG,iHAAiH;SACpH,CAAC,CAAC;IACL,CAAC;IACD,OAAO,QAAQ,CAAC;AAClB,CAAC","sourcesContent":["/**\n * An authored view id that collides with one loam GENERATES into\n * `architecture/subsystems.likec4`.\n *\n * This closes a green-while-broken hole, and the shape of it is measured rather\n * than argued. The LikeC4 renderer merges every `.likec4` file in a project into\n * one model, and `likec4.config.json` scopes the root project to\n * `architecture/` — so `landscape.likec4` and the generated `subsystems.likec4`\n * share ONE flat view-id namespace. Author `view subsystem_commerce { }` in the\n * landscape while the tree has a `commerce` subsystem and the renderer refuses\n * the ENTIRE `architecture/` project with two `Duplicate view` diagnostics, one\n * per file — while `loam validate --all` printed `landscape: N service(s)\n * modelled — architecture/landscape.likec4 and services/ agree`. Reproduced at\n * the 1.59.2 pin.\n *\n * Nothing else in a loam repo can produce this. A duplicate INSIDE one document\n * is already 2 LikeC4 errors, so `landscape.invalid` has it (measured). A\n * service's `model.likec4` and a feature's `delta.likec4` are each their own\n * LikeC4 project — `likec4.config.json` excludes `services/**` and\n * `features/**` from the root — so their view ids cannot collide with the\n * landscape's, and a delta's views never travel through `archive` anyway. That\n * leaves exactly one pair, which is why this check compares exactly one pair\n * rather than taking a census across every document loam parses.\n *\n * ONLY the real collision is refused, never the merely reserved-looking name.\n * A landscape view called `subsystem_overview` with no `overview` subsystem\n * breaks nothing today, and refusing it would be loam inventing a rule about a\n * name that harms no one. The latent case is not lost: the moment somebody\n * creates that subsystem, the generator mints the id, and this same check fires\n * on the same run. The message names the reservation anyway, so an author fixing\n * one collision learns not to make the next.\n *\n * Graded on `validate --all` only, and the caller holds that gate together with\n * the landscape-parsed one: under a single-target run the fleet tree is not\n * walked and the generated ids are unknown, so the question is unanswerable and\n * the check stays silent rather than half-answering.\n */\nimport type { ViewIdClaim } from \"../../../../core/c4/parsed/view-ids.js\";\nimport { SUBSYSTEM_VIEW_PREFIX, subsystemViewId } from \"../../../../core/repo/tree/render/views.js\";\nimport type { FleetTree } from \"../../../../core/repo/tree/walk.js\";\nimport type { Finding } from \"../../../../core/vocabulary/report.js\";\n\n/**\n * `authored` is every view id the `architecture/` project claims, each with the\n * file that claims it — static views included, because a static view claims an\n * id exactly as firmly as a dynamic one. Absent (the document did not parse, or\n * an older loader did not read them) is treated as \"nothing to compare\", never\n * as \"nothing collides\".\n */\nexport function viewIdFindings(authored: ViewIdClaim[] | undefined, tree: FleetTree): Finding[] {\n  if (authored === undefined || authored.length === 0) return [];\n  const generated = new Map(tree.subsystems.map((sub) => [subsystemViewId(sub), sub.path.join(\"/\")]));\n  const findings: Finding[] = [];\n  // Sorted and de-duplicated by id so a project claiming the same id twice —\n  // itself already a parse error, but reachable through a partial read — yields\n  // one finding per id rather than one per occurrence. The first claimant's file\n  // is the one named: with a duplicate the project does not parse at all, so\n  // there is never a second one to choose between.\n  const claimants = new Map<string, string>();\n  for (const claim of authored) if (!claimants.has(claim.id)) claimants.set(claim.id, claim.sourcePath);\n  for (const [id, file] of [...claimants].sort(([a], [b]) => (a < b ? -1 : 1))) {\n    const owner = generated.get(id);\n    if (owner === undefined) continue;\n    findings.push({\n      severity: \"error\",\n      code: \"subsystem.view-id-collision\",\n      subject: id,\n      // The CLAIMANT file — the one the message tells the reader to edit, and\n      // the one the report's target fallback gets wrong: it files this under\n      // the landscape, which is exactly the file a reader must NOT rename the\n      // view in when the claim came from a document of their own.\n      locations: [{ path: `architecture/${file}`, role: \"primary\" as const }],\n      message:\n        `subsystems: architecture/${file} declares \\`view ${id}\\`, which is the id loam generates ` +\n        `into architecture/subsystems.likec4 for services/${owner}/ — LikeC4 merges both files into one project, ` +\n        `so it refuses the whole architecture/ project and renders nothing. ` +\n        `Rename the view in architecture/${file}; ids beginning \\`${SUBSYSTEM_VIEW_PREFIX}\\` are loam's ` +\n        \"to mint, and architecture/subsystems.likec4 is generated (`loam subsystem sync`) and must never be hand-edited.\",\n    });\n  }\n  return findings;\n}\n"]}
+{"version":3,"file":"ids.js","sourceRoot":"","sources":["../../../../../src/commands/validate/fleet/views/ids.ts"],"names":[],"mappings":"AAqDA,OAAO,EAAE,qBAAqB,EAAE,eAAe,EAAE,MAAM,4CAA4C,CAAC;AAIpG;;;;;;GAMG;AACH,MAAM,UAAU,cAAc,CAAC,QAAmC,EAAE,IAAe;IACjF,IAAI,QAAQ,KAAK,SAAS,IAAI,QAAQ,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,EAAE,CAAC;IAC/D,MAAM,SAAS,GAAG,IAAI,GAAG,CAAC,IAAI,CAAC,UAAU,CAAC,GAAG,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,CAAC,eAAe,CAAC,GAAG,CAAC,EAAE,GAAG,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC;IACpG,MAAM,QAAQ,GAAc,EAAE,CAAC;IAC/B,2EAA2E;IAC3E,8EAA8E;IAC9E,+EAA+E;IAC/E,2EAA2E;IAC3E,iDAAiD;IACjD,MAAM,SAAS,GAAG,IAAI,GAAG,EAAkB,CAAC;IAC5C,KAAK,MAAM,KAAK,IAAI,QAAQ;QAAE,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAC;YAAE,SAAS,CAAC,GAAG,CAAC,KAAK,CAAC,EAAE,EAAE,KAAK,CAAC,UAAU,CAAC,CAAC;IACtG,KAAK,MAAM,CAAC,EAAE,EAAE,IAAI,CAAC,IAAI,CAAC,GAAG,SAAS,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;QAC7E,MAAM,KAAK,GAAG,SAAS,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;QAChC,IAAI,KAAK,KAAK,SAAS;YAAE,SAAS;QAClC,QAAQ,CAAC,IAAI,CAAC;YACZ,QAAQ,EAAE,OAAO;YACjB,IAAI,EAAE,6BAA6B;YACnC,OAAO,EAAE,EAAE;YACX,wEAAwE;YACxE,uEAAuE;YACvE,wEAAwE;YACxE,4DAA4D;YAC5D,SAAS,EAAE,CAAC,EAAE,IAAI,EAAE,IAAI,EAAE,IAAI,EAAE,SAAkB,EAAE,CAAC;YACrD,OAAO,EACL,eAAe,IAAI,oBAAoB,EAAE,qCAAqC;gBAC9E,oDAAoD,KAAK,iDAAiD;gBAC1G,uEAAuE;gBACvE,uEAAuE;gBACvE,uEAAuE;gBACvE,mEAAmE;gBACnE,4DAA4D;gBAC5D,sBAAsB,IAAI,qBAAqB,qBAAqB,gBAAgB;gBACpF,iHAAiH;SACpH,CAAC,CAAC;IACL,CAAC;IACD,OAAO,QAAQ,CAAC;AAClB,CAAC","sourcesContent":["/**\n * An authored view id that collides with one loam GENERATES into\n * `architecture/subsystems.likec4`.\n *\n * This closes a green-while-broken hole, and the shape of it is measured rather\n * than argued. The LikeC4 renderer merges every `.likec4` file in a project into\n * one model, and `architecture/landscape.likec4` and the generated\n * `architecture/subsystems.likec4` are two documents of the ROOT project — so\n * they share ONE flat view-id namespace. (This file used to say the reason was\n * that `likec4.config.json` scopes the root project to `architecture/`; it does\n * not, and never had to for the collision to exist. The scaffold's `exclude`\n * names `features/**` and node_modules, and a fleet whose models extend the map\n * has `services/` in the root project too — see `./fleet-project.ts`.) Author\n * `view subsystem_commerce { }` in the landscape while the tree has a `commerce`\n * subsystem and the renderer refuses the ENTIRE root project with two\n * `Duplicate view` diagnostics, one per file — while `loam validate --all`\n * printed `landscape: N service(s) modelled — architecture/landscape.likec4 and\n * services/ agree`. Reproduced at the 1.59.2 pin.\n *\n * WHICH DOCUMENTS CLAIM IDS IN THAT NAMESPACE, corrected. A duplicate INSIDE one\n * document is already 2 LikeC4 errors, so `landscape.invalid` has it (measured).\n * A feature's `delta.likec4` is its own LikeC4 project — the root excludes\n * `features/**` — and a delta's views never travel through `archive` anyway. A\n * service's `model.likec4` used to be in the same position and no longer is:\n * this file's original premise, that `likec4.config.json` excludes `services/**`\n * so a model's view ids cannot collide with the landscape's, holds only for a\n * model that STANDS ALONE. A model that EXTENDS the map lives in the root\n * project beside it, so its authored view ids — and those of every `.likec4`\n * beside it — share exactly this namespace. That census is made by the merged\n * load in `./fleet-project.ts` and handed here; the landscape's own claims are\n * still graded from the `architecture/` project, which is the only census a run\n * with no extending model can make.\n *\n * The claims therefore arrive spelled DOCS-RELATIVE, and the caller does the\n * spelling: the `architecture/` project reports a view's `sourcePath` relative\n * to `architecture/`, the merged project reports it relative to the docs root,\n * and a prefix pasted on here would name `architecture/services/…` for every\n * model. The message and the location both print the path verbatim.\n *\n * ONLY the real collision is refused, never the merely reserved-looking name.\n * A landscape view called `subsystem_overview` with no `overview` subsystem\n * breaks nothing today, and refusing it would be loam inventing a rule about a\n * name that harms no one. The latent case is not lost: the moment somebody\n * creates that subsystem, the generator mints the id, and this same check fires\n * on the same run. The message names the reservation anyway, so an author fixing\n * one collision learns not to make the next.\n *\n * Graded on `validate --all` only, and the caller holds that gate together with\n * the landscape-parsed one: under a single-target run the fleet tree is not\n * walked and the generated ids are unknown, so the question is unanswerable and\n * the check stays silent rather than half-answering.\n */\nimport type { ViewIdClaim } from \"../../../../core/c4/parsed/view-ids.js\";\nimport { SUBSYSTEM_VIEW_PREFIX, subsystemViewId } from \"../../../../core/repo/tree/render/views.js\";\nimport type { FleetTree } from \"../../../../core/repo/tree/walk.js\";\nimport type { Finding } from \"../../../../core/vocabulary/report.js\";\n\n/**\n * `authored` is every view id the project claims, each with the DOCS-RELATIVE\n * path of the file that claims it — static views included, because a static view\n * claims an id exactly as firmly as a dynamic one. Absent (the document did not\n * parse, or an older loader did not read them) is treated as \"nothing to\n * compare\", never as \"nothing collides\".\n */\nexport function viewIdFindings(authored: ViewIdClaim[] | undefined, tree: FleetTree): Finding[] {\n  if (authored === undefined || authored.length === 0) return [];\n  const generated = new Map(tree.subsystems.map((sub) => [subsystemViewId(sub), sub.path.join(\"/\")]));\n  const findings: Finding[] = [];\n  // Sorted and de-duplicated by id so a project claiming the same id twice —\n  // itself already a parse error, but reachable through a partial read — yields\n  // one finding per id rather than one per occurrence. The first claimant's file\n  // is the one named: with a duplicate the project does not parse at all, so\n  // there is never a second one to choose between.\n  const claimants = new Map<string, string>();\n  for (const claim of authored) if (!claimants.has(claim.id)) claimants.set(claim.id, claim.sourcePath);\n  for (const [id, file] of [...claimants].sort(([a], [b]) => (a < b ? -1 : 1))) {\n    const owner = generated.get(id);\n    if (owner === undefined) continue;\n    findings.push({\n      severity: \"error\",\n      code: \"subsystem.view-id-collision\",\n      subject: id,\n      // The CLAIMANT file — the one the message tells the reader to edit, and\n      // the one the report's target fallback gets wrong: it files this under\n      // the landscape, which is exactly the file a reader must NOT rename the\n      // view in when the claim came from a document of their own.\n      locations: [{ path: file, role: \"primary\" as const }],\n      message:\n        `subsystems: ${file} declares \\`view ${id}\\`, which is the id loam generates ` +\n        `into architecture/subsystems.likec4 for services/${owner}/ — LikeC4 merges both files into one project, ` +\n        // The ROOT project, not `architecture/`: the claimant may be a model's\n        // own view now (an extending model is a document of the root project),\n        // and telling that author the `architecture/` project is refused sends\n        // them to look for the breakage in a directory they never touched.\n        `so it refuses the whole root project and renders nothing. ` +\n        `Rename the view in ${file}; ids beginning \\`${SUBSYSTEM_VIEW_PREFIX}\\` are loam's ` +\n        \"to mint, and architecture/subsystems.likec4 is generated (`loam subsystem sync`) and must never be hand-edited.\",\n    });\n  }\n  return findings;\n}\n"]}

package/dist/commands/validate/fleet/views/projects.js

@@ -0,0 +1,278 @@
+/**
+ * The four ways a service's `model.likec4` and the renderer's project files can
+ * disagree, graded as one warning per service on the fleet target — plus the
+ * one way the same root config can hide the fleet MAP, graded once for the
+ * fleet (`landscape.excluded`, at the foot of this module).
+ *
+ * They are one walk because they are one question — "can the renderer actually
+ * show what this model says?" — asked of the two shapes a model has. A model
+ * that STANDS ALONE (declares its own element kinds) is parsed alone: it needs a
+ * project file of its own, and the root project must exclude its directory. A
+ * model that EXTENDS the fleet map declares no kinds and lives IN the root
+ * project: it must NOT be excluded, and a project file beside it TAKES it out of
+ * there — measured at the 1.59.2 pin, the nested project claims the model, which
+ * then does not resolve (the map's kinds are not in there with it) and the fleet
+ * project loses the service's interior. Each shape therefore owes the opposite of
+ * the other, and each of the four codes below is one half of one of those pairs:
+ *
+ *  - `service.likec4-config-missing` — standalone, no project file.
+ *  - `service.likec4-config-stray`   — extending, project file present.
+ *  - `service.model-excluded`        — extending, root `exclude` covers it. Two
+ *    questions, not one: the DIRECTORY (`excludingEntry`, which `subsystem sync`
+ *    can repair) and, where that says no, the model FILE (`excludingPath`, which
+ *    it cannot — the message says so).
+ *  - `service.model-unexcluded`      — standalone, root `exclude` does not.
+ *
+ * `landscape.excluded` is the fifth, and it is the same question asked one
+ * level up: the root `exclude` covering `architecture/landscape.likec4` itself.
+ *
+ * WHY WARNINGS. Every fact loam grades about a model — its parse, its bindings,
+ * its edges into the spine — holds exactly as it did in all five states, so
+ * nothing here may gate. The fifth is only true because the architecture loader
+ * keeps the map whatever the root `exclude` says (`core/c4/project/architecture.ts`);
+ * before it did, an excluded map blanked every cross-service grade in the run. ROADMAP's clause that rendering "must stay outside
+ * validation so view computation cannot slow or change the gate" is about
+ * computing views; this check computes nothing: one `existsSync` per service and
+ * one read of the root config. And the sibling that grades the ROOT file's
+ * absence (`doctor.likec4-config-missing`, `core/doctor/doctor.ts`) calls a repo
+ * without it "only unrenderable" and warns; these are the same condition one
+ * directory down and earn the same severity.
+ *
+ * WHY `validate --all` AND NOT `doctor`. `doctor` is the step-0 preflight of the
+ * adopt protocol — wiring, the config, the fleet map's readability — and the
+ * protocol's step 5 is the `validate --all` run whose findings the agent
+ * branches on. The report that motivated the first of these codes had its own
+ * `doctor --json` answer `healthy: true` with 0 findings on a tree where every
+ * adopted model was unrenderable from the root: the model is written in step 3,
+ * so its renderability is a fact that first exists at step 5, and a preflight
+ * that ran before the model did could not have said otherwise. Never in
+ * `validate --service`, `status` or `doctor`: the writer is a fleet verb
+ * (`subsystem sync`) and the findings belong beside the files that verb owns.
+ *
+ * WHY PER SERVICE. `subject` is the service id so a `--json` worklist filters by
+ * team the way `landscape.service-unmodelled` already lets it — one fleet
+ * finding listing every gap would have to be re-parsed to find out whose it is.
+ * The `scope` location is the service's tree path, through `serviceTreePath` on
+ * the ENTRY the survey hands back — never a join by id: these grades are emitted
+ * before the map's early returns precisely so they hold on a broken tree, and a
+ * tree with two services sharing a leaf name under different subsystems
+ * (`subsystem.name-collision`) is exactly such a tree, still enumerated in full.
+ * Joined by id, both findings named the first directory while `subsystem sync`
+ * wrote both files at the right paths.
+ *
+ * WHY THE ROOT GATE, and it does double duty. Semantically: `subsystem sync`
+ * writes nothing — no per-service file, no rewritten `exclude` — until the root
+ * `likec4.config.json` exists (the docs root is then a LikeC4 workspace and a
+ * nested project is registered inside it — measured at the 1.59.2 pin), so a
+ * repo without the root file has `doctor` telling it to write that first and
+ * nothing to sync into; grading a gap the writer would not fill is a loop no
+ * command can clear. The same rule silences a directory whose name is not a
+ * legal service id: the survey skips it (`render/projects.ts` says why),
+ * `service.id-invalid` already names it, and a warning here would advertise a
+ * repair `sync` refuses to perform. Fixture-wise: `makeProject` writes NO root
+ * file, so every existing fixture stays silent under this gate, and the suites
+ * that pin a fleet's warning set exactly (`test/examples.test.ts`,
+ * `test/self-model.test.ts`) ship the files their shapes call for and keep their
+ * counts.
+ *
+ * The exclude half has a SECOND gate, inside `readRootExclude`: a root config
+ * loam cannot read an `exclude` list out of answers `null`, and both grades that
+ * read it stay silent. loam does not know what the renderer will do with a file
+ * it could not parse, and asserting an exclusion on evidence it does not have is
+ * worse than saying nothing.
+ */
+import { existsSync } from "node:fs";
+import { relative, resolve } from "node:path";
+import { excludingEntry, excludingPath, readRootExclude } from "../../../../core/c4/root-project/exclude.js";
+import { serviceTreePath } from "../../../../core/kernel/ids/dirs.js";
+import { ARTIFACT_FILES, landscapePath, LIKEC4_PROJECT_FILENAME, rootProjectPath, serviceRenderPaths } from "../../../../core/repo/paths.js";
+import { surveyProjects } from "../../../../core/repo/tree/render/projects.js";
+/**
+ * `entries` is the fleet enumeration at whatever depth each service lives, and
+ * `shapes` is the shape of every model in it, keyed by resolved path
+ * (`FleetContext.modelShapes`). The shape map is built over the FULL enumeration
+ * rather than a `--base` narrowing: a model missing from it would read as
+ * standalone, which is the wrong half of every pair above.
+ *
+ * The predicate handed into the survey is the ONE spelling of "has a model,
+ * lacks a project file" that `subsystem sync` also fills, so the grader can
+ * never name a gap the writer would leave.
+ */
+export async function projectFindings(docsDir, entries, shapes) {
+    // No root project file, no root project — and no `exclude` list either, so the
+    // map is not excluded by anything loam can see. `false` here is a fact, not a
+    // default: `readRootExclude` would answer `null` one line down and every grade
+    // below it stays silent for the same reason.
+    if (!existsSync(rootProjectPath(docsDir)))
+        return { findings: [], mapExcluded: false };
+    const survey = surveyProjects(entries, serviceRenderPaths, (model) => shapes.get(resolve(model)) !== "extending");
+    const exclude = await readRootExclude(docsDir);
+    const findings = [];
+    // The ONE derivation. The boolean is read off the finding rather than computed
+    // beside it, so a fleet where `c4.fleet-project-invalid` is suspended is by
+    // construction a fleet where `landscape.excluded` says why.
+    const excluded = mapExcluded(docsDir, exclude);
+    findings.push(...excluded);
+    for (const model of survey.models) {
+        const tree = serviceTreePath(model.service);
+        // Everything the four share, so each push below is its code and its
+        // sentence and nothing else. `scope`, not `primary`: two of the four are
+        // about a file that does not exist yet, and the actionable place is the
+        // directory either way.
+        const at = {
+            severity: "warn",
+            subject: model.service.id,
+            locations: [{ path: tree, role: "scope" }],
+        };
+        if (model.standalone && !model.configured) {
+            findings.push({
+                ...at,
+                code: "service.likec4-config-missing",
+                message: `${model.service.id}: ${tree}/${ARTIFACT_FILES.model} exists and ${tree}/${LIKEC4_PROJECT_FILENAME} does not — ` +
+                    "a model that stands alone (declares its own `specification`) renders only as a project of its own, " +
+                    "and nothing renders it from the docs root now. Run `loam subsystem sync`; it writes the file (create-only) — never write it by hand.",
+            });
+        }
+        if (!model.standalone && model.configured) {
+            findings.push({
+                ...at,
+                code: "service.likec4-config-stray",
+                message: `${model.service.id}: ${tree}/${ARTIFACT_FILES.model} extends the fleet map and ${tree}/${LIKEC4_PROJECT_FILENAME} ` +
+                    "sits beside it — the renderer registers that file as a project of its own rooted at that directory, so " +
+                    "the docs root stops being a one-project workspace (`likec4 validate .` then refuses without `--project`), " +
+                    "and wherever that nested project claims the model it parses alone, out of the root project where the " +
+                    "map's kinds are: the model does not resolve and `export json --project fleet` loses this service's " +
+                    "containers (measured, likec4 1.59.2 — which of the two happens depends on the workspace, and neither is " +
+                    "a state this file buys anything in). Run `loam subsystem sync`; it deletes the file (or delete it " +
+                    "yourself). loam never writes one beside an extending model",
+            });
+        }
+        // `excludingEntry` reports the entry VERBATIM because the repair is to
+        // delete or narrow THAT line, and a fleet that files its services under
+        // subsystems is excluded by `services/platform/**` rather than by anything
+        // naming the service — a message that did not quote the entry would send
+        // its reader looking for a line that is not there.
+        const entry = exclude === null ? null : excludingEntry(exclude, tree);
+        // THE SECOND QUESTION, and the state that was silent until it was asked:
+        // an entry shaped like a FILE hides the model without covering the
+        // directory. `services/**/model.likec4` and the bare `**/model.likec4` each
+        // took every extending model out of the renderer on `examples/docs` — 3
+        // source files of 8, five drill-down views gone from the export — with the
+        // whole run reporting 0 errors and not one line containing the word
+        // "exclude" (re-verification 2026-09-04, area C item 5). It is asked ONLY
+        // where the directory question said no, because that arm names an entry
+        // `subsystem sync` can take back and this one names an entry it cannot.
+        const fileEntry = exclude === null || entry !== null ? null : excludingPath(exclude, `${tree}/${ARTIFACT_FILES.model}`);
+        const hiding = entry ?? fileEntry;
+        if (exclude !== null && !model.standalone && hiding !== null) {
+            findings.push({
+                ...at,
+                code: "service.model-excluded",
+                message: `${model.service.id}: ${tree}/${ARTIFACT_FILES.model} extends the fleet map and the root ` +
+                    `${LIKEC4_PROJECT_FILENAME} excludes it ('${hiding}') — the renderer never loads it, so the service is ` +
+                    "a box with nothing inside it from the docs root. " +
+                    (entry === null
+                        ? // The repair is an EDIT, not a command, and saying otherwise is the
+                            // loop `landscape.excluded` already refuses to open: sync recomputes
+                            // only the `services/<tree>/**` entries and would report success
+                            // having changed nothing.
+                            "That entry hides the model file without covering " +
+                                `${tree}/, so \`loam subsystem sync\` cannot repair it: sync maintains only the ` +
+                                "`services/` directory entries and leaves every other line exactly as the team wrote it. Narrow that " +
+                                "entry to the paths it was written for, or delete it"
+                        : "Run `loam subsystem sync`: it rewrites the root project's `exclude` to cover exactly the models " +
+                            "that stand alone"),
+            });
+        }
+        if (exclude !== null && model.standalone && entry === null) {
+            findings.push({
+                ...at,
+                code: "service.model-unexcluded",
+                message: `${model.service.id}: ${tree}/${ARTIFACT_FILES.model} stands alone (declares its own specification) and ` +
+                    `the root ${LIKEC4_PROJECT_FILENAME} does not exclude ${tree}/ — the renderer merges it into the map ` +
+                    "and reports every kind and element it declares as a duplicate, blanking the whole root project. " +
+                    `Run \`loam subsystem sync\`: it adds ${tree}/** to the root project's \`exclude\``,
+            });
+        }
+    }
+    return { findings, mapExcluded: excluded.length > 0 };
+}
+/**
+ * `landscape.excluded` — the root `exclude` covers the fleet MAP itself.
+ *
+ * WHY IT EXISTS AT ALL, and why only now. The architecture loader used to apply
+ * the root `exclude` with no floor under it, so an entry covering
+ * `architecture/landscape.likec4` — an `architecture/*.likec4` written for a
+ * palette, say — left that project EMPTY, and an empty project parses with zero
+ * errors. Every reader downstream took that for "the map declares nothing":
+ * `landscape.service-unmodelled` on every service, `c4.invalid` on every
+ * extending model, `subsystem sync` cutting a good generated file back to a
+ * title (verification 2026-09-04, review C). The loader now keeps the map
+ * whatever the list says, so loam has stopped asserting those falsehoods — but
+ * the RENDERER still applies the entry, and it has no floor. Nothing told the
+ * author that the fleet map they are grading is a map nobody can open. This is
+ * that sentence, and it is the only finding in the run that names it.
+ *
+ * WARN, NEVER GATING, for the reason the module banner gives: with the loader's
+ * floor in place, every fact loam grades holds identically either way. The gap
+ * is a renderer gap, exactly like the four per-service grades above.
+ *
+ * THE SAME ROOT GATE covers it — the caller returns early with no root
+ * `likec4.config.json`, and a config loam cannot read an `exclude` list out of
+ * answers `null`, which says nothing rather than guessing. It is gated on the
+ * map EXISTING as well: with no file there, `landscape.missing` is the finding
+ * and an entry covering a path nobody wrote is not a repair anyone owes.
+ *
+ * `excludingPath`, not `excludingEntry`: the map is a FILE, and this must fire
+ * exactly when `architectureProjectDocuments` would have dropped it — same
+ * list, same matcher, same argument. Asking the directory question instead
+ * would answer for `architecture/` as a whole and miss `architecture/*.likec4`,
+ * which is the spelling that caused the defect.
+ *
+ * The repair is NOT `loam subsystem sync`, and the message says so where the
+ * four grades above name it: sync recomputes only the `services/<tree>/**`
+ * entries and leaves every other line in the order the team wrote it, so it
+ * would report success and change nothing. The four had a writer; this one has
+ * an author.
+ *
+ * AND IT SUSPENDS `c4.fleet-project-invalid`, which is the cascade discipline
+ * `permissions.invalid` and `capability.invalid` already state: a grade that
+ * RESOLVES against a document nobody loaded is not a diagnosis. That check
+ * builds the fleet project the way the renderer does — no floor under the map —
+ * so the very entry named here takes the map out of it and every `extend` in
+ * every extending model then resolves against nothing. Measured on
+ * `examples/docs` with `architecture/*.likec4` in the list: one
+ * `landscape.excluded` and **161** `c4.fleet-project-invalid`, all of them one
+ * line's fault. The message carries that clause so the reader knows the fleet
+ * project is unread rather than clean, and the caller reads the same fact off
+ * `ProjectGrade.mapExcluded` — see `./fleet-project.ts`'s `mapExcluded` gate.
+ */
+function mapExcluded(docsDir, exclude) {
+    const map = landscapePath(docsDir);
+    if (exclude === null || !existsSync(map))
+        return [];
+    const rel = relative(docsDir, map).split(/[\\/]/).join("/");
+    const entry = excludingPath(exclude, rel);
+    if (entry === null)
+        return [];
+    return [
+        {
+            severity: "warn",
+            code: "landscape.excluded",
+            // Quoted VERBATIM, for `service.model-excluded`'s reason one level down:
+            // the repair is to edit THAT line, and an entry loam re-spelled is a line
+            // its author would go looking for and not find.
+            message: `landscape: the root ${LIKEC4_PROJECT_FILENAME}'s \`exclude\` covers ${rel} ('${entry}') — the renderer never ` +
+                "loads the fleet map, so it draws no map at all and every model that EXTENDS the map resolves against " +
+                "nothing in the root project, while loam goes on grading the map it reads from disk. `c4.fleet-project-invalid` " +
+                "is NOT graded while this entry stands: that check loads the fleet project the way the renderer does, so it " +
+                "would report the same one line as an unresolved reference in every extending model rather than as this. " +
+                "Remove that entry, or " +
+                `narrow it to the paths it was written for, and the fleet project is graded again. \`loam subsystem sync\` ` +
+                "will not do it: that command maintains " +
+                "only the `services/` entries in the list and leaves every other line exactly as the team wrote it",
+            locations: [{ path: rel, role: "primary" }],
+        },
+    ];
+}
+//# sourceMappingURL=projects.js.map