@ybotok/loam 0.1.0-beta.3 → 0.2.0-alpha.13

package/dist/core/deployment/delta.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"delta.js","sourceRoot":"","sources":["../../../src/core/deployment/delta.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiDG;AACH,OAAO,EAAE,UAAU,EAAE,MAAM,SAAS,CAAC;AACrC,OAAO,EAAE,QAAQ,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAC3C,OAAO,EAAE,eAAe,EAAE,MAAM,+BAA+B,CAAC;AAChE,OAAO,EAAE,kBAAkB,EAAE,MAAM,yBAAyB,CAAC;AAC7D,OAAO,EAAkB,MAAM,iBAAiB,CAAC;AAEjD,OAAO,EAAE,iBAAiB,EAAE,MAAM,4BAA4B,CAAC;AAC/D,OAAO,EAAE,oBAAoB,EAAE,MAAM,2BAA2B,CAAC;AACjE,OAAO,EAAE,wBAAwB,EAAE,MAAM,kBAAkB,CAAC;AAE5D,OAAO,EAAc,MAAM,wBAAwB,CAAC;AAcpD;;;;;;;GAOG;AACH,MAAM,CAAC,KAAK,UAAU,kBAAkB,CAAC,UAAsB;IAC7D,OAAO,iBAAiB,CAAC,oBAAoB,CAAC,UAAU,CAAC,CAAC,CAAC;AAC7D,CAAC;AAED;;;;;;;;;;;;;GAaG;AACH,MAAM,UAAU,oBAAoB,CAAC,OAAgB,EAAE,GAAW;IAChE,OAAO,IAAI,CAAC,eAAe,CAAC,OAAO,CAAC,EAAE,GAAG,CAAC,CAAC;AAC7C,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,MAAM,CAAC,KAAK,UAAU,qBAAqB,CAAC,OAAgB,EAAE,UAAsB;IAClF,MAAM,IAAI,GAAG,MAAM,kBAAkB,CAAC,UAAU,CAAC,CAAC;IAClD,MAAM,MAAM,GAAY,EAAE,CAAC;IAC3B,8EAA8E;IAC9E,wEAAwE;IACxE,sEAAsE;IACtE,4EAA4E;IAC5E,qEAAqE;IACrE,6EAA6E;IAC7E,6BAA6B;IAC7B,KAAK,MAAM,GAAG,IAAI,IAAI,EAAE,CAAC;QACvB,MAAM,MAAM,GAAG,wBAAwB,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;QACjD,IAAI,MAAM,KAAK,IAAI;YAAE,SAAS;QAC9B,MAAM,CAAC,IAAI,CAAC;YACV,QAAQ,EAAE,OAAO;YACjB,IAAI,EAAE,yBAAyB;YAC/B,OAAO,EAAE,GAAG,CAAC,GAAG;YAChB,OAAO,EACL,8BAA8B,GAAG,CAAC,GAAG,gCAAgC,GAAG,CAAC,GAAG,6BAA6B;gBACzG,GAAG,MAAM,kGAAkG;gBAC3G,0CAA0C;SAC7C,CAAC,CAAC;IACL,CAAC;IACD,OAAO,MAAM,CAAC,MAAM,CAClB,IAAI;SACD,MAAM,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,wBAAwB,CAAC,GAAG,CAAC,GAAG,CAAC,KAAK,IAAI,CAAC;SAC3D,MAAM,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,UAAU,CAAC,oBAAoB,CAAC,OAAO,EAAE,GAAG,CAAC,GAAG,CAAC,CAAC,CAAC;SACnE,GAAG,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,CAAC;QACb,QAAQ,EAAE,OAAgB;QAC1B,IAAI,EAAE,uBAAgC;QACtC,OAAO,EAAE,GAAG,CAAC,GAAG;QAChB,OAAO,EACL,gBAAgB,GAAG,CAAC,GAAG,wFAAwF;YAC/G,mFAAmF;YACnF,qCAAqC,GAAG,CAAC,GAAG,0BAA0B,GAAG,CAAC,GAAG,iCAAiC;YAC9G,8EAA8E;YAC9E,6FAA6F;YAC7F,KAAK,OAAO,CAAC,GAAG,CAAC,GAAG,CAAC,mFAAmF;KAC3G,CAAC,CAAC,CACN,CAAC;AACJ,CAAC;AAkCD;;;;;;;;;;;;;GAaG;AACH,MAAM,CAAC,KAAK,UAAU,sBAAsB,CAAC,GAA6B;IACxE,MAAM,IAAI,GAAG,MAAM,kBAAkB,CAAC,GAAG,CAAC,UAAU,CAAC,CAAC;IACtD,IAAI,IAAI,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,EAAE,IAAI,EAAE,MAAM,EAAE,CAAC;IAC/C,wEAAwE;IACxE,uCAAuC;IACvC,MAAM,MAAM,GAAG,GAAG,CAAC,MAAM,KAAK,SAAS,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,MAAM,GAAG,CAAC,MAAM,EAAE,CAAC;IACzE,MAAM,MAAM,GAAG,MAAM,kBAAkB,CAAC;QACtC,OAAO,EAAE,GAAG,CAAC,OAAO;QACpB,UAAU,EAAE,GAAG,CAAC,UAAU;QAC1B,SAAS,EAAE,GAAG,CAAC,SAAS;QACxB,SAAS,EAAE,IAAI,CAAC,GAAG,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,CAAC,EAAE,GAAG,EAAE,GAAG,CAAC,GAAG,EAAE,IAAI,EAAE,GAAG,CAAC,IAAI,EAAE,CAAC,CAAC;QAChE,GAAG,CAAC,GAAG,CAAC,IAAI,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,IAAI,EAAE,GAAG,CAAC,IAAI,EAAE,CAAC;QACrD,GAAG,CAAC,MAAM,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,MAAM,EAAE,CAAC;KAC5C,CAAC,CAAC;IACH,OAAO,MAAM,CAAC,IAAI,KAAK,YAAY,CAAC,CAAC,CAAC,EAAE,IAAI,EAAE,YAAY,EAAE,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,CAAC,CAAC,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,CAAC;AACzG,CAAC;AAED,sFAAsF;AACtF,SAAS,OAAO,CAAC,GAAW;IAC1B,MAAM,IAAI,GAAG,QAAQ,CAAC,GAAG,CAAC,CAAC,OAAO,CAAC,WAAW,EAAE,EAAE,CAAC,CAAC;IACpD,MAAM,GAAG,GAAG,GAAG,CAAC,KAAK,CAAC,CAAC,EAAE,GAAG,CAAC,MAAM,GAAG,QAAQ,CAAC,GAAG,CAAC,CAAC,MAAM,CAAC,CAAC;IAC5D,OAAO,GAAG,GAAG,GAAG,IAAI,gBAAgB,CAAC;AACvC,CAAC","sourcesContent":["/**\n * A feature's own topology: `features/<FEAT>/deployment/<name>.likec4`.\n *\n * Until this slot existed a change that stood up a standby cluster had to be\n * written in two places at once — the requirement in the feature, the topology\n * edited straight into `architecture/` — because `delta.likec4` refuses a\n * `deployment { }` block and always will: that document re-declares the\n * landscape's own identifiers and carries its own `specification`, so it cannot\n * be staged beside the map in one LikeC4 project. A document that declares\n * NEITHER can, which is exactly why the use-case axis put its flows in files of\n * their own, and why this mirrors it rather than inventing a shape.\n *\n * WHAT MAKES IT WORK, and it was measured before the axis was written: LikeC4\n * `extend` resolves across documents of one project. A feature writes\n *\n *     deployment {\n *       extend eu {\n *         dcC = datacenter 'DC-C' { k8sC = cluster 'cluster-c' { … } }\n *       }\n *       eu.dcA.k8sA -> eu.dcC.k8sC 'async replication'\n *     }\n *\n * and the living region gains a datacenter with the living file untouched. So\n * the merge is a copy, not a splice, and `unarchive` needs nothing new — a\n * create is undone by deleting, which the snapshot manifest already records for\n * every write in the plan.\n *\n * CREATE-ONLY, for `core/usecases/delta/flows.ts`'s reasons rather than a\n * weaker version of them. A requirement delta merges INTO a living document and\n * two features editing one requirement would overwrite each other silently; a\n * topology document has no such algebra — the file is one block, the merge is a\n * whole-file copy, and there is nothing to merge partially. Rewriting a living\n * one through a feature would be a silent whole-file replacement with no pin to\n * collide on, where editing `architecture/<name>.likec4` directly in the same\n * pull request produces an ordinary git conflict a human resolves.\n *\n * ## Graded against the map its own merge would leave behind\n *\n * `ARCH-LOAM-FEATURE-CORPUS`, and this axis needs it more literally than the\n * use-case one does: a feature that stands a service up in a new cluster\n * declares that service in its `delta.likec4` and instances it here, so the\n * element the topology names exists ONLY post-merge. Read against the living\n * landscape it is unresolved, LikeC4 refuses the whole project, and loam would\n * report a hole against a file whose only fault is arriving with the change\n * that makes it true.\n *\n * The staging is `core/c4/project/staged.ts`, shared with the use-case slot\n * rather than copied — the two would have disagreed first about the merge\n * preview, which is the one thing both refusals rest on.\n */\nimport { existsSync } from \"node:fs\";\nimport { basename, join } from \"node:path\";\nimport { architectureDir } from \"../c4/project/architecture.js\";\nimport { stageMergedProject } from \"../c4/project/staged.js\";\nimport { type LoadedDoc } from \"../c4/likec4.js\";\nimport type { ExtendingModel } from \"../c4/splice/contract.js\";\nimport { relativeDocuments } from \"../c4/project/documents.js\";\nimport { featureDeploymentDir } from \"../repo/authored/paths.js\";\nimport { reservedArchitectureName } from \"../repo/paths.js\";\nimport type { DocsDir, FeatureDir } from \"../kernel/ids/dirs.js\";\nimport { type Issue } from \"../vocabulary/issue.js\";\n\n/** One topology document a feature carries. */\nexport interface FeatureDeployment {\n  /**\n   * The path INSIDE the feature's `deployment/` directory, `/`-separated — the\n   * id this axis has. Nesting is spelled by the tree, as it is for every other\n   * authored tree in the repo.\n   */\n  rel: string;\n  /** The absolute path of the authored file. */\n  path: string;\n}\n\n/**\n * The topology documents one feature carries, ordered by path.\n *\n * Zero readdirs when the feature has no `deployment/` directory, which is every\n * feature in a fleet that has not adopted the axis: `architectureDocuments`\n * answers an absent directory with an empty list rather than a throw. That\n * directory's existence is the whole per-feature opt-in.\n */\nexport async function featureDeployments(featureDir: FeatureDir): Promise<FeatureDeployment[]> {\n  return relativeDocuments(featureDeploymentDir(featureDir));\n}\n\n/**\n * The LIVING path a feature-local topology document addresses.\n *\n * Straight into `architecture/`, with no subdirectory of its own — unlike\n * `architecture/usecases/`, and the difference is the model rather than taste.\n * A `deployment { }` block is part of the fleet's ONE architecture project and\n * is read as such by every loader; filing it under a subdirectory would suggest\n * a second project, which is exactly the reading `subsystems.likec4` and\n * `landscape.likec4` already refuse by sitting at the top level together.\n *\n * `rel` is joined un-split, which `node:path` normalizes. What holds the join is\n * PROVENANCE: every `rel` here came out of an `architectureDocuments` walk, so\n * each component is a directory entry that exists. No caller takes one from argv.\n */\nexport function livingDeploymentPath(docsDir: DocsDir, rel: string): string {\n  return join(architectureDir(docsDir), rel);\n}\n\n/**\n * The two things that can go wrong about a topology document's NAME, before\n * anything about its contents is asked.\n *\n * `deployment.doc-reserved` — the name is one loam owns inside `architecture/`.\n * The merge writes straight into that directory, unlike a flow, which lands\n * under `usecases/`, so `<name>` is free to collide with the living map, either\n * of the two GENERATED views files (`subsystems.likec4` and `services.likec4`),\n * or the flow tree. `reservedArchitectureName` carries which and why. It is\n * asked FIRST and WITHOUT an existence test, because three of the four fail\n * silently when the target does not exist yet.\n *\n * `deployment.doc-exists` — a topology document this feature introduces that\n * the living `architecture/` already holds.\n *\n * An ERROR and never a warning-that-gates, for `usecase.flow-exists`'s reason:\n * there is no legal reading of it. The merge would replace an authored topology\n * wholesale, and no `--approve` makes that a different act than it is. Two\n * features introducing the same file is the case that makes it load-bearing\n * rather than pedantic — whichever archives first creates the living document,\n * and the second is told before it merges that its own file is the one to\n * delete.\n *\n * The collision is on the FILE, not on what is inside it. Two features may both\n * extend the same living region from two documents of their own and both\n * archive; that is the shape `extend` exists for, and refusing it would make the\n * slot useless for the fleet-wide change it was built for.\n */\nexport async function deploymentDeltaIssues(docsDir: DocsDir, featureDir: FeatureDir): Promise<Issue[]> {\n  const docs = await featureDeployments(featureDir);\n  const issues: Issue[] = [];\n  // The reservation runs FIRST and independently of existence, because three of\n  // the four names it refuses need not exist for the merge to be wrong. A\n  // topology copied over either GENERATED file — `subsystems.likec4` or\n  // `services.likec4` — is destroyed by the next `loam subsystem sync` and is\n  // invisible to every project load until then: the merge would report\n  // `created architecture/subsystems.likec4` and nothing downstream would ever\n  // say another word about it.\n  for (const doc of docs) {\n    const reason = reservedArchitectureName(doc.rel);\n    if (reason === null) continue;\n    issues.push({\n      severity: \"error\",\n      code: \"deployment.doc-reserved\",\n      subject: doc.rel,\n      message:\n        `features/<FEAT>/deployment/${doc.rel} would merge to architecture/${doc.rel}, and that name is loam's: ` +\n        `${reason}. Rename the feature's document — its name is yours to choose, and \\`extend\\` is how it adds to ` +\n        \"what a living document already declares.\",\n    });\n  }\n  return issues.concat(\n    docs\n      .filter((doc) => reservedArchitectureName(doc.rel) === null)\n      .filter((doc) => existsSync(livingDeploymentPath(docsDir, doc.rel)))\n      .map((doc) => ({\n        severity: \"error\" as const,\n        code: \"deployment.doc-exists\" as const,\n        subject: doc.rel,\n        message:\n          `architecture/${doc.rel} already exists, so this feature's topology would replace an authored one wholesale — ` +\n          \"a feature-local deployment document INTRODUCES topology, it does not rewrite it. \" +\n          `Delete features/<FEAT>/deployment/${doc.rel} and edit architecture/${doc.rel} directly in this same change, ` +\n          \"where git produces an ordinary conflict if somebody else is editing it too. \" +\n          `To ADD to what that file declares, write a document of another name that says \\`extend\\` — ` +\n          `\\`${suggest(doc.rel)}\\` — which is what lets two features grow one region without touching each other.`,\n      })),\n  );\n}\n\n/** What the caller needs to grade this feature's topology against the merge preview. */\nexport interface DeploymentOverlayRequest {\n  docsDir: DocsDir;\n  featureDir: FeatureDir;\n  /** The feature's id — the tag that selects the delta's own additions. */\n  featureId: string;\n  /**\n   * The caller's memoised LikeC4 read, when it has one. A FUNCTION rather than\n   * the `FleetContext` itself, for the reason the use-case overlay states: one\n   * memoised read does not justify an edge from this package to\n   * `core/fleet-context.ts`, and the edge would push it up a DAG level for\n   * nothing.\n   */\n  load?: (path: string) => Promise<LoadedDoc>;\n  /**\n   * The fleet's extending models, for the merge preview — the SAME list\n   * `loam archive` routes with. A preview computed without them holds interior\n   * the archive puts in `services/<…>/model.likec4`, so a topology document\n   * naming `<service-fqn>.<container>` reads clean here and against nothing\n   * once it is living; `deployment.doc-invalid` is the gate that then fails\n   * open (verification 2026-09-04, review F8).\n   *\n   * A THUNK for `load`'s reason and one more: the early return below is the\n   * axis's per-feature opt-in, and a feature with no `deployment/` directory\n   * must not pay a fleet enumeration to be told so.\n   */\n  models?: () => Promise<readonly ExtendingModel[]>;\n}\n\n/** Whether this feature's topology could be read at all, against the map its merge would leave. */\nexport type DeploymentOverlay = { kind: \"read\" } | { kind: \"unreadable\"; errors: string[] };\n\n/**\n * Parse this feature's topology documents over the post-merge map.\n *\n * A feature with no `deployment/` directory is `read` at the cost of one walk\n * over a directory that is not there — the axis's per-feature opt-in, and the\n * whole price a fleet that has not adopted it pays. Nothing is staged, nothing\n * is parsed, and no temp tree is made.\n *\n * The verdict is deliberately BINARY. The use-case overlay hands its caller the\n * views it read because the axis has questions about their content; this one\n * has none — a topology document is checked by being parseable against the map\n * the merge will write, and everything else about it is graded by\n * `loam validate --all` once it is living, exactly as the landscape is.\n */\nexport async function readFeatureDeployments(req: DeploymentOverlayRequest): Promise<DeploymentOverlay> {\n  const docs = await featureDeployments(req.featureDir);\n  if (docs.length === 0) return { kind: \"read\" };\n  // AFTER the early return: the fleet read is paid only by a feature that\n  // actually brings a topology document.\n  const models = req.models === undefined ? undefined : await req.models();\n  const staged = await stageMergedProject({\n    docsDir: req.docsDir,\n    featureDir: req.featureDir,\n    featureId: req.featureId,\n    documents: docs.map((doc) => ({ rel: doc.rel, path: doc.path })),\n    ...(req.load === undefined ? {} : { load: req.load }),\n    ...(models === undefined ? {} : { models }),\n  });\n  return staged.kind === \"unreadable\" ? { kind: \"unreadable\", errors: staged.errors } : { kind: \"read\" };\n}\n\n/** A free name near the colliding one, so the fix is a rename the author can copy. */\nfunction suggest(rel: string): string {\n  const name = basename(rel).replace(/\\.likec4$/, \"\");\n  const dir = rel.slice(0, rel.length - basename(rel).length);\n  return `${dir}${name}-extend.likec4`;\n}\n"]}

package/dist/core/deployment/objects.js

@@ -0,0 +1,145 @@
+/**
+ * The deployment axis: which objects on the fleet's TOPOLOGY carry a rule, and
+ * who owns each of them.
+ *
+ * A `#obl-` tag is a claim about the object it sits on, and the object's model
+ * is not a property any reader can see. Before this module the same undeclared
+ * tag was `obligation.unknown` on a container and SILENCE on a datacenter,
+ * because `validate/fleet/obligations.ts` walked the logical model only — the
+ * fail-open case where a rule an architect placed does not exist for any check,
+ * and a reviewer has no way to tell that from a rule that passed. This is the
+ * derivation that closes it (FEAT-1's ARCH-LOAM-DEPLOY-TAGGED).
+ *
+ * ## The `where` string is the `Covers:` line
+ *
+ * Every finding about a tagged object tells its reader to write
+ * `Covers: <where>`, so `where` is spelled as the grammar reads it —
+ * `node:eu.dcA`, `node:a.db -> node:b.db` — and never as a bare id. A message
+ * that names an object one way and asks for a line spelled another way sends
+ * the reader round the loop twice.
+ *
+ * ## Who owns a datacenter
+ *
+ * Nobody, and the answer is `undefined` rather than a guess. An INSTANCE is
+ * owned by the service its logical element belongs to, which is a real join
+ * through the landscape's own binding; an edge between two instances of one
+ * service is owned by that service; a region, a datacenter or a cluster is
+ * owned by whoever runs the platform, and loam has no such concept. The finding
+ * changes its sentence rather than naming a service that did not ask for the
+ * work — "write it in payment-service's arch.spec.md" is actionable, and
+ * "write it in <the wrong team>'s" is worse than no attribution at all.
+ *
+ * This package is one module today and gains its second with the feature-local
+ * `features/<FEAT>/deployment/` slot, which is the step of the axis that needs
+ * `repo` and `kernel`. Nothing here reads a path.
+ */
+import {} from "../c4/likec4.js";
+import {} from "../c4/parsed/deployment.js";
+import { serviceResolver } from "../c4/resolve/service.js";
+/**
+ * Every `#obl-` tag on the deployment model, one entry per (obligation, object)
+ * pair — the same shape, and the same bare-prefix tolerance, the logical walk
+ * has: a bare `#obl-` slugs to the empty string and is KEPT, because the prefix
+ * is the author's opt-in however little follows it, and dropping it would leave
+ * an object that asked to be graded silently ungraded.
+ */
+export function taggedDeployment(deployment, elements, known, prefix) {
+    const owner = instanceOwners(deployment, elements, known);
+    const out = [];
+    const push = (tags, rest) => {
+        for (const tag of tags.filter((t) => t.startsWith(prefix))) {
+            out.push({ obligation: tag.slice(prefix.length), ...rest });
+        }
+    };
+    // Nodes first, then instances, then edges — the order the model declares them
+    // in, so a fleet report reads top-down the way the document does.
+    for (const node of deployment.nodes)
+        push(node.tags, { where: `node:${node.id}`, id: node.id });
+    for (const instance of deployment.instances) {
+        const service = owner.get(instance.id);
+        push(instance.tags, {
+            where: `node:${instance.id}`,
+            id: instance.id,
+            ...(service === undefined ? {} : { service }),
+        });
+    }
+    for (const edge of deployment.relationships) {
+        // An edge is owned only when BOTH ends agree. A replication edge between
+        // two instances of one service belongs to that service; one crossing
+        // services belongs to neither, and picking the target — the rule the
+        // logical walk uses, where the arrow means "calls" — says nothing here,
+        // because a deployment edge is as often symmetric as directed.
+        const from = owner.get(edge.source);
+        const to = owner.get(edge.target);
+        const service = from !== undefined && from === to ? from : undefined;
+        push(edge.tags, {
+            where: `node:${edge.source} -> node:${edge.target}`,
+            edge,
+            ...(service === undefined ? {} : { service }),
+        });
+    }
+    return out;
+}
+/**
+ * The topology one service is part of.
+ *
+ * Built for the CONTEXT PACK, which is the surface whose reader is an agent
+ * about to write the implementation. Before this, that pack described a
+ * service's calls and contracts and said nothing whatever about where it runs —
+ * so a failover was implemented against a map nobody had read, which is the
+ * gap FEAT-1's ARCH-LOAM-DEPLOY-UNCHECKED names alongside the sentence about
+ * what a green axis does not mean.
+ *
+ * BOTH ENDS, not only the outbound one. A replication edge is as often read
+ * from the standby's side as from the primary's, and a pack that showed only
+ * what this service points at would hide the stream it receives.
+ */
+export function serviceTopology(deployment, elements, known, service) {
+    const owner = instanceOwners(deployment, elements, known);
+    const mine = deployment.instances.filter((i) => owner.get(i.id) === service);
+    const ids = new Set(mine.map((i) => i.id));
+    return {
+        instances: mine.map((i) => ({ id: i.id, element: i.element })),
+        edges: deployment.relationships
+            .filter((r) => ids.has(r.source) || ids.has(r.target))
+            .map((r) => ({ source: r.source, target: r.target, ...(r.title === undefined ? {} : { title: r.title }) })),
+    };
+}
+/**
+ * instance id → the service its logical element belongs to.
+ *
+ * Through `serviceResolver` and NOT `elementService`, and the difference is a
+ * defect this axis shipped once. A deployment instances a CONTAINER far more
+ * often than a whole system — `instanceOf orders.cache` is the ordinary way to
+ * say where the Redis a service owns actually runs — and `elementService` reads
+ * the binding or the TITLE of the element handed to it. A nested container
+ * carries no `metadata { service }` of its own, so that read answered "order
+ * cache", and `obligation.uncovered` told an author to write the requirement in
+ * "order cache's arch.spec.md" — a service that has never existed. The
+ * resolver's whole job is the ancestor walk that finds the bound system above
+ * it, which is the same join every other check makes about a container.
+ *
+ * `known` rides in for the reason `coversEdge` takes it: without the enumerated
+ * fleet the resolver's second tier — the nearest ancestor whose title names a
+ * real `services/<id>/` — cannot run, and a fleet that binds by title rather
+ * than by `metadata { service }` resolves to the title alone. It must be the
+ * SAME set the caller's own findings resolve with, or the message names one
+ * service and the check counts another.
+ *
+ * An instance of an element the landscape does not declare is left UNOWNED
+ * rather than filed under a fabricated name. LikeC4 refuses an unresolved
+ * `instanceOf` outright, so that state is reachable only when the caller hands
+ * in elements from a narrower document than the one the topology was parsed
+ * with.
+ */
+function instanceOwners(deployment, elements, known) {
+    const ids = new Set(elements.map((e) => e.id));
+    const resolve = serviceResolver([...elements], known);
+    const out = new Map();
+    for (const instance of deployment.instances) {
+        if (ids.has(instance.element))
+            out.set(instance.id, resolve(instance.element));
+    }
+    return out;
+}
+//# sourceMappingURL=objects.js.map

package/dist/core/deployment/objects.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"objects.js","sourceRoot":"","sources":["../../../src/core/deployment/objects.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAkCG;AACH,OAAO,EAAa,MAAM,iBAAiB,CAAC;AAC5C,OAAO,EAAwC,MAAM,4BAA4B,CAAC;AAClF,OAAO,EAAE,eAAe,EAAE,MAAM,0BAA0B,CAAC;AAmB3D;;;;;;GAMG;AACH,MAAM,UAAU,gBAAgB,CAC9B,UAA2B,EAC3B,QAAyB,EACzB,KAA0B,EAC1B,MAAc;IAEd,MAAM,KAAK,GAAG,cAAc,CAAC,UAAU,EAAE,QAAQ,EAAE,KAAK,CAAC,CAAC;IAC1D,MAAM,GAAG,GAAuB,EAAE,CAAC;IACnC,MAAM,IAAI,GAAG,CAAC,IAAuB,EAAE,IAA0C,EAAQ,EAAE;QACzF,KAAK,MAAM,GAAG,IAAI,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,UAAU,CAAC,MAAM,CAAC,CAAC,EAAE,CAAC;YAC3D,GAAG,CAAC,IAAI,CAAC,EAAE,UAAU,EAAE,GAAG,CAAC,KAAK,CAAC,MAAM,CAAC,MAAM,CAAC,EAAE,GAAG,IAAI,EAAE,CAAC,CAAC;QAC9D,CAAC;IACH,CAAC,CAAC;IAEF,8EAA8E;IAC9E,kEAAkE;IAClE,KAAK,MAAM,IAAI,IAAI,UAAU,CAAC,KAAK;QAAE,IAAI,CAAC,IAAI,CAAC,IAAI,EAAE,EAAE,KAAK,EAAE,QAAQ,IAAI,CAAC,EAAE,EAAE,EAAE,EAAE,EAAE,IAAI,CAAC,EAAE,EAAE,CAAC,CAAC;IAChG,KAAK,MAAM,QAAQ,IAAI,UAAU,CAAC,SAAS,EAAE,CAAC;QAC5C,MAAM,OAAO,GAAG,KAAK,CAAC,GAAG,CAAC,QAAQ,CAAC,EAAE,CAAC,CAAC;QACvC,IAAI,CAAC,QAAQ,CAAC,IAAI,EAAE;YAClB,KAAK,EAAE,QAAQ,QAAQ,CAAC,EAAE,EAAE;YAC5B,EAAE,EAAE,QAAQ,CAAC,EAAE;YACf,GAAG,CAAC,OAAO,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,OAAO,EAAE,CAAC;SAC9C,CAAC,CAAC;IACL,CAAC;IACD,KAAK,MAAM,IAAI,IAAI,UAAU,CAAC,aAAa,EAAE,CAAC;QAC5C,yEAAyE;QACzE,qEAAqE;QACrE,qEAAqE;QACrE,wEAAwE;QACxE,+DAA+D;QAC/D,MAAM,IAAI,GAAG,KAAK,CAAC,GAAG,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;QACpC,MAAM,EAAE,GAAG,KAAK,CAAC,GAAG,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;QAClC,MAAM,OAAO,GAAG,IAAI,KAAK,SAAS,IAAI,IAAI,KAAK,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,SAAS,CAAC;QACrE,IAAI,CAAC,IAAI,CAAC,IAAI,EAAE;YACd,KAAK,EAAE,QAAQ,IAAI,CAAC,MAAM,YAAY,IAAI,CAAC,MAAM,EAAE;YACnD,IAAI;YACJ,GAAG,CAAC,OAAO,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,OAAO,EAAE,CAAC;SAC9C,CAAC,CAAC;IACL,CAAC;IACD,OAAO,GAAG,CAAC;AACb,CAAC;AAUD;;;;;;;;;;;;;GAaG;AACH,MAAM,UAAU,eAAe,CAC7B,UAA2B,EAC3B,QAAyB,EACzB,KAA0B,EAC1B,OAAe;IAEf,MAAM,KAAK,GAAG,cAAc,CAAC,UAAU,EAAE,QAAQ,EAAE,KAAK,CAAC,CAAC;IAC1D,MAAM,IAAI,GAAG,UAAU,CAAC,SAAS,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,KAAK,OAAO,CAAC,CAAC;IAC7E,MAAM,GAAG,GAAG,IAAI,GAAG,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC;IAC3C,OAAO;QACL,SAAS,EAAE,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,CAAC,EAAE,EAAE,OAAO,EAAE,CAAC,CAAC,OAAO,EAAE,CAAC,CAAC;QAC9D,KAAK,EAAE,UAAU,CAAC,aAAa;aAC5B,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,CAAC,MAAM,CAAC,IAAI,GAAG,CAAC,GAAG,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC;aACrD,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,EAAE,MAAM,EAAE,CAAC,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC,CAAC,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,CAAC,CAAC,KAAK,EAAE,CAAC,EAAE,CAAC,CAAC;KAC9G,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AACH,SAAS,cAAc,CACrB,UAA2B,EAC3B,QAAyB,EACzB,KAA0B;IAE1B,MAAM,GAAG,GAAG,IAAI,GAAG,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC;IAC/C,MAAM,OAAO,GAAG,eAAe,CAAC,CAAC,GAAG,QAAQ,CAAC,EAAE,KAAK,CAAC,CAAC;IACtD,MAAM,GAAG,GAAG,IAAI,GAAG,EAAkB,CAAC;IACtC,KAAK,MAAM,QAAQ,IAAI,UAAU,CAAC,SAAS,EAAE,CAAC;QAC5C,IAAI,GAAG,CAAC,GAAG,CAAC,QAAQ,CAAC,OAAO,CAAC;YAAE,GAAG,CAAC,GAAG,CAAC,QAAQ,CAAC,EAAE,EAAE,OAAO,CAAC,QAAQ,CAAC,OAAO,CAAC,CAAC,CAAC;IACjF,CAAC;IACD,OAAO,GAAG,CAAC;AACb,CAAC","sourcesContent":["/**\n * The deployment axis: which objects on the fleet's TOPOLOGY carry a rule, and\n * who owns each of them.\n *\n * A `#obl-` tag is a claim about the object it sits on, and the object's model\n * is not a property any reader can see. Before this module the same undeclared\n * tag was `obligation.unknown` on a container and SILENCE on a datacenter,\n * because `validate/fleet/obligations.ts` walked the logical model only — the\n * fail-open case where a rule an architect placed does not exist for any check,\n * and a reviewer has no way to tell that from a rule that passed. This is the\n * derivation that closes it (FEAT-1's ARCH-LOAM-DEPLOY-TAGGED).\n *\n * ## The `where` string is the `Covers:` line\n *\n * Every finding about a tagged object tells its reader to write\n * `Covers: <where>`, so `where` is spelled as the grammar reads it —\n * `node:eu.dcA`, `node:a.db -> node:b.db` — and never as a bare id. A message\n * that names an object one way and asks for a line spelled another way sends\n * the reader round the loop twice.\n *\n * ## Who owns a datacenter\n *\n * Nobody, and the answer is `undefined` rather than a guess. An INSTANCE is\n * owned by the service its logical element belongs to, which is a real join\n * through the landscape's own binding; an edge between two instances of one\n * service is owned by that service; a region, a datacenter or a cluster is\n * owned by whoever runs the platform, and loam has no such concept. The finding\n * changes its sentence rather than naming a service that did not ask for the\n * work — \"write it in payment-service's arch.spec.md\" is actionable, and\n * \"write it in <the wrong team>'s\" is worse than no attribution at all.\n *\n * This package is one module today and gains its second with the feature-local\n * `features/<FEAT>/deployment/` slot, which is the step of the axis that needs\n * `repo` and `kernel`. Nothing here reads a path.\n */\nimport { type Elem } from \"../c4/likec4.js\";\nimport { type DeploymentModel, type DeployRel } from \"../c4/parsed/deployment.js\";\nimport { serviceResolver } from \"../c4/resolve/service.js\";\n\n/** One deployment object carrying one obligation tag. */\nexport interface TaggedDeployment {\n  /** The obligation id — the tag suffix, exactly as the logical walk reads it. */\n  obligation: string;\n  /**\n   * How a `Covers:` line names this object, and how every message spells it:\n   * `node:<id>` for a node or an instance, `node:<a> -> node:<b>` for an edge.\n   */\n  where: string;\n  /** The service that owns it, where the topology says. Absent for a node nobody's service runs. */\n  service?: string;\n  /** The edge, when this object is one — the caller matches `Covers:` against it. */\n  edge?: DeployRel;\n  /** The node or instance id, when this object is one. */\n  id?: string;\n}\n\n/**\n * Every `#obl-` tag on the deployment model, one entry per (obligation, object)\n * pair — the same shape, and the same bare-prefix tolerance, the logical walk\n * has: a bare `#obl-` slugs to the empty string and is KEPT, because the prefix\n * is the author's opt-in however little follows it, and dropping it would leave\n * an object that asked to be graded silently ungraded.\n */\nexport function taggedDeployment(\n  deployment: DeploymentModel,\n  elements: readonly Elem[],\n  known: ReadonlySet<string>,\n  prefix: string,\n): TaggedDeployment[] {\n  const owner = instanceOwners(deployment, elements, known);\n  const out: TaggedDeployment[] = [];\n  const push = (tags: readonly string[], rest: Omit<TaggedDeployment, \"obligation\">): void => {\n    for (const tag of tags.filter((t) => t.startsWith(prefix))) {\n      out.push({ obligation: tag.slice(prefix.length), ...rest });\n    }\n  };\n\n  // Nodes first, then instances, then edges — the order the model declares them\n  // in, so a fleet report reads top-down the way the document does.\n  for (const node of deployment.nodes) push(node.tags, { where: `node:${node.id}`, id: node.id });\n  for (const instance of deployment.instances) {\n    const service = owner.get(instance.id);\n    push(instance.tags, {\n      where: `node:${instance.id}`,\n      id: instance.id,\n      ...(service === undefined ? {} : { service }),\n    });\n  }\n  for (const edge of deployment.relationships) {\n    // An edge is owned only when BOTH ends agree. A replication edge between\n    // two instances of one service belongs to that service; one crossing\n    // services belongs to neither, and picking the target — the rule the\n    // logical walk uses, where the arrow means \"calls\" — says nothing here,\n    // because a deployment edge is as often symmetric as directed.\n    const from = owner.get(edge.source);\n    const to = owner.get(edge.target);\n    const service = from !== undefined && from === to ? from : undefined;\n    push(edge.tags, {\n      where: `node:${edge.source} -> node:${edge.target}`,\n      edge,\n      ...(service === undefined ? {} : { service }),\n    });\n  }\n  return out;\n}\n\n/** Where one service runs, and what its instances talk to across the topology. */\nexport interface ServiceTopology {\n  /** This service's instances: the deployment id, and the element each one deploys. */\n  instances: Array<{ id: string; element: string }>;\n  /** Deployment edges with at least one end among them — replication, failover, a network hop. */\n  edges: Array<{ source: string; target: string; title?: string }>;\n}\n\n/**\n * The topology one service is part of.\n *\n * Built for the CONTEXT PACK, which is the surface whose reader is an agent\n * about to write the implementation. Before this, that pack described a\n * service's calls and contracts and said nothing whatever about where it runs —\n * so a failover was implemented against a map nobody had read, which is the\n * gap FEAT-1's ARCH-LOAM-DEPLOY-UNCHECKED names alongside the sentence about\n * what a green axis does not mean.\n *\n * BOTH ENDS, not only the outbound one. A replication edge is as often read\n * from the standby's side as from the primary's, and a pack that showed only\n * what this service points at would hide the stream it receives.\n */\nexport function serviceTopology(\n  deployment: DeploymentModel,\n  elements: readonly Elem[],\n  known: ReadonlySet<string>,\n  service: string,\n): ServiceTopology {\n  const owner = instanceOwners(deployment, elements, known);\n  const mine = deployment.instances.filter((i) => owner.get(i.id) === service);\n  const ids = new Set(mine.map((i) => i.id));\n  return {\n    instances: mine.map((i) => ({ id: i.id, element: i.element })),\n    edges: deployment.relationships\n      .filter((r) => ids.has(r.source) || ids.has(r.target))\n      .map((r) => ({ source: r.source, target: r.target, ...(r.title === undefined ? {} : { title: r.title }) })),\n  };\n}\n\n/**\n * instance id → the service its logical element belongs to.\n *\n * Through `serviceResolver` and NOT `elementService`, and the difference is a\n * defect this axis shipped once. A deployment instances a CONTAINER far more\n * often than a whole system — `instanceOf orders.cache` is the ordinary way to\n * say where the Redis a service owns actually runs — and `elementService` reads\n * the binding or the TITLE of the element handed to it. A nested container\n * carries no `metadata { service }` of its own, so that read answered \"order\n * cache\", and `obligation.uncovered` told an author to write the requirement in\n * \"order cache's arch.spec.md\" — a service that has never existed. The\n * resolver's whole job is the ancestor walk that finds the bound system above\n * it, which is the same join every other check makes about a container.\n *\n * `known` rides in for the reason `coversEdge` takes it: without the enumerated\n * fleet the resolver's second tier — the nearest ancestor whose title names a\n * real `services/<id>/` — cannot run, and a fleet that binds by title rather\n * than by `metadata { service }` resolves to the title alone. It must be the\n * SAME set the caller's own findings resolve with, or the message names one\n * service and the check counts another.\n *\n * An instance of an element the landscape does not declare is left UNOWNED\n * rather than filed under a fabricated name. LikeC4 refuses an unresolved\n * `instanceOf` outright, so that state is reachable only when the caller hands\n * in elements from a narrower document than the one the topology was parsed\n * with.\n */\nfunction instanceOwners(\n  deployment: DeploymentModel,\n  elements: readonly Elem[],\n  known: ReadonlySet<string>,\n): Map<string, string> {\n  const ids = new Set(elements.map((e) => e.id));\n  const resolve = serviceResolver([...elements], known);\n  const out = new Map<string, string>();\n  for (const instance of deployment.instances) {\n    if (ids.has(instance.element)) out.set(instance.id, resolve(instance.element));\n  }\n  return out;\n}\n"]}

package/dist/core/diff/base-git.js

@@ -0,0 +1,230 @@
+/**
+ * Git-at-a-ref reader for the DOCS repo — the base side of `loam diff`, and
+ * the "what had already shipped" side of `loam gate --since`.
+ *
+ * Five questions, all read-only: does this docs directory sit in a git
+ * repository and where (`resolveBase`), what did `services/` hold at the base
+ * commit (`listBaseTree`), which subdirectories did one docs directory hold
+ * there (`listBaseSubdirs` — gate's `features/archive/` question) and which of
+ * them differ in the working tree now (`subdirsChangedSince` — its second),
+ * and what were one file's bytes there (`showBaseFile`). No checkout, no temp
+ * writes — the base state is read straight out of the object store with
+ * `rev-parse`/`ls-tree`/`show`, and the comparison with `diff`/`ls-files`.
+ *
+ * Gate takes diff's doctrine below along with the mechanics: a `--since` ref
+ * git cannot answer for is a refusal, never "nothing was archived since",
+ * because that silence would pass a deploy over every feature it could not
+ * see — the same fail-open as a silently empty diff base, one command over.
+ *
+ * The doctrine here is deliberately NOT provenance's. `../provenance/git.ts`
+ * answers every git decline with "git will not say" — null, no finding —
+ * because provenance has no denominator without git and nothing to report.
+ * Diff is the opposite case: without the base there is no honest diff at all,
+ * and a silently empty base would report the whole fleet as ADDED — the exact
+ * "green over zero services" failure `docsRepoReady` exists to prevent, one
+ * step later. So every decline travels as a typed outcome the command REFUSES
+ * on, carrying git's own words (bounded) so the refusal can say why.
+ *
+ * What is shared with provenance is the mechanics: the one timeout and the
+ * capped stdout reader, so rule 20 (every child spawn bounded) holds by
+ * construction.
+ */
+import { spawn } from "node:child_process";
+import { relative, sep } from "node:path";
+import { collectStderr, declineDetail, GIT_TIMEOUT_MS, gitSaid, gitText } from "../provenance/git.js";
+/**
+ * How many bytes one base file may be — the same generosity as
+ * `../provenance/git.ts`'s stdout cap, restated here because that constant is
+ * private to its module and this one collects BYTES, not text (a base
+ * contract's UTF-8-ness is a fact to grade, and `setEncoding("utf8")` would
+ * substitute U+FFFD before anyone could check). Past the cap the child is
+ * killed and the file reads as unreadable for its subject, never truncated.
+ *
+ * The question-asking mechanics — `gitText`, `GitAnswer`, `gitSaid`,
+ * `declineDetail`, `collectStderr` — are the shared set `../provenance/git.ts`
+ * exports: `../provenance/gitq/vouched-ancestor.ts` asks with the
+ * same shapes and the opposite consequence (it degrades to "full read" where
+ * this module's callers REFUSE), and the helpers stay verdict-free so the two
+ * doctrines cannot bleed into each other through a shared line.
+ */
+const MAX_BASE_FILE_BYTES = 64 * 1024 * 1024;
+/**
+ * Resolve the base: is `docsDir` inside a git work tree, where does it sit in
+ * that repository, and which commit does `ref` name?
+ *
+ * `--show-prefix` is asked FIRST and is not decoration: a docs repo checked
+ * out as a subdirectory of a larger repository (a monorepo's `docs/`) answers
+ * every later `ls-tree`/`show` only under that prefix. Dropping it makes every
+ * path miss, and a diff whose base paths all miss reports the whole fleet as
+ * added — silently, in exactly the repositories big enough to care.
+ */
+export async function resolveBase(docsDir, ref) {
+    const where = await gitText(docsDir, ["rev-parse", "--show-prefix"]);
+    if (where.spawnError !== undefined || where.code !== 0) {
+        return { kind: "no-git", detail: declineDetail(where) };
+    }
+    // A ref spelled like an option would be parsed as one by git, not resolved
+    // as a revision — refuse it before it reaches an argv. Same reason the MCP
+    // argv boundary refuses '-'-prefixed strings.
+    const spelled = ref.trim();
+    if (spelled === "" || spelled.startsWith("-")) {
+        return { kind: "no-ref", detail: "a ref must be a revision name, not empty and not option-shaped." };
+    }
+    // `^{commit}` peels an annotated tag to the commit it tags, and refuses a
+    // ref that names any other object kind — a tree or blob sha is not a base
+    // state to diff against.
+    const verified = await gitText(docsDir, ["rev-parse", "--verify", `${spelled}^{commit}`]);
+    const commit = verified.out.trim();
+    if (verified.code !== 0 || !/^[0-9a-f]{40}$/.test(commit)) {
+        const said = gitSaid(verified);
+        return { kind: "no-ref", detail: said === "" ? "" : `git said: ${said}` };
+    }
+    return { kind: "ok", commit, prefix: where.out.trim() };
+}
+/**
+ * Every file path under `services/` at the base commit, DOCS-RELATIVE
+ * (`services/...`, prefix already stripped — `lsTree` below holds the
+ * mechanics both listings share). An empty answer is git ANSWERING — the base
+ * commit simply has no `services/` — and only a non-zero exit is a failure.
+ */
+export async function listBaseTree(base) {
+    return lsTree(base, "-r", "services");
+}
+/**
+ * The NAMES of the immediate subdirectories of one docs directory at the base
+ * commit — `loam gate --since`'s question: which `features/archive/<FEAT>/`
+ * directories already existed at the ref, so every other archived feature
+ * shipped after it. `dir` is the absolute path a `repo/paths.ts` builder
+ * spells (`archiveDir`), made docs-relative here, so the layout keeps its one
+ * spelling; the separator is forced to `/` because git paths are slash-joined
+ * on every host. `-d` lists trees only, and the trailing slash asks for the
+ * directory's CHILDREN rather than the directory entry itself. An empty answer
+ * is git answering — the base had no such directory — and only a decline is
+ * `failed`, which the caller refuses on, as `listBaseTree`'s callers do.
+ */
+export async function listBaseSubdirs(base, dir) {
+    const rel = `${relative(base.docsDir, dir).split(sep).join("/")}/`;
+    const listing = await lsTree(base, "-d", rel);
+    if (listing.kind === "failed")
+        return listing;
+    return {
+        kind: "ok",
+        names: listing.paths.filter((p) => p.startsWith(rel)).map((p) => p.slice(rel.length)),
+    };
+}
+/**
+ * The NAMES of the immediate subdirectories of one docs directory whose
+ * contents differ between the base commit and the WORKING TREE — committed
+ * since or not — gate's second `features/archive/` question. A directory that
+ * was already there at the ref is not thereby old: `loam unarchive`, an edit
+ * and `loam archive` again leave a feature at the very path it shipped from
+ * before, and reading presence alone graded that re-shipped feature as one an
+ * earlier deploy had already answered for.
+ *
+ * Not a comparison of tree ids, though `ls-tree` has the ref's: the working
+ * tree has no id until somebody commits it, and minting one means writing
+ * objects — this module asks git, it never writes. The same two questions as
+ * `validate --base`'s scope (`./scope/changed-paths.ts`) instead, narrowed to
+ * the one directory: `git diff` for every tracked path that differs from the
+ * ref, `--no-renames` so a moved file names the place it left as well as the
+ * one it reached, and `ls-files --others` for what nobody has committed yet —
+ * the re-archive a pipeline is about to ship is exactly that. Both pathspecs
+ * are relative to `docsDir`, where git runs; both listings answer
+ * root-relative (`git diff` always, `ls-files` under `--full-name`), so the
+ * one prefix strip serves both. A decline is `failed`, and the caller decides
+ * which way that fails.
+ */
+export async function subdirsChangedSince(base, dir) {
+    const rel = `${relative(base.docsDir, dir).split(sep).join("/")}/`;
+    const tracked = await gitText(base.docsDir, ["diff", "--name-only", "--no-renames", "--no-ext-diff", "-z", base.commit, "--", rel]);
+    if (tracked.spawnError !== undefined || tracked.code !== 0 || tracked.overflowed) {
+        return { kind: "failed", detail: tracked.overflowed ? "the changed-path listing exceeded the output cap." : declineDetail(tracked) };
+    }
+    const untracked = await gitText(base.docsDir, ["ls-files", "--others", "--exclude-standard", "--full-name", "-z", "--", rel]);
+    if (untracked.spawnError !== undefined || untracked.code !== 0 || untracked.overflowed) {
+        return { kind: "failed", detail: untracked.overflowed ? "the untracked-path listing exceeded the output cap." : declineDetail(untracked) };
+    }
+    const under = `${base.prefix}${rel}`;
+    const names = new Set();
+    for (const path of [...tracked.out.split("\0"), ...untracked.out.split("\0")]) {
+        if (!path.startsWith(under))
+            continue;
+        const name = path.slice(under.length).split("/")[0];
+        if (name !== "")
+            names.add(name);
+    }
+    return { kind: "ok", names };
+}
+/**
+ * The one `ls-tree` both listings ask, DOCS-RELATIVE (prefix already
+ * stripped). `--full-tree` anchors both the pathspec and the output at the
+ * repository root regardless of cwd, so the one prefix from `resolveBase` is
+ * the whole story; `-z` because git quotes non-ASCII paths in line output.
+ */
+async function lsTree(base, mode, root) {
+    const answer = await gitText(base.docsDir, [
+        "ls-tree", mode, "-z", "--name-only", "--full-tree", base.commit, "--", `${base.prefix}${root}`,
+    ]);
+    if (answer.spawnError !== undefined || answer.code !== 0 || answer.overflowed) {
+        return {
+            kind: "failed",
+            detail: answer.overflowed
+                ? "the base tree listing exceeded the output cap."
+                : declineDetail(answer),
+        };
+    }
+    return {
+        kind: "ok",
+        paths: answer.out
+            .split("\0")
+            .filter((p) => p.startsWith(base.prefix) && p !== "")
+            .map((p) => p.slice(base.prefix.length)),
+    };
+}
+/**
+ * One base file's bytes, by docs-relative path. Callers only ask for paths
+ * `listBaseTree` returned, so there is no "absent" arm: a decline here is
+ * abnormal and travels as `failed` for per-subject containment — that one
+ * subject degrades with the detail, never the whole diff.
+ */
+export async function showBaseFile(base, rel) {
+    return new Promise((done) => {
+        const child = spawn("git", ["show", `${base.commit}:${base.prefix}${rel}`], {
+            cwd: base.docsDir,
+            stdio: ["ignore", "pipe", "pipe"],
+            timeout: GIT_TIMEOUT_MS,
+        });
+        // Bytes, not text: `collectStdout` decodes as UTF-8, and a base contract
+        // whose bytes are NOT UTF-8 must arrive intact so base-state can grade it
+        // unreadable instead of parsing a document nobody wrote.
+        const chunks = [];
+        let held = 0;
+        let overflowed = false;
+        child.stdout.on("data", (chunk) => {
+            if (overflowed)
+                return;
+            if (held + chunk.length > MAX_BASE_FILE_BYTES) {
+                overflowed = true;
+                child.kill();
+                return;
+            }
+            chunks.push(chunk);
+            held += chunk.length;
+        });
+        const err = collectStderr(child);
+        child.on("error", (e) => done({ kind: "failed", detail: `git could not be started: ${e.message}.` }));
+        child.on("close", (code) => {
+            if (code !== 0 || overflowed) {
+                done({
+                    kind: "failed",
+                    detail: overflowed
+                        ? "the file exceeds the base-read byte cap."
+                        : declineDetail({ code, out: "", err: err(), overflowed }),
+                });
+                return;
+            }
+            done({ kind: "ok", bytes: Buffer.concat(chunks) });
+        });
+    });
+}
+//# sourceMappingURL=base-git.js.map

package/dist/core/diff/base-git.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"base-git.js","sourceRoot":"","sources":["../../../src/core/diff/base-git.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8BG;AACH,OAAO,EAAE,KAAK,EAAE,MAAM,oBAAoB,CAAC;AAC3C,OAAO,EAAE,QAAQ,EAAE,GAAG,EAAE,MAAM,WAAW,CAAC;AAC1C,OAAO,EAAE,aAAa,EAAE,aAAa,EAAE,cAAc,EAAE,OAAO,EAAE,OAAO,EAAE,MAAM,sBAAsB,CAAC;AAGtG;;;;;;;;;;;;;;GAcG;AACH,MAAM,mBAAmB,GAAG,EAAE,GAAG,IAAI,GAAG,IAAI,CAAC;AAO7C;;;;;;;;;GASG;AACH,MAAM,CAAC,KAAK,UAAU,WAAW,CAAC,OAAgB,EAAE,GAAW;IAC7D,MAAM,KAAK,GAAG,MAAM,OAAO,CAAC,OAAO,EAAE,CAAC,WAAW,EAAE,eAAe,CAAC,CAAC,CAAC;IACrE,IAAI,KAAK,CAAC,UAAU,KAAK,SAAS,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,EAAE,CAAC;QACvD,OAAO,EAAE,IAAI,EAAE,QAAQ,EAAE,MAAM,EAAE,aAAa,CAAC,KAAK,CAAC,EAAE,CAAC;IAC1D,CAAC;IACD,2EAA2E;IAC3E,2EAA2E;IAC3E,8CAA8C;IAC9C,MAAM,OAAO,GAAG,GAAG,CAAC,IAAI,EAAE,CAAC;IAC3B,IAAI,OAAO,KAAK,EAAE,IAAI,OAAO,CAAC,UAAU,CAAC,GAAG,CAAC,EAAE,CAAC;QAC9C,OAAO,EAAE,IAAI,EAAE,QAAQ,EAAE,MAAM,EAAE,iEAAiE,EAAE,CAAC;IACvG,CAAC;IACD,0EAA0E;IAC1E,0EAA0E;IAC1E,yBAAyB;IACzB,MAAM,QAAQ,GAAG,MAAM,OAAO,CAAC,OAAO,EAAE,CAAC,WAAW,EAAE,UAAU,EAAE,GAAG,OAAO,WAAW,CAAC,CAAC,CAAC;IAC1F,MAAM,MAAM,GAAG,QAAQ,CAAC,GAAG,CAAC,IAAI,EAAE,CAAC;IACnC,IAAI,QAAQ,CAAC,IAAI,KAAK,CAAC,IAAI,CAAC,gBAAgB,CAAC,IAAI,CAAC,MAAM,CAAC,EAAE,CAAC;QAC1D,MAAM,IAAI,GAAG,OAAO,CAAC,QAAQ,CAAC,CAAC;QAC/B,OAAO,EAAE,IAAI,EAAE,QAAQ,EAAE,MAAM,EAAE,IAAI,KAAK,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,aAAa,IAAI,EAAE,EAAE,CAAC;IAC5E,CAAC;IACD,OAAO,EAAE,IAAI,EAAE,IAAI,EAAE,MAAM,EAAE,MAAM,EAAE,KAAK,CAAC,GAAG,CAAC,IAAI,EAAE,EAAE,CAAC;AAC1D,CAAC;AAcD;;;;;GAKG;AACH,MAAM,CAAC,KAAK,UAAU,YAAY,CAAC,IAAkB;IACnD,OAAO,MAAM,CAAC,IAAI,EAAE,IAAI,EAAE,UAAU,CAAC,CAAC;AACxC,CAAC;AAED;;;;;;;;;;;GAWG;AACH,MAAM,CAAC,KAAK,UAAU,eAAe,CACnC,IAAkB,EAClB,GAAW;IAEX,MAAM,GAAG,GAAG,GAAG,QAAQ,CAAC,IAAI,CAAC,OAAO,EAAE,GAAG,CAAC,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,GAAG,CAAC;IACnE,MAAM,OAAO,GAAG,MAAM,MAAM,CAAC,IAAI,EAAE,IAAI,EAAE,GAAG,CAAC,CAAC;IAC9C,IAAI,OAAO,CAAC,IAAI,KAAK,QAAQ;QAAE,OAAO,OAAO,CAAC;IAC9C,OAAO;QACL,IAAI,EAAE,IAAI;QACV,KAAK,EAAE,OAAO,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,UAAU,CAAC,GAAG,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,KAAK,CAAC,GAAG,CAAC,MAAM,CAAC,CAAC;KACtF,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,CAAC,KAAK,UAAU,mBAAmB,CACvC,IAAkB,EAClB,GAAW;IAEX,MAAM,GAAG,GAAG,GAAG,QAAQ,CAAC,IAAI,CAAC,OAAO,EAAE,GAAG,CAAC,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,GAAG,CAAC;IACnE,MAAM,OAAO,GAAG,MAAM,OAAO,CAAC,IAAI,CAAC,OAAO,EAAE,CAAC,MAAM,EAAE,aAAa,EAAE,cAAc,EAAE,eAAe,EAAE,IAAI,EAAE,IAAI,CAAC,MAAM,EAAE,IAAI,EAAE,GAAG,CAAC,CAAC,CAAC;IACpI,IAAI,OAAO,CAAC,UAAU,KAAK,SAAS,IAAI,OAAO,CAAC,IAAI,KAAK,CAAC,IAAI,OAAO,CAAC,UAAU,EAAE,CAAC;QACjF,OAAO,EAAE,IAAI,EAAE,QAAQ,EAAE,MAAM,EAAE,OAAO,CAAC,UAAU,CAAC,CAAC,CAAC,mDAAmD,CAAC,CAAC,CAAC,aAAa,CAAC,OAAO,CAAC,EAAE,CAAC;IACvI,CAAC;IACD,MAAM,SAAS,GAAG,MAAM,OAAO,CAAC,IAAI,CAAC,OAAO,EAAE,CAAC,UAAU,EAAE,UAAU,EAAE,oBAAoB,EAAE,aAAa,EAAE,IAAI,EAAE,IAAI,EAAE,GAAG,CAAC,CAAC,CAAC;IAC9H,IAAI,SAAS,CAAC,UAAU,KAAK,SAAS,IAAI,SAAS,CAAC,IAAI,KAAK,CAAC,IAAI,SAAS,CAAC,UAAU,EAAE,CAAC;QACvF,OAAO,EAAE,IAAI,EAAE,QAAQ,EAAE,MAAM,EAAE,SAAS,CAAC,UAAU,CAAC,CAAC,CAAC,qDAAqD,CAAC,CAAC,CAAC,aAAa,CAAC,SAAS,CAAC,EAAE,CAAC;IAC7I,CAAC;IACD,MAAM,KAAK,GAAG,GAAG,IAAI,CAAC,MAAM,GAAG,GAAG,EAAE,CAAC;IACrC,MAAM,KAAK,GAAG,IAAI,GAAG,EAAU,CAAC;IAChC,KAAK,MAAM,IAAI,IAAI,CAAC,GAAG,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,EAAE,GAAG,SAAS,CAAC,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC,EAAE,CAAC;QAC9E,IAAI,CAAC,IAAI,CAAC,UAAU,CAAC,KAAK,CAAC;YAAE,SAAS;QACtC,MAAM,IAAI,GAAG,IAAI,CAAC,KAAK,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC,CAAE,CAAC;QACrD,IAAI,IAAI,KAAK,EAAE;YAAE,KAAK,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;IACnC,CAAC;IACD,OAAO,EAAE,IAAI,EAAE,IAAI,EAAE,KAAK,EAAE,CAAC;AAC/B,CAAC;AAED;;;;;GAKG;AACH,KAAK,UAAU,MAAM,CAAC,IAAkB,EAAE,IAAiB,EAAE,IAAY;IACvE,MAAM,MAAM,GAAG,MAAM,OAAO,CAAC,IAAI,CAAC,OAAO,EAAE;QACzC,SAAS,EAAE,IAAI,EAAE,IAAI,EAAE,aAAa,EAAE,aAAa,EAAE,IAAI,CAAC,MAAM,EAAE,IAAI,EAAE,GAAG,IAAI,CAAC,MAAM,GAAG,IAAI,EAAE;KAChG,CAAC,CAAC;IACH,IAAI,MAAM,CAAC,UAAU,KAAK,SAAS,IAAI,MAAM,CAAC,IAAI,KAAK,CAAC,IAAI,MAAM,CAAC,UAAU,EAAE,CAAC;QAC9E,OAAO;YACL,IAAI,EAAE,QAAQ;YACd,MAAM,EAAE,MAAM,CAAC,UAAU;gBACvB,CAAC,CAAC,gDAAgD;gBAClD,CAAC,CAAC,aAAa,CAAC,MAAM,CAAC;SAC1B,CAAC;IACJ,CAAC;IACD,OAAO;QACL,IAAI,EAAE,IAAI;QACV,KAAK,EAAE,MAAM,CAAC,GAAG;aACd,KAAK,CAAC,IAAI,CAAC;aACX,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,UAAU,CAAC,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,KAAK,EAAE,CAAC;aACpD,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,KAAK,CAAC,IAAI,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC;KAC3C,CAAC;AACJ,CAAC;AAMD;;;;;GAKG;AACH,MAAM,CAAC,KAAK,UAAU,YAAY,CAAC,IAAkB,EAAE,GAAW;IAChE,OAAO,IAAI,OAAO,CAAe,CAAC,IAAI,EAAE,EAAE;QACxC,MAAM,KAAK,GAAG,KAAK,CAAC,KAAK,EAAE,CAAC,MAAM,EAAE,GAAG,IAAI,CAAC,MAAM,IAAI,IAAI,CAAC,MAAM,GAAG,GAAG,EAAE,CAAC,EAAE;YAC1E,GAAG,EAAE,IAAI,CAAC,OAAO;YACjB,KAAK,EAAE,CAAC,QAAQ,EAAE,MAAM,EAAE,MAAM,CAAC;YACjC,OAAO,EAAE,cAAc;SACxB,CAAC,CAAC;QACH,yEAAyE;QACzE,0EAA0E;QAC1E,yDAAyD;QACzD,MAAM,MAAM,GAAa,EAAE,CAAC;QAC5B,IAAI,IAAI,GAAG,CAAC,CAAC;QACb,IAAI,UAAU,GAAG,KAAK,CAAC;QACvB,KAAK,CAAC,MAAM,CAAC,EAAE,CAAC,MAAM,EAAE,CAAC,KAAa,EAAE,EAAE;YACxC,IAAI,UAAU;gBAAE,OAAO;YACvB,IAAI,IAAI,GAAG,KAAK,CAAC,MAAM,GAAG,mBAAmB,EAAE,CAAC;gBAC9C,UAAU,GAAG,IAAI,CAAC;gBAClB,KAAK,CAAC,IAAI,EAAE,CAAC;gBACb,OAAO;YACT,CAAC;YACD,MAAM,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;YACnB,IAAI,IAAI,KAAK,CAAC,MAAM,CAAC;QACvB,CAAC,CAAC,CAAC;QACH,MAAM,GAAG,GAAG,aAAa,CAAC,KAAK,CAAC,CAAC;QACjC,KAAK,CAAC,EAAE,CAAC,OAAO,EAAE,CAAC,CAAC,EAAE,EAAE,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,QAAQ,EAAE,MAAM,EAAE,6BAA6B,CAAC,CAAC,OAAO,GAAG,EAAE,CAAC,CAAC,CAAC;QACtG,KAAK,CAAC,EAAE,CAAC,OAAO,EAAE,CAAC,IAAI,EAAE,EAAE;YACzB,IAAI,IAAI,KAAK,CAAC,IAAI,UAAU,EAAE,CAAC;gBAC7B,IAAI,CAAC;oBACH,IAAI,EAAE,QAAQ;oBACd,MAAM,EAAE,UAAU;wBAChB,CAAC,CAAC,0CAA0C;wBAC5C,CAAC,CAAC,aAAa,CAAC,EAAE,IAAI,EAAE,GAAG,EAAE,EAAE,EAAE,GAAG,EAAE,GAAG,EAAE,EAAE,UAAU,EAAE,CAAC;iBAC7D,CAAC,CAAC;gBACH,OAAO;YACT,CAAC;YACD,IAAI,CAAC,EAAE,IAAI,EAAE,IAAI,EAAE,KAAK,EAAE,MAAM,CAAC,MAAM,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;QACrD,CAAC,CAAC,CAAC;IACL,CAAC,CAAC,CAAC;AACL,CAAC","sourcesContent":["/**\n * Git-at-a-ref reader for the DOCS repo — the base side of `loam diff`, and\n * the \"what had already shipped\" side of `loam gate --since`.\n *\n * Five questions, all read-only: does this docs directory sit in a git\n * repository and where (`resolveBase`), what did `services/` hold at the base\n * commit (`listBaseTree`), which subdirectories did one docs directory hold\n * there (`listBaseSubdirs` — gate's `features/archive/` question) and which of\n * them differ in the working tree now (`subdirsChangedSince` — its second),\n * and what were one file's bytes there (`showBaseFile`). No checkout, no temp\n * writes — the base state is read straight out of the object store with\n * `rev-parse`/`ls-tree`/`show`, and the comparison with `diff`/`ls-files`.\n *\n * Gate takes diff's doctrine below along with the mechanics: a `--since` ref\n * git cannot answer for is a refusal, never \"nothing was archived since\",\n * because that silence would pass a deploy over every feature it could not\n * see — the same fail-open as a silently empty diff base, one command over.\n *\n * The doctrine here is deliberately NOT provenance's. `../provenance/git.ts`\n * answers every git decline with \"git will not say\" — null, no finding —\n * because provenance has no denominator without git and nothing to report.\n * Diff is the opposite case: without the base there is no honest diff at all,\n * and a silently empty base would report the whole fleet as ADDED — the exact\n * \"green over zero services\" failure `docsRepoReady` exists to prevent, one\n * step later. So every decline travels as a typed outcome the command REFUSES\n * on, carrying git's own words (bounded) so the refusal can say why.\n *\n * What is shared with provenance is the mechanics: the one timeout and the\n * capped stdout reader, so rule 20 (every child spawn bounded) holds by\n * construction.\n */\nimport { spawn } from \"node:child_process\";\nimport { relative, sep } from \"node:path\";\nimport { collectStderr, declineDetail, GIT_TIMEOUT_MS, gitSaid, gitText } from \"../provenance/git.js\";\nimport type { DocsDir } from \"../kernel/ids/dirs.js\";\n\n/**\n * How many bytes one base file may be — the same generosity as\n * `../provenance/git.ts`'s stdout cap, restated here because that constant is\n * private to its module and this one collects BYTES, not text (a base\n * contract's UTF-8-ness is a fact to grade, and `setEncoding(\"utf8\")` would\n * substitute U+FFFD before anyone could check). Past the cap the child is\n * killed and the file reads as unreadable for its subject, never truncated.\n *\n * The question-asking mechanics — `gitText`, `GitAnswer`, `gitSaid`,\n * `declineDetail`, `collectStderr` — are the shared set `../provenance/git.ts`\n * exports: `../provenance/gitq/vouched-ancestor.ts` asks with the\n * same shapes and the opposite consequence (it degrades to \"full read\" where\n * this module's callers REFUSE), and the helpers stay verdict-free so the two\n * doctrines cannot bleed into each other through a shared line.\n */\nconst MAX_BASE_FILE_BYTES = 64 * 1024 * 1024;\n\nexport type BaseResolution =\n  | { kind: \"no-git\"; detail: string }\n  | { kind: \"no-ref\"; detail: string }\n  | { kind: \"ok\"; commit: string; prefix: string };\n\n/**\n * Resolve the base: is `docsDir` inside a git work tree, where does it sit in\n * that repository, and which commit does `ref` name?\n *\n * `--show-prefix` is asked FIRST and is not decoration: a docs repo checked\n * out as a subdirectory of a larger repository (a monorepo's `docs/`) answers\n * every later `ls-tree`/`show` only under that prefix. Dropping it makes every\n * path miss, and a diff whose base paths all miss reports the whole fleet as\n * added — silently, in exactly the repositories big enough to care.\n */\nexport async function resolveBase(docsDir: DocsDir, ref: string): Promise<BaseResolution> {\n  const where = await gitText(docsDir, [\"rev-parse\", \"--show-prefix\"]);\n  if (where.spawnError !== undefined || where.code !== 0) {\n    return { kind: \"no-git\", detail: declineDetail(where) };\n  }\n  // A ref spelled like an option would be parsed as one by git, not resolved\n  // as a revision — refuse it before it reaches an argv. Same reason the MCP\n  // argv boundary refuses '-'-prefixed strings.\n  const spelled = ref.trim();\n  if (spelled === \"\" || spelled.startsWith(\"-\")) {\n    return { kind: \"no-ref\", detail: \"a ref must be a revision name, not empty and not option-shaped.\" };\n  }\n  // `^{commit}` peels an annotated tag to the commit it tags, and refuses a\n  // ref that names any other object kind — a tree or blob sha is not a base\n  // state to diff against.\n  const verified = await gitText(docsDir, [\"rev-parse\", \"--verify\", `${spelled}^{commit}`]);\n  const commit = verified.out.trim();\n  if (verified.code !== 0 || !/^[0-9a-f]{40}$/.test(commit)) {\n    const said = gitSaid(verified);\n    return { kind: \"no-ref\", detail: said === \"\" ? \"\" : `git said: ${said}` };\n  }\n  return { kind: \"ok\", commit, prefix: where.out.trim() };\n}\n\n/** The resolved base every later question is asked against. */\nexport interface ResolvedBase {\n  docsDir: DocsDir;\n  commit: string;\n  /** The docs repo's path inside its repository, `\"\"` or `\"docs/\"`-shaped — `rev-parse --show-prefix`'s answer. */\n  prefix: string;\n}\n\nexport type BaseTreeListing =\n  | { kind: \"ok\"; paths: string[] }\n  | { kind: \"failed\"; detail: string };\n\n/**\n * Every file path under `services/` at the base commit, DOCS-RELATIVE\n * (`services/...`, prefix already stripped — `lsTree` below holds the\n * mechanics both listings share). An empty answer is git ANSWERING — the base\n * commit simply has no `services/` — and only a non-zero exit is a failure.\n */\nexport async function listBaseTree(base: ResolvedBase): Promise<BaseTreeListing> {\n  return lsTree(base, \"-r\", \"services\");\n}\n\n/**\n * The NAMES of the immediate subdirectories of one docs directory at the base\n * commit — `loam gate --since`'s question: which `features/archive/<FEAT>/`\n * directories already existed at the ref, so every other archived feature\n * shipped after it. `dir` is the absolute path a `repo/paths.ts` builder\n * spells (`archiveDir`), made docs-relative here, so the layout keeps its one\n * spelling; the separator is forced to `/` because git paths are slash-joined\n * on every host. `-d` lists trees only, and the trailing slash asks for the\n * directory's CHILDREN rather than the directory entry itself. An empty answer\n * is git answering — the base had no such directory — and only a decline is\n * `failed`, which the caller refuses on, as `listBaseTree`'s callers do.\n */\nexport async function listBaseSubdirs(\n  base: ResolvedBase,\n  dir: string,\n): Promise<{ kind: \"ok\"; names: string[] } | { kind: \"failed\"; detail: string }> {\n  const rel = `${relative(base.docsDir, dir).split(sep).join(\"/\")}/`;\n  const listing = await lsTree(base, \"-d\", rel);\n  if (listing.kind === \"failed\") return listing;\n  return {\n    kind: \"ok\",\n    names: listing.paths.filter((p) => p.startsWith(rel)).map((p) => p.slice(rel.length)),\n  };\n}\n\n/**\n * The NAMES of the immediate subdirectories of one docs directory whose\n * contents differ between the base commit and the WORKING TREE — committed\n * since or not — gate's second `features/archive/` question. A directory that\n * was already there at the ref is not thereby old: `loam unarchive`, an edit\n * and `loam archive` again leave a feature at the very path it shipped from\n * before, and reading presence alone graded that re-shipped feature as one an\n * earlier deploy had already answered for.\n *\n * Not a comparison of tree ids, though `ls-tree` has the ref's: the working\n * tree has no id until somebody commits it, and minting one means writing\n * objects — this module asks git, it never writes. The same two questions as\n * `validate --base`'s scope (`./scope/changed-paths.ts`) instead, narrowed to\n * the one directory: `git diff` for every tracked path that differs from the\n * ref, `--no-renames` so a moved file names the place it left as well as the\n * one it reached, and `ls-files --others` for what nobody has committed yet —\n * the re-archive a pipeline is about to ship is exactly that. Both pathspecs\n * are relative to `docsDir`, where git runs; both listings answer\n * root-relative (`git diff` always, `ls-files` under `--full-name`), so the\n * one prefix strip serves both. A decline is `failed`, and the caller decides\n * which way that fails.\n */\nexport async function subdirsChangedSince(\n  base: ResolvedBase,\n  dir: string,\n): Promise<{ kind: \"ok\"; names: Set<string> } | { kind: \"failed\"; detail: string }> {\n  const rel = `${relative(base.docsDir, dir).split(sep).join(\"/\")}/`;\n  const tracked = await gitText(base.docsDir, [\"diff\", \"--name-only\", \"--no-renames\", \"--no-ext-diff\", \"-z\", base.commit, \"--\", rel]);\n  if (tracked.spawnError !== undefined || tracked.code !== 0 || tracked.overflowed) {\n    return { kind: \"failed\", detail: tracked.overflowed ? \"the changed-path listing exceeded the output cap.\" : declineDetail(tracked) };\n  }\n  const untracked = await gitText(base.docsDir, [\"ls-files\", \"--others\", \"--exclude-standard\", \"--full-name\", \"-z\", \"--\", rel]);\n  if (untracked.spawnError !== undefined || untracked.code !== 0 || untracked.overflowed) {\n    return { kind: \"failed\", detail: untracked.overflowed ? \"the untracked-path listing exceeded the output cap.\" : declineDetail(untracked) };\n  }\n  const under = `${base.prefix}${rel}`;\n  const names = new Set<string>();\n  for (const path of [...tracked.out.split(\"\\0\"), ...untracked.out.split(\"\\0\")]) {\n    if (!path.startsWith(under)) continue;\n    const name = path.slice(under.length).split(\"/\")[0]!;\n    if (name !== \"\") names.add(name);\n  }\n  return { kind: \"ok\", names };\n}\n\n/**\n * The one `ls-tree` both listings ask, DOCS-RELATIVE (prefix already\n * stripped). `--full-tree` anchors both the pathspec and the output at the\n * repository root regardless of cwd, so the one prefix from `resolveBase` is\n * the whole story; `-z` because git quotes non-ASCII paths in line output.\n */\nasync function lsTree(base: ResolvedBase, mode: \"-r\" | \"-d\", root: string): Promise<BaseTreeListing> {\n  const answer = await gitText(base.docsDir, [\n    \"ls-tree\", mode, \"-z\", \"--name-only\", \"--full-tree\", base.commit, \"--\", `${base.prefix}${root}`,\n  ]);\n  if (answer.spawnError !== undefined || answer.code !== 0 || answer.overflowed) {\n    return {\n      kind: \"failed\",\n      detail: answer.overflowed\n        ? \"the base tree listing exceeded the output cap.\"\n        : declineDetail(answer),\n    };\n  }\n  return {\n    kind: \"ok\",\n    paths: answer.out\n      .split(\"\\0\")\n      .filter((p) => p.startsWith(base.prefix) && p !== \"\")\n      .map((p) => p.slice(base.prefix.length)),\n  };\n}\n\nexport type BaseFileRead =\n  | { kind: \"ok\"; bytes: Buffer }\n  | { kind: \"failed\"; detail: string };\n\n/**\n * One base file's bytes, by docs-relative path. Callers only ask for paths\n * `listBaseTree` returned, so there is no \"absent\" arm: a decline here is\n * abnormal and travels as `failed` for per-subject containment — that one\n * subject degrades with the detail, never the whole diff.\n */\nexport async function showBaseFile(base: ResolvedBase, rel: string): Promise<BaseFileRead> {\n  return new Promise<BaseFileRead>((done) => {\n    const child = spawn(\"git\", [\"show\", `${base.commit}:${base.prefix}${rel}`], {\n      cwd: base.docsDir,\n      stdio: [\"ignore\", \"pipe\", \"pipe\"],\n      timeout: GIT_TIMEOUT_MS,\n    });\n    // Bytes, not text: `collectStdout` decodes as UTF-8, and a base contract\n    // whose bytes are NOT UTF-8 must arrive intact so base-state can grade it\n    // unreadable instead of parsing a document nobody wrote.\n    const chunks: Buffer[] = [];\n    let held = 0;\n    let overflowed = false;\n    child.stdout.on(\"data\", (chunk: Buffer) => {\n      if (overflowed) return;\n      if (held + chunk.length > MAX_BASE_FILE_BYTES) {\n        overflowed = true;\n        child.kill();\n        return;\n      }\n      chunks.push(chunk);\n      held += chunk.length;\n    });\n    const err = collectStderr(child);\n    child.on(\"error\", (e) => done({ kind: \"failed\", detail: `git could not be started: ${e.message}.` }));\n    child.on(\"close\", (code) => {\n      if (code !== 0 || overflowed) {\n        done({\n          kind: \"failed\",\n          detail: overflowed\n            ? \"the file exceeds the base-read byte cap.\"\n            : declineDetail({ code, out: \"\", err: err(), overflowed }),\n        });\n        return;\n      }\n      done({ kind: \"ok\", bytes: Buffer.concat(chunks) });\n    });\n  });\n}\n"]}