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

package/dist/core/coherence/events/declared.js

@@ -0,0 +1,191 @@
+/**
+ * What a feature's asyncapi deltas DECLARE, per service — ../declared.ts's
+ * mirror on the event axis, indexed in one walk and graded as it goes.
+ *
+ * The walk owns every check that reads ONE service's pair of contracts: the
+ * feature document's readability (`asyncapi.invalid` suspends the rest, the
+ * unreadableApis discipline), the baseline pins and removal-marker exactness
+ * (./grades.ts, slot-keyed), the removal↔REMOVED-requirement justification
+ * join, and the merge simulation (../retired/merged.ts) the cross-axis
+ * checks grade against. What it cannot answer alone — who still consumes a message, what
+ * other features are adding — lives in ./lookups.ts, and the cross-axis
+ * grading of edges and requirement lines in ./events.ts.
+ *
+ * Slot identity is core/asyncapi/digest.ts's: three sections, and an inline
+ * channel message is channel-slot interior — a marker NESTED on one makes
+ * the channel an EDIT against the channel's pin, never a message removal,
+ * so nothing here reads it as one. A CHANNEL-slot removal, by contrast,
+ * takes its living inline interior with it (SCHEMA.md's decision), so the
+ * justification join counts those inline names as marked: without that, a
+ * message declared only inline was a deadlock — the sanctioned channel
+ * marker graded remove-marker-missing, and the components.messages marker
+ * the error suggested graded remove-target-missing.
+ */
+import { existsSync } from "node:fs";
+import { readFile } from "node:fs/promises";
+import {} from "../../kernel/ids/service.js";
+import { featureSpecPaths, SPEC_AXES } from "../../repo/paths.js";
+import { locateServicePaths } from "../../repo/service-target.js";
+import { parseRequirements } from "../../document/parse.js";
+import { readAsyncapi } from "../../asyncapi/read.js";
+import { gradeBaselines, gradeMarkers } from "./grades.js";
+import { messageRetirements } from "../retired/retirement.js";
+import { eventArrivals } from "../retired/revival/arrivals.js";
+import { readEventPair } from "../retired/event-pair.js";
+/**
+ * The delta's `Publishes:`/`Consumes:` lines for one service, split by
+ * requirement fate — read from BOTH spec files, because the outbox
+ * requirement in arch.spec.md is the canonical home of an event line. A
+ * REMOVED requirement's lines justify removals; everything else's are
+ * claims ./events.ts grades against the contract.
+ */
+export async function deltaEventLines(scope, service, context) {
+    const removed = new Set();
+    const links = [];
+    for (const axis of SPEC_AXES) {
+        const p = featureSpecPaths(scope.featureDir, service)[axis.key];
+        if (!existsSync(p))
+            continue;
+        const reqs = context === undefined
+            ? parseRequirements(await readFile(p, "utf8"))
+            : await context.readRequirements(p);
+        for (const r of reqs) {
+            if (r.kind === "REMOVED") {
+                for (const m of [...r.publishes, ...r.consumes])
+                    removed.add(m);
+                continue;
+            }
+            links.push(...r.publishes.map((m) => ({ direction: "publishes", message: m, requirement: r.name })));
+            links.push(...r.consumes.map((m) => ({ direction: "consumes", message: m, requirement: r.name })));
+        }
+    }
+    return { removed, links };
+}
+export async function declaredEvents(scope, svcNames, issues, context) {
+    const { docsDir, featureDir, featureId } = scope;
+    const featureDocs = new Map();
+    const mergedDocs = new Map();
+    const netRemoved = new Map();
+    const stoppedSending = new Map();
+    const sentAfter = new Map();
+    const links = new Map();
+    const unreadable = new Set();
+    const revivalCandidates = new Map();
+    for (const svc of svcNames) {
+        const featPath = featureSpecPaths(featureDir, svc).asyncapi;
+        const { removed: justifiedMsgs, links: svcLinks } = await deltaEventLines(scope, svc, context);
+        links.set(svc, svcLinks);
+        // The living contract is read only where a question will be asked of it:
+        // no event delta and no REMOVED line means no marker debt and no slot to
+        // grade. The unguarded read was an eager parse per touched service —
+        // paid on every archive, whose gate runs without a FleetContext — for an
+        // answer nothing consumed.
+        if (!existsSync(featPath) && justifiedMsgs.size === 0)
+            continue;
+        const livingPath = (await locateServicePaths(docsDir, svc, context)).asyncapi;
+        const livingDoc = await readAsyncapi(livingPath, context);
+        if (!existsSync(featPath)) {
+            // No event delta — but a REMOVED requirement may still be walking away
+            // from a message the LIVING contract declares, and the marker that
+            // retires the declaration has to ride in the same feature. Only
+            // messages the living contract actually carries are owed one: an event
+            // contract is optional, and a fleet retiring a requirement over a
+            // message no contract declares owes no file.
+            for (const m of justifiedMsgs) {
+                if (livingDoc.unreadable || !livingDoc.messages.some((msg) => msg.name === m))
+                    continue;
+                issues.push({
+                    severity: "error",
+                    code: "asyncapi.remove-marker-missing",
+                    subject: svc,
+                    message: `${svc}: a REMOVED requirement's Publishes:/Consumes: line names '${m}', which the living asyncapi.yaml still declares, but this feature carries no matching x-loam-remove: true marker in specs/${svc}/asyncapi.yaml`,
+                });
+            }
+            continue;
+        }
+        const featDoc = await readAsyncapi(featPath, context);
+        // A feature contract that EXISTS but does not read is a broken document,
+        // not an empty one — openapi.invalid's discipline (../declared.ts),
+        // applied to the event axis: the rest of this service's event checks are
+        // suspended, because every one of them would be an opinion about a
+        // document nobody could open.
+        if (featDoc.unreadable) {
+            unreadable.add(svc);
+            issues.push({
+                severity: "error",
+                code: "asyncapi.invalid",
+                subject: svc,
+                message: `${svc}: this feature's asyncapi.yaml does not read as AsyncAPI 3.0${featDoc.error === undefined ? "" : ` (${featDoc.error})`} — the event axis is unchecked and the merge would have nothing true to write. Fix the document first.`,
+            });
+            continue;
+        }
+        featureDocs.set(svc, featDoc);
+        // Both sides' texts, trees and slots, read the one way rebase's
+        // standalone revival read reads them too (../retired/event-pair.ts owns
+        // the guards: absent living is an answer, unreadable living is not).
+        const read = await readEventPair({ featPath, featDoc, livingPath, livingDoc, service: svc }, context);
+        const { featSlots, livingText } = read;
+        revivalCandidates.set(svc, eventArrivals(read));
+        // The pair's one simulation, which the revival candidates above have
+        // already asked: absent living included, where it is the create branch.
+        const sends = read.merged()?.doc.sent;
+        if (sends !== undefined)
+            sentAfter.set(svc, sends);
+        if (livingText !== undefined) {
+            gradeBaselines({ ...read, svc, featureId }, issues);
+            gradeMarkers(read, svc, issues);
+            // The pair's one simulation — the revival candidates above have already
+            // asked it, comparing it with the living contract.
+            const merged = read.merged()?.doc;
+            if (merged !== undefined) {
+                mergedDocs.set(svc, merged);
+                stoppedSending.set(svc, livingDoc.sent.filter((m) => !merged.sent.includes(m)));
+            }
+        }
+        // The raw marker sets and the NET one (minus relocations) —
+        // ../retired/retirement.ts owns the rule and says why each set exists;
+        // the retired index reads every archived feature through the same
+        // function, against that feature's snapshot pre-image instead of the
+        // living contract on disk.
+        const { markerNames, inlineRetired, redeclared, net } = messageRetirements(featDoc, featSlots, livingDoc);
+        netRemoved.set(svc, net);
+        for (const name of markerNames) {
+            if (redeclared.has(name) || justifiedMsgs.has(name))
+                continue;
+            issues.push({
+                severity: "error",
+                code: "asyncapi.remove-marker-unjustified",
+                subject: svc,
+                message: `${svc}: removal marker for message '${name}' is not justified by a REMOVED requirement's Publishes:/Consumes: line`,
+            });
+        }
+        for (const m of justifiedMsgs) {
+            // Owed only while the living contract still declares the message —
+            // and satisfied by ANY marker taking it out, relocation included: a
+            // message-slot marker naming it, or a channel-slot removal whose
+            // living inline interior declares it (the SCHEMA-sanctioned way to
+            // retire an inline declaration). And owed only while the MERGE would
+            // still declare it: a slot re-keyed to another name takes the message
+            // out with no marker, and none could be written there — the key holds
+            // the re-keyed declaration — so the route `asyncapi.remove-message-
+            // consumed` names (REMOVE the requirement whose Publishes: line names
+            // it) ended in this error, `openapi.remove-marker-missing`'s deadlock
+            // one axis over.
+            if (markerNames.has(m) || inlineRetired.has(m))
+                continue;
+            if (livingDoc.unreadable || !livingDoc.messages.some((msg) => msg.name === m))
+                continue;
+            const after = mergedDocs.get(svc);
+            if (after !== undefined && !after.messages.some((msg) => msg.name === m))
+                continue;
+            issues.push({
+                severity: "error",
+                code: "asyncapi.remove-marker-missing",
+                subject: svc,
+                message: `${svc}: a REMOVED requirement's Publishes:/Consumes: line names '${m}', which the living asyncapi.yaml still declares, but this feature's asyncapi.yaml has no matching x-loam-remove: true marker`,
+            });
+        }
+    }
+    return { featureDocs, mergedDocs, netRemoved, stoppedSending, sentAfter, links, unreadable, revivalCandidates };
+}
+//# sourceMappingURL=declared.js.map

package/dist/core/coherence/events/declared.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"declared.js","sourceRoot":"","sources":["../../../../src/core/coherence/events/declared.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,OAAO,EAAE,UAAU,EAAE,MAAM,SAAS,CAAC;AACrC,OAAO,EAAE,QAAQ,EAAE,MAAM,kBAAkB,CAAC;AAC5C,OAAO,EAAwB,MAAM,6BAA6B,CAAC;AAEnE,OAAO,EAAE,gBAAgB,EAAE,SAAS,EAAE,MAAM,qBAAqB,CAAC;AAClE,OAAO,EAAE,kBAAkB,EAAE,MAAM,8BAA8B,CAAC;AAClE,OAAO,EAAE,iBAAiB,EAAE,MAAM,yBAAyB,CAAC;AAC5D,OAAO,EAAE,YAAY,EAAE,MAAM,wBAAwB,CAAC;AAItD,OAAO,EAAE,cAAc,EAAE,YAAY,EAAE,MAAM,aAAa,CAAC;AAC3D,OAAO,EAAE,kBAAkB,EAAE,MAAM,0BAA0B,CAAC;AAC9D,OAAO,EAAE,aAAa,EAAsB,MAAM,gCAAgC,CAAC;AACnF,OAAO,EAAE,aAAa,EAAE,MAAM,0BAA0B,CAAC;AAyEzD;;;;;;GAMG;AACH,MAAM,CAAC,KAAK,UAAU,eAAe,CACnC,KAAsB,EACtB,OAAwB,EACxB,OAAsB;IAEtB,MAAM,OAAO,GAAG,IAAI,GAAG,EAAU,CAAC;IAClC,MAAM,KAAK,GAAgB,EAAE,CAAC;IAC9B,KAAK,MAAM,IAAI,IAAI,SAAS,EAAE,CAAC;QAC7B,MAAM,CAAC,GAAG,gBAAgB,CAAC,KAAK,CAAC,UAAU,EAAE,OAAO,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;QAChE,IAAI,CAAC,UAAU,CAAC,CAAC,CAAC;YAAE,SAAS;QAC7B,MAAM,IAAI,GAAG,OAAO,KAAK,SAAS;YAChC,CAAC,CAAC,iBAAiB,CAAC,MAAM,QAAQ,CAAC,CAAC,EAAE,MAAM,CAAC,CAAC;YAC9C,CAAC,CAAC,MAAM,OAAO,CAAC,gBAAgB,CAAC,CAAC,CAAC,CAAC;QACtC,KAAK,MAAM,CAAC,IAAI,IAAI,EAAE,CAAC;YACrB,IAAI,CAAC,CAAC,IAAI,KAAK,SAAS,EAAE,CAAC;gBACzB,KAAK,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,SAAS,EAAE,GAAG,CAAC,CAAC,QAAQ,CAAC;oBAAE,OAAO,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC;gBAChE,SAAS;YACX,CAAC;YACD,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,EAAE,SAAS,EAAE,WAAoB,EAAE,OAAO,EAAE,CAAC,EAAE,WAAW,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC;YAC9G,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,EAAE,SAAS,EAAE,UAAmB,EAAE,OAAO,EAAE,CAAC,EAAE,WAAW,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC;QAC9G,CAAC;IACH,CAAC;IACD,OAAO,EAAE,OAAO,EAAE,KAAK,EAAE,CAAC;AAC5B,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,cAAc,CAClC,KAAsB,EACtB,QAA2B,EAC3B,MAAe,EACf,OAAsB;IAEtB,MAAM,EAAE,OAAO,EAAE,UAAU,EAAE,SAAS,EAAE,GAAG,KAAK,CAAC;IACjD,MAAM,WAAW,GAAG,IAAI,GAAG,EAAgC,CAAC;IAC5D,MAAM,UAAU,GAAG,IAAI,GAAG,EAAgC,CAAC;IAC3D,MAAM,UAAU,GAAG,IAAI,GAAG,EAAuB,CAAC;IAClD,MAAM,cAAc,GAAG,IAAI,GAAG,EAAoB,CAAC;IACnD,MAAM,SAAS,GAAG,IAAI,GAAG,EAAsC,CAAC;IAChE,MAAM,KAAK,GAAG,IAAI,GAAG,EAAgC,CAAC;IACtD,MAAM,UAAU,GAAG,IAAI,GAAG,EAAU,CAAC;IACrC,MAAM,iBAAiB,GAAG,IAAI,GAAG,EAAkC,CAAC;IACpE,KAAK,MAAM,GAAG,IAAI,QAAQ,EAAE,CAAC;QAC3B,MAAM,QAAQ,GAAG,gBAAgB,CAAC,UAAU,EAAE,GAAG,CAAC,CAAC,QAAQ,CAAC;QAC5D,MAAM,EAAE,OAAO,EAAE,aAAa,EAAE,KAAK,EAAE,QAAQ,EAAE,GAAG,MAAM,eAAe,CAAC,KAAK,EAAE,GAAG,EAAE,OAAO,CAAC,CAAC;QAC/F,KAAK,CAAC,GAAG,CAAC,GAAG,EAAE,QAAQ,CAAC,CAAC;QACzB,yEAAyE;QACzE,yEAAyE;QACzE,qEAAqE;QACrE,yEAAyE;QACzE,2BAA2B;QAC3B,IAAI,CAAC,UAAU,CAAC,QAAQ,CAAC,IAAI,aAAa,CAAC,IAAI,KAAK,CAAC;YAAE,SAAS;QAChE,MAAM,UAAU,GAAG,CAAC,MAAM,kBAAkB,CAAC,OAAO,EAAE,GAAG,EAAE,OAAO,CAAC,CAAC,CAAC,QAAQ,CAAC;QAC9E,MAAM,SAAS,GAAG,MAAM,YAAY,CAAC,UAAU,EAAE,OAAO,CAAC,CAAC;QAC1D,IAAI,CAAC,UAAU,CAAC,QAAQ,CAAC,EAAE,CAAC;YAC1B,uEAAuE;YACvE,mEAAmE;YACnE,gEAAgE;YAChE,uEAAuE;YACvE,kEAAkE;YAClE,6CAA6C;YAC7C,KAAK,MAAM,CAAC,IAAI,aAAa,EAAE,CAAC;gBAC9B,IAAI,SAAS,CAAC,UAAU,IAAI,CAAC,SAAS,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,GAAG,CAAC,IAAI,KAAK,CAAC,CAAC;oBAAE,SAAS;gBACxF,MAAM,CAAC,IAAI,CAAC;oBACV,QAAQ,EAAE,OAAO;oBACjB,IAAI,EAAE,gCAAgC;oBACtC,OAAO,EAAE,GAAG;oBACZ,OAAO,EAAE,GAAG,GAAG,8DAA8D,CAAC,8HAA8H,GAAG,gBAAgB;iBAChO,CAAC,CAAC;YACL,CAAC;YACD,SAAS;QACX,CAAC;QACD,MAAM,OAAO,GAAG,MAAM,YAAY,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAC;QACtD,yEAAyE;QACzE,oEAAoE;QACpE,yEAAyE;QACzE,mEAAmE;QACnE,8BAA8B;QAC9B,IAAI,OAAO,CAAC,UAAU,EAAE,CAAC;YACvB,UAAU,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;YACpB,MAAM,CAAC,IAAI,CAAC;gBACV,QAAQ,EAAE,OAAO;gBACjB,IAAI,EAAE,kBAAkB;gBACxB,OAAO,EAAE,GAAG;gBACZ,OAAO,EAAE,GAAG,GAAG,+DAA+D,OAAO,CAAC,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,KAAK,OAAO,CAAC,KAAK,GAAG,wGAAwG;aAC/O,CAAC,CAAC;YACH,SAAS;QACX,CAAC;QACD,WAAW,CAAC,GAAG,CAAC,GAAG,EAAE,OAAO,CAAC,CAAC;QAE9B,gEAAgE;QAChE,wEAAwE;QACxE,qEAAqE;QACrE,MAAM,IAAI,GAAG,MAAM,aAAa,CAAC,EAAE,QAAQ,EAAE,OAAO,EAAE,UAAU,EAAE,SAAS,EAAE,OAAO,EAAE,GAAG,EAAE,EAAE,OAAO,CAAC,CAAC;QACtG,MAAM,EAAE,SAAS,EAAE,UAAU,EAAE,GAAG,IAAI,CAAC;QACvC,iBAAiB,CAAC,GAAG,CAAC,GAAG,EAAE,aAAa,CAAC,IAAI,CAAC,CAAC,CAAC;QAChD,qEAAqE;QACrE,wEAAwE;QACxE,MAAM,KAAK,GAAG,IAAI,CAAC,MAAM,EAAE,EAAE,GAAG,CAAC,IAAI,CAAC;QACtC,IAAI,KAAK,KAAK,SAAS;YAAE,SAAS,CAAC,GAAG,CAAC,GAAG,EAAE,KAAK,CAAC,CAAC;QAEnD,IAAI,UAAU,KAAK,SAAS,EAAE,CAAC;YAC7B,cAAc,CAAC,EAAE,GAAG,IAAI,EAAE,GAAG,EAAE,SAAS,EAAE,EAAE,MAAM,CAAC,CAAC;YACpD,YAAY,CAAC,IAAI,EAAE,GAAG,EAAE,MAAM,CAAC,CAAC;YAChC,wEAAwE;YACxE,mDAAmD;YACnD,MAAM,MAAM,GAAG,IAAI,CAAC,MAAM,EAAE,EAAE,GAAG,CAAC;YAClC,IAAI,MAAM,KAAK,SAAS,EAAE,CAAC;gBACzB,UAAU,CAAC,GAAG,CAAC,GAAG,EAAE,MAAM,CAAC,CAAC;gBAC5B,cAAc,CAAC,GAAG,CAAC,GAAG,EAAE,SAAS,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,MAAM,CAAC,IAAI,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;YAClF,CAAC;QACH,CAAC;QAED,4DAA4D;QAC5D,uEAAuE;QACvE,kEAAkE;QAClE,qEAAqE;QACrE,2BAA2B;QAC3B,MAAM,EAAE,WAAW,EAAE,aAAa,EAAE,UAAU,EAAE,GAAG,EAAE,GAAG,kBAAkB,CAAC,OAAO,EAAE,SAAS,EAAE,SAAS,CAAC,CAAC;QAC1G,UAAU,CAAC,GAAG,CAAC,GAAG,EAAE,GAAG,CAAC,CAAC;QAEzB,KAAK,MAAM,IAAI,IAAI,WAAW,EAAE,CAAC;YAC/B,IAAI,UAAU,CAAC,GAAG,CAAC,IAAI,CAAC,IAAI,aAAa,CAAC,GAAG,CAAC,IAAI,CAAC;gBAAE,SAAS;YAC9D,MAAM,CAAC,IAAI,CAAC;gBACV,QAAQ,EAAE,OAAO;gBACjB,IAAI,EAAE,oCAAoC;gBAC1C,OAAO,EAAE,GAAG;gBACZ,OAAO,EAAE,GAAG,GAAG,iCAAiC,IAAI,yEAAyE;aAC9H,CAAC,CAAC;QACL,CAAC;QACD,KAAK,MAAM,CAAC,IAAI,aAAa,EAAE,CAAC;YAC9B,mEAAmE;YACnE,oEAAoE;YACpE,iEAAiE;YACjE,mEAAmE;YACnE,qEAAqE;YACrE,sEAAsE;YACtE,sEAAsE;YACtE,oEAAoE;YACpE,sEAAsE;YACtE,sEAAsE;YACtE,iBAAiB;YACjB,IAAI,WAAW,CAAC,GAAG,CAAC,CAAC,CAAC,IAAI,aAAa,CAAC,GAAG,CAAC,CAAC,CAAC;gBAAE,SAAS;YACzD,IAAI,SAAS,CAAC,UAAU,IAAI,CAAC,SAAS,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,GAAG,CAAC,IAAI,KAAK,CAAC,CAAC;gBAAE,SAAS;YACxF,MAAM,KAAK,GAAG,UAAU,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;YAClC,IAAI,KAAK,KAAK,SAAS,IAAI,CAAC,KAAK,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,GAAG,CAAC,IAAI,KAAK,CAAC,CAAC;gBAAE,SAAS;YACnF,MAAM,CAAC,IAAI,CAAC;gBACV,QAAQ,EAAE,OAAO;gBACjB,IAAI,EAAE,gCAAgC;gBACtC,OAAO,EAAE,GAAG;gBACZ,OAAO,EAAE,GAAG,GAAG,8DAA8D,CAAC,+HAA+H;aAC9M,CAAC,CAAC;QACL,CAAC;IACH,CAAC;IACD,OAAO,EAAE,WAAW,EAAE,UAAU,EAAE,UAAU,EAAE,cAAc,EAAE,SAAS,EAAE,KAAK,EAAE,UAAU,EAAE,iBAAiB,EAAE,CAAC;AAClH,CAAC","sourcesContent":["/**\n * What a feature's asyncapi deltas DECLARE, per service — ../declared.ts's\n * mirror on the event axis, indexed in one walk and graded as it goes.\n *\n * The walk owns every check that reads ONE service's pair of contracts: the\n * feature document's readability (`asyncapi.invalid` suspends the rest, the\n * unreadableApis discipline), the baseline pins and removal-marker exactness\n * (./grades.ts, slot-keyed), the removal↔REMOVED-requirement justification\n * join, and the merge simulation (../retired/merged.ts) the cross-axis\n * checks grade against. What it cannot answer alone — who still consumes a message, what\n * other features are adding — lives in ./lookups.ts, and the cross-axis\n * grading of edges and requirement lines in ./events.ts.\n *\n * Slot identity is core/asyncapi/digest.ts's: three sections, and an inline\n * channel message is channel-slot interior — a marker NESTED on one makes\n * the channel an EDIT against the channel's pin, never a message removal,\n * so nothing here reads it as one. A CHANNEL-slot removal, by contrast,\n * takes its living inline interior with it (SCHEMA.md's decision), so the\n * justification join counts those inline names as marked: without that, a\n * message declared only inline was a deadlock — the sanctioned channel\n * marker graded remove-marker-missing, and the components.messages marker\n * the error suggested graded remove-target-missing.\n */\nimport { existsSync } from \"node:fs\";\nimport { readFile } from \"node:fs/promises\";\nimport { type PathableService } from \"../../kernel/ids/service.js\";\nimport type { Issue } from \"../../vocabulary/issue.js\";\nimport { featureSpecPaths, SPEC_AXES } from \"../../repo/paths.js\";\nimport { locateServicePaths } from \"../../repo/service-target.js\";\nimport { parseRequirements } from \"../../document/parse.js\";\nimport { readAsyncapi } from \"../../asyncapi/read.js\";\nimport type { AsyncapiDoc } from \"../../asyncapi/model.js\";\nimport type { FleetContext } from \"../../fleet-context.js\";\nimport type { DocsDir, FeatureDir } from \"../../kernel/ids/dirs.js\";\nimport { gradeBaselines, gradeMarkers } from \"./grades.js\";\nimport { messageRetirements } from \"../retired/retirement.js\";\nimport { eventArrivals, type EventArrivals } from \"../retired/revival/arrivals.js\";\nimport { readEventPair } from \"../retired/event-pair.js\";\n\n/** The three facts this walk needs about the feature it is reading. */\nexport interface EventDeltaScope {\n  docsDir: DocsDir;\n  featureDir: FeatureDir;\n  featureId: string;\n}\n\n/** One delta requirement's `Publishes:`/`Consumes:` claim — what ./events.ts grades against the contract. */\nexport interface EventLink {\n  direction: \"publishes\" | \"consumes\";\n  message: string;\n  requirement: string;\n}\n\n/** Everything one feature's asyncapi deltas say about their own services. */\nexport interface DeclaredEvents {\n  /** Per touched service: the feature delta's parse — present only where the file exists and reads. */\n  featureDocs: Map<PathableService, AsyncapiDoc>;\n  /**\n   * Per touched service: the living contract as the MERGE would leave it\n   * (../retired/merged.ts) — present where a feature delta sits over a\n   * readable living contract and the simulation had an answer. What `declares()` and\n   * the consumer gate's wire half read, so the gate grades the post-archive\n   * contract rather than the union of two documents one of which is leaving.\n   */\n  mergedDocs: Map<PathableService, AsyncapiDoc>;\n  /**\n   * Per service: message names this feature genuinely retires — message-slot\n   * markers plus a removed channel's living INLINE interior (SCHEMA.md:\n   * retiring a whole channel retires its inline messages with it), minus\n   * redeclarations.\n   */\n  netRemoved: Map<string, Set<string>>;\n  /**\n   * Per service: messages the living contract SENDS that the merged one\n   * would not — a channel or operation removal, or an edit, stopping\n   * production while the declaration may well survive. The wire half of the\n   * consumer question (./events.ts); empty where no simulation ran.\n   */\n  stoppedSending: Map<string, string[]>;\n  /**\n   * Per touched service whose feature asyncapi.yaml reads: the names its\n   * contract would SEND once the archive writes it — the merged contract over a\n   * readable living one, and the create branch's document where none exists\n   * (a feature may move production to a service with no contract yet). Absent\n   * where the simulation stands down: an unreadable living contract, or a pair\n   * the merge refuses. What the consumer gate asks for the senders that keep a\n   * message produced after this merge (./events.ts), so a service absent here\n   * that this feature carries a delta for vouches for nothing.\n   */\n  sentAfter: Map<PathableService, readonly string[]>;\n  /**\n   * Per service in the walk: the delta's non-REMOVED `Publishes:`/`Consumes:`\n   * lines — read once HERE and graded in ./events.ts, the indexed-in-one-walk\n   * rule this record exists for (the same lines used to be re-read and\n   * re-parsed per question on the context-less archive-gate path).\n   */\n  links: Map<PathableService, EventLink[]>;\n  /** Services whose FEATURE asyncapi.yaml exists but does not parse — every event check suspends for them. */\n  unreadable: Set<string>;\n  /**\n   * Per touched service: the slots the delta declares that the living\n   * contract lacks, and the message names the contract the archive would\n   * write declares where the living one does not — new, or a revival of what\n   * an archived feature retired or moved away, which the living contract\n   * alone cannot tell apart. ./events.ts asks the retired index (../retired/)\n   * only when one of these is non-empty.\n   */\n  revivalCandidates: Map<PathableService, EventArrivals>;\n}\n\n/**\n * The delta's `Publishes:`/`Consumes:` lines for one service, split by\n * requirement fate — read from BOTH spec files, because the outbox\n * requirement in arch.spec.md is the canonical home of an event line. A\n * REMOVED requirement's lines justify removals; everything else's are\n * claims ./events.ts grades against the contract.\n */\nexport async function deltaEventLines(\n  scope: EventDeltaScope,\n  service: PathableService,\n  context?: FleetContext,\n): Promise<{ removed: Set<string>; links: EventLink[] }> {\n  const removed = new Set<string>();\n  const links: EventLink[] = [];\n  for (const axis of SPEC_AXES) {\n    const p = featureSpecPaths(scope.featureDir, service)[axis.key];\n    if (!existsSync(p)) continue;\n    const reqs = context === undefined\n      ? parseRequirements(await readFile(p, \"utf8\"))\n      : await context.readRequirements(p);\n    for (const r of reqs) {\n      if (r.kind === \"REMOVED\") {\n        for (const m of [...r.publishes, ...r.consumes]) removed.add(m);\n        continue;\n      }\n      links.push(...r.publishes.map((m) => ({ direction: \"publishes\" as const, message: m, requirement: r.name })));\n      links.push(...r.consumes.map((m) => ({ direction: \"consumes\" as const, message: m, requirement: r.name })));\n    }\n  }\n  return { removed, links };\n}\n\nexport async function declaredEvents(\n  scope: EventDeltaScope,\n  svcNames: PathableService[],\n  issues: Issue[],\n  context?: FleetContext,\n): Promise<DeclaredEvents> {\n  const { docsDir, featureDir, featureId } = scope;\n  const featureDocs = new Map<PathableService, AsyncapiDoc>();\n  const mergedDocs = new Map<PathableService, AsyncapiDoc>();\n  const netRemoved = new Map<string, Set<string>>();\n  const stoppedSending = new Map<string, string[]>();\n  const sentAfter = new Map<PathableService, readonly string[]>();\n  const links = new Map<PathableService, EventLink[]>();\n  const unreadable = new Set<string>();\n  const revivalCandidates = new Map<PathableService, EventArrivals>();\n  for (const svc of svcNames) {\n    const featPath = featureSpecPaths(featureDir, svc).asyncapi;\n    const { removed: justifiedMsgs, links: svcLinks } = await deltaEventLines(scope, svc, context);\n    links.set(svc, svcLinks);\n    // The living contract is read only where a question will be asked of it:\n    // no event delta and no REMOVED line means no marker debt and no slot to\n    // grade. The unguarded read was an eager parse per touched service —\n    // paid on every archive, whose gate runs without a FleetContext — for an\n    // answer nothing consumed.\n    if (!existsSync(featPath) && justifiedMsgs.size === 0) continue;\n    const livingPath = (await locateServicePaths(docsDir, svc, context)).asyncapi;\n    const livingDoc = await readAsyncapi(livingPath, context);\n    if (!existsSync(featPath)) {\n      // No event delta — but a REMOVED requirement may still be walking away\n      // from a message the LIVING contract declares, and the marker that\n      // retires the declaration has to ride in the same feature. Only\n      // messages the living contract actually carries are owed one: an event\n      // contract is optional, and a fleet retiring a requirement over a\n      // message no contract declares owes no file.\n      for (const m of justifiedMsgs) {\n        if (livingDoc.unreadable || !livingDoc.messages.some((msg) => msg.name === m)) continue;\n        issues.push({\n          severity: \"error\",\n          code: \"asyncapi.remove-marker-missing\",\n          subject: svc,\n          message: `${svc}: a REMOVED requirement's Publishes:/Consumes: line names '${m}', which the living asyncapi.yaml still declares, but this feature carries no matching x-loam-remove: true marker in specs/${svc}/asyncapi.yaml`,\n        });\n      }\n      continue;\n    }\n    const featDoc = await readAsyncapi(featPath, context);\n    // A feature contract that EXISTS but does not read is a broken document,\n    // not an empty one — openapi.invalid's discipline (../declared.ts),\n    // applied to the event axis: the rest of this service's event checks are\n    // suspended, because every one of them would be an opinion about a\n    // document nobody could open.\n    if (featDoc.unreadable) {\n      unreadable.add(svc);\n      issues.push({\n        severity: \"error\",\n        code: \"asyncapi.invalid\",\n        subject: svc,\n        message: `${svc}: this feature's asyncapi.yaml does not read as AsyncAPI 3.0${featDoc.error === undefined ? \"\" : ` (${featDoc.error})`} — the event axis is unchecked and the merge would have nothing true to write. Fix the document first.`,\n      });\n      continue;\n    }\n    featureDocs.set(svc, featDoc);\n\n    // Both sides' texts, trees and slots, read the one way rebase's\n    // standalone revival read reads them too (../retired/event-pair.ts owns\n    // the guards: absent living is an answer, unreadable living is not).\n    const read = await readEventPair({ featPath, featDoc, livingPath, livingDoc, service: svc }, context);\n    const { featSlots, livingText } = read;\n    revivalCandidates.set(svc, eventArrivals(read));\n    // The pair's one simulation, which the revival candidates above have\n    // already asked: absent living included, where it is the create branch.\n    const sends = read.merged()?.doc.sent;\n    if (sends !== undefined) sentAfter.set(svc, sends);\n\n    if (livingText !== undefined) {\n      gradeBaselines({ ...read, svc, featureId }, issues);\n      gradeMarkers(read, svc, issues);\n      // The pair's one simulation — the revival candidates above have already\n      // asked it, comparing it with the living contract.\n      const merged = read.merged()?.doc;\n      if (merged !== undefined) {\n        mergedDocs.set(svc, merged);\n        stoppedSending.set(svc, livingDoc.sent.filter((m) => !merged.sent.includes(m)));\n      }\n    }\n\n    // The raw marker sets and the NET one (minus relocations) —\n    // ../retired/retirement.ts owns the rule and says why each set exists;\n    // the retired index reads every archived feature through the same\n    // function, against that feature's snapshot pre-image instead of the\n    // living contract on disk.\n    const { markerNames, inlineRetired, redeclared, net } = messageRetirements(featDoc, featSlots, livingDoc);\n    netRemoved.set(svc, net);\n\n    for (const name of markerNames) {\n      if (redeclared.has(name) || justifiedMsgs.has(name)) continue;\n      issues.push({\n        severity: \"error\",\n        code: \"asyncapi.remove-marker-unjustified\",\n        subject: svc,\n        message: `${svc}: removal marker for message '${name}' is not justified by a REMOVED requirement's Publishes:/Consumes: line`,\n      });\n    }\n    for (const m of justifiedMsgs) {\n      // Owed only while the living contract still declares the message —\n      // and satisfied by ANY marker taking it out, relocation included: a\n      // message-slot marker naming it, or a channel-slot removal whose\n      // living inline interior declares it (the SCHEMA-sanctioned way to\n      // retire an inline declaration). And owed only while the MERGE would\n      // still declare it: a slot re-keyed to another name takes the message\n      // out with no marker, and none could be written there — the key holds\n      // the re-keyed declaration — so the route `asyncapi.remove-message-\n      // consumed` names (REMOVE the requirement whose Publishes: line names\n      // it) ended in this error, `openapi.remove-marker-missing`'s deadlock\n      // one axis over.\n      if (markerNames.has(m) || inlineRetired.has(m)) continue;\n      if (livingDoc.unreadable || !livingDoc.messages.some((msg) => msg.name === m)) continue;\n      const after = mergedDocs.get(svc);\n      if (after !== undefined && !after.messages.some((msg) => msg.name === m)) continue;\n      issues.push({\n        severity: \"error\",\n        code: \"asyncapi.remove-marker-missing\",\n        subject: svc,\n        message: `${svc}: a REMOVED requirement's Publishes:/Consumes: line names '${m}', which the living asyncapi.yaml still declares, but this feature's asyncapi.yaml has no matching x-loam-remove: true marker`,\n      });\n    }\n  }\n  return { featureDocs, mergedDocs, netRemoved, stoppedSending, sentAfter, links, unreadable, revivalCandidates };\n}\n"]}

package/dist/core/coherence/events/events.js

@@ -0,0 +1,335 @@
+/**
+ * The event axis of the feature gate: do the C4 delta's tagged edges, the
+ * requirement deltas' `Publishes:`/`Consumes:` lines, and the asyncapi
+ * contracts agree about what each service puts on the wire?
+ *
+ * The package's orchestrator, called once from featureCoherence with the
+ * delta facts it already holds (tagged relationships and the element
+ * resolver): ./declared.ts walks the feature's own contracts and grades
+ * what one service's pair of documents can settle; ./lookups.ts answers the
+ * in-flight question lazily, and the consumer index (core/consumers/) who
+ * still consumes a message; this module joins the three axes — the exact
+ * shape coherence.ts gives the operation join, on the message name.
+ *
+ * A package of its own rather than lines in coherence.ts because that file
+ * ran at its 300-line limit before the event axis existed; the seam is
+ * real, not cosmetic — everything here joins on a message name, nothing
+ * there does.
+ */
+import {} from "../../c4/likec4.js";
+import { eventKeys, unboundSentence } from "../../c4/direction/direction.js";
+import {} from "../../kernel/ids/service.js";
+import { locateServicePaths } from "../../repo/service-target.js";
+import { enumeratedServiceIndex } from "../../repo/service-target.js";
+import { readAsyncapi } from "../../asyncapi/read.js";
+import { declaredEvents } from "./declared.js";
+import { eventLookups } from "./lookups.js";
+import { revivedEvents } from "../retired/revival/revived.js";
+import { nothingStill, refusalDetails, refusalMessage, stillNamed } from "../consumed/refusal.js";
+import { fleetSendersAfter, unproducedIssues } from "./produced.js";
+export async function eventCoherence(request) {
+    const { scope, svcNames, taggedRels, svcOf, context, consumers } = request;
+    const issues = [];
+    const declared = await declaredEvents(scope, svcNames, issues, context);
+    const lookups = eventLookups({ docsDir: scope.docsDir, featureId: scope.featureId }, context);
+    // Who would still name a message after this merge: the consumer index's
+    // consumers, and its `own` — the provider's own `Publishes:` lines as the
+    // merge leaves them. That is the event twin of the overwrite's own-requirement
+    // scan: a message re-keyed or no longer sent while the provider's living
+    // requirement still says it `Publishes:` it archived at exit 0, and the next
+    // `validate --all` reported `spec-event.message-undefined` against the
+    // provider (review 2026-10-12, finding 3) — a REMOVED requirement justifies a
+    // marker, but nothing asks a re-key or a turned-around operation for one.
+    // A consumer document nobody could read or place refuses too, as on the
+    // contract axis (../consumed/refusal.ts).
+    //
+    // But a CONSUMER is stranded only when nothing would send the message after
+    // this merge — no service, and no #external element whose edge publishes it.
+    // That is the rule `spine.message-unproduced` grades a consumer by — it stays
+    // quiet over an outside producer (`externalProducerOf`,
+    // core/c4/resolve/external.ts) — and the one `loam diff` asks first
+    // (`producers`, then `externalProducer`, core/diff/semantic.ts).
+    // Counting every consumer "whoever its producer is" refused a retirement from
+    // one of two senders over the other sender's own consumes edge, and told the
+    // author to drop it, while `loam diff` called the same removal a warning
+    // ("still sent by …") and the next `validate --all` was clean (the
+    // verification of the consumer fixes, N2). Counting the fleet's senders alone
+    // then refused a retirement from a message's only fleet sender while an
+    // #external element still published it, and `loam diff` called the archived
+    // removal `diff.message-removed-consumed`, while the next `validate --all` was
+    // clean again (the verification of N1–N3, D1). The provider's OWN documents are
+    // another matter: the spine and validate grade them against the provider's
+    // own contract, so they strand whoever else sends the message, and `own`
+    // still refuses beside a surviving sender.
+    //
+    // The senders are asked of the MERGE, never of the living fleet alone:
+    // `producers` reads the fleet as it stands, so a feature retiring the message
+    // from both senders would let each one pass on the other's living contract.
+    // A service this feature carries an event delta for sends what the
+    // simulation leaves it (`declared.sentAfter`), or vouches for nothing; every
+    // other service sends what its living contract does. Positive evidence only,
+    // as `producers` is: an unreadable contract, or a merge that stood down,
+    // never keeps a message produced. The outside producer is the living map's
+    // edge and tag, which the landscape merge cannot take away (it only adds to
+    // the map), asked over the directories the merge leaves: each `specs/<svc>/`
+    // of this feature becomes a `services/<svc>/`, and a directory the #external
+    // element resolves to outranks its tag, so a feature onboarding the outside
+    // system as a service takes the producer away. Asked over the directories
+    // as they stood, the gate passed that retirement while the next `loam diff`
+    // reported `diff.message-removed-consumed` and `validate --all`
+    // `spine.message-unproduced` (the verification of D1, X2). One this
+    // feature's own C4 delta would draw is not counted, so that shape errs
+    // toward refusing — `--approve`, or draw the edge in the living map. The
+    // consumer check in ./produced.ts DOES count it, deliberately: there the
+    // closed direction is the other one (that module says why), and the fleet
+    // half of the senders is the one helper both read.
+    const sendersAfter = async (svc, message) => {
+        const fleet = (await fleetSendersAfter(declared, consumers, message)).filter((id) => id !== svc);
+        const outside = await consumers.externalProducer(message);
+        return outside === null ? fleet : [...fleet, `${outside} (#external)`];
+    };
+    const still = async (svc, message) => {
+        const answer = await consumers.messageConsumers(svc, message);
+        const senders = await sendersAfter(svc, message);
+        return { senders, found: stillNamed(senders.length === 0 ? answer : { ...answer, victims: [], suspended: [] }) };
+    };
+    // The landscape merge only ADDS edges, so an edge is dropped in the living map
+    // itself — a consumer's consumes edge, or the provider's own publishes edge,
+    // which the spine grades on its source (`own`, core/consumers/consumers.ts).
+    const route = `drop its consumes edge, or drop or redraw its publishes edge, in the architecture/ project, MODIFY or REMOVE the requirement whose Consumes:/Publishes: line names it in this feature's specs/<service>/ delta`;
+    // With a sender left only the provider's own documents are named, so the
+    // remedy is theirs alone — telling the author to drop a consumer's edge
+    // there is the false route this gate used to give.
+    const ownRoute = (svc) => `drop or redraw its publishes edge in the architecture/ project, or MODIFY or REMOVE the requirement whose Publishes: line names it in this feature's specs/${svc}/ delta`;
+    const ownOnly = (svc, senders) => `${senders.join(", ")} would still send it after this merge, so its consumers keep a producer, but ${svc}'s own documents would still name it`;
+    // The route a consumer's refusal gains: another sender keeps the message
+    // produced, and one this feature adds counts (`declared.sentAfter`); so does
+    // the #external element that publishes it, drawn in the living map — the one
+    // place `sendersAfter` reads an outside producer from — unless this feature
+    // makes it a service. The route says so: a feature onboarding the gateway is
+    // told no #external element publishes the message while its living map
+    // draws one doing exactly that, and the way out is the first route, the new
+    // service's own send operation in its specs/<service>/ delta.
+    const anotherSender = "keep another service sending it (an action: send operation in its asyncapi.yaml, living or in this feature's specs/<service>/ delta) or an #external element publishing it (a publishes edge from it in the living architecture/ project; one whose element this feature's specs/<service>/ makes a service no longer counts)";
+    // Retiring a message the fleet still consumes — openapi.remove-op-consumed's
+    // twin, and like it a question neither exactness nor justification asks:
+    // the merge deletes the declaration while the consumes edge and the other
+    // repo's requirement stay, so the next `validate --all` breaks on a
+    // repository whose author was never in this feature.
+    for (const [svc, net] of declared.netRemoved) {
+        for (const message of net) {
+            const { found, senders } = await still(svc, message);
+            if (nothingStill(found))
+                continue;
+            const lost = `this feature retires message '${message}'`;
+            issues.push({
+                severity: "error",
+                code: "asyncapi.remove-message-consumed",
+                subject: svc,
+                details: refusalDetails(found),
+                message: refusalMessage(found, {
+                    subject: svc,
+                    lost,
+                    verb: "name",
+                    named: (list) => senders.length === 0
+                        ? `${svc}: ${lost}, and no readable contract would still send it after this merge, nor does an #external element publish it, but the fleet would still name it — ${list}. Retire each in the same change (${route}), ${anotherSender}, or archive with --approve to break it deliberately.`
+                        : `${svc}: ${lost}; ${ownOnly(svc, senders)} — ${list}. Retire each in the same change (${ownRoute(svc)}), or archive with --approve to break it deliberately.`,
+                }),
+            });
+        }
+    }
+    // The WIRE half of the same question: a channel or operation removal (or
+    // an edit) can stop the service SENDING a message whose declaration
+    // survives — the merge applies cleanly, and the next `validate --all`
+    // breaks on the consumer's repository (spine.message-unproduced) exactly
+    // as a deleted declaration would. Asked of the simulated merge's sent-set
+    // diff; a name the net-removal loop above already asked keeps one finding.
+    for (const [svc, stopped] of declared.stoppedSending) {
+        const net = declared.netRemoved.get(svc);
+        for (const message of stopped) {
+            if (net?.has(message) === true)
+                continue;
+            const { found, senders } = await still(svc, message);
+            if (nothingStill(found))
+                continue;
+            const lost = `after this feature's merge, ${svc}'s asyncapi.yaml would no longer declare an action: send operation for '${message}'`;
+            issues.push({
+                severity: "error",
+                code: "asyncapi.remove-message-consumed",
+                subject: svc,
+                details: refusalDetails(found),
+                message: refusalMessage(found, {
+                    subject: svc,
+                    lost,
+                    verb: "name",
+                    named: (list) => senders.length === 0
+                        ? `${svc}: ${lost}, and no other readable contract would send it either, nor does an #external element publish it, but the fleet would still name it — ${list}. Keep an operation sending it, ${anotherSender}, retire each in the same change (${route}), or archive with --approve to break it deliberately.`
+                        : `${svc}: ${lost}; ${ownOnly(svc, senders)} — ${list}. Keep an operation sending it, retire each in the same change (${ownRoute(svc)}), or archive with --approve to break it deliberately.`,
+                }),
+            });
+        }
+    }
+    // A revival: a slot or message this delta declares that the living
+    // contract no longer has because an ARCHIVED feature retired it, or a
+    // message name declared again at a key an archived feature took it out of
+    // — the contract axis's `openapi.op-revived`, on the slot and the message
+    // name (../retired/revival/revived.ts). Asked of the index only when the merged
+    // contract declares something the living one does not.
+    for (const [svc, arrived] of declared.revivalCandidates) {
+        if (arrived.slots.length === 0 && arrived.messages.length === 0)
+            continue;
+        issues.push(...revivedEvents(svc, arrived, await request.retired()));
+    }
+    // Two features declaring one (service, message): both deltas apply
+    // cleanly, so whichever archives second replaces the other's declaration
+    // wholesale — delta.added-conflict's shape on the message join.
+    for (const [svc, doc] of declared.featureDocs) {
+        for (const m of doc.messages) {
+            if (m.remove === true)
+                continue;
+            const other = await lookups.messageDefinedElsewhere(svc, m.name);
+            if (other === undefined)
+                continue;
+            issues.push({
+                severity: "warn",
+                code: "asyncapi.message-conflict",
+                subject: svc,
+                message: `${svc}: this feature declares message '${m.name}', which in-flight ${other} also adds or edits — whichever archives second replaces the other's declaration wholesale; coordinate before either ships`,
+            });
+        }
+    }
+    // The bound service's contract as the feature would leave it. Where the
+    // feature carries a delta over a readable living contract, that is the
+    // SIMULATED merge (declared.mergedDocs): a slot the delta retires or edits
+    // away stops answering here BEFORE archive — a leftover Publishes: line on
+    // a surviving requirement used to pass this gate on living's say-so, then
+    // break `validate --all` on the post-archive docs. Everywhere the
+    // simulation has no answer — no delta for the service, a side that does
+    // not read, a document the merge refuses — the feature ∪ living union
+    // stands in, which can only be too lenient, never wrongly red; the living
+    // side is read lazily per service, since an edge may bind a service the
+    // feature carries no specs/ directory for.
+    const livingDocs = new Map();
+    const livingOf = async (svc) => {
+        let doc = livingDocs.get(svc);
+        if (doc === undefined) {
+            doc = await readAsyncapi((await locateServicePaths(scope.docsDir, svc, context)).asyncapi, context);
+            livingDocs.set(svc, doc);
+        }
+        return doc;
+    };
+    // undefined = no verdict: an unreadable LIVING contract proves nothing
+    // about the message (validate's asyncapi.invalid owns that file), and
+    // grading against its empty parse would blame every edge for one broken
+    // document.
+    const declares = async (svc, direction, message) => {
+        const merged = declared.mergedDocs.get(svc);
+        if (merged !== undefined) {
+            return direction === "publishes" ? merged.sent.includes(message) : merged.received.includes(message);
+        }
+        const living = await livingOf(svc);
+        if (living.unreadable)
+            return undefined;
+        const feat = declared.featureDocs.get(svc);
+        return direction === "publishes"
+            ? living.sent.includes(message) || (feat?.sent.includes(message) ?? false)
+            : living.received.includes(message) || (feat?.received.includes(message) ?? false);
+    };
+    const action = (direction) => (direction === "publishes" ? "send" : "receive");
+    // The declared→enumerated bridge coherence.ts uses for op edges, for the
+    // same reason: every lookup below joins into services/<id>/ or the
+    // feature's own specs/. A bound element NEITHER knows is skipped rather
+    // than graded — an #external producer is the documented shape for a
+    // message produced outside the fleet (spine.message-external), so grading
+    // its edge against an absent service directory would turn the worked
+    // example red.
+    const enumeratedTarget = enumeratedServiceIndex(scope.docsDir, svcNames, context);
+    // Tagged edges: `publishes` binds the edge's SOURCE, `consumes` its
+    // TARGET — the same reading validate's event spine takes of the living
+    // landscape, applied to the delta, from the one statement of the rule
+    // (core/c4/direction/direction.ts).
+    // Every consumption this merge would add, collected as the two loops below
+    // walk the edges and the lines, and asked for a producer at the end
+    // (./produced.ts) — `spine.message-unproduced` at feature scope.
+    const claims = [];
+    for (const r of taggedRels) {
+        const edge = `${svcOf(r.source)} → ${svcOf(r.target)}`;
+        for (const key of eventKeys(r)) {
+            const b = { direction: key.direction, message: key.message, name: svcOf(key.bound), edge };
+            const pathable = await enumeratedTarget(b.name);
+            if (pathable === undefined) {
+                // The skip above, unless the key is bound to infrastructure and a
+                // service sits at the OTHER end: then it is on the wrong end of its
+                // edge and binds nothing, which the living spine reports under the
+                // same code once this delta merges. An `#external` system at the bound
+                // end is an outside producer or consumer, and stays skipped.
+                const kind = request.infraKindOf(key.bound);
+                const drawer = kind === undefined ? undefined : await enumeratedTarget(svcOf(key.other));
+                if (kind !== undefined && drawer !== undefined) {
+                    issues.push({ severity: "warn", code: "spine.message-unbound", subject: drawer, message: `delta ${unboundSentence(r, key, kind)}` });
+                }
+                continue;
+            }
+            // asyncapi.invalid already gates; one breach, one finding.
+            if (declared.unreadable.has(pathable))
+                continue;
+            if (b.direction === "consumes")
+                claims.push({ service: pathable, message: b.message, source: "edge", via: `edge ${b.edge}` });
+            const ok = await declares(pathable, b.direction, b.message);
+            if (ok !== false)
+                continue;
+            const other = await lookups.messageDefinedElsewhere(pathable, b.message);
+            if (other !== undefined) {
+                issues.push({
+                    severity: "warn",
+                    code: "c4-event.message-pending",
+                    message: `edge ${b.edge} ${b.direction} '${b.message}', defined by in-flight ${other} — archive it first`,
+                });
+            }
+            else {
+                issues.push({
+                    severity: "error",
+                    code: "c4-event.message-undefined",
+                    message: `edge ${b.edge} ${b.direction} '${b.message}', but ${b.name}'s asyncapi contract (feature and living alike) declares no operation with action: ${action(b.direction)} for it`,
+                });
+            }
+        }
+    }
+    // The requirement deltas' own lines, graded the same way — the same
+    // sentence validate gives the living-side breach, under the same code, so
+    // one breach keeps one name across scopes. The lines were read once by
+    // ./declared.ts's walk (declared.links); re-reading them here per service
+    // was a second parse of both spec files on the context-less archive path.
+    for (const svc of svcNames) {
+        if (declared.unreadable.has(svc))
+            continue;
+        for (const link of declared.links.get(svc) ?? []) {
+            if (link.direction === "consumes") {
+                claims.push({ service: svc, message: link.message, source: "requirement", via: `requirement '${link.requirement}'` });
+            }
+            const ok = await declares(svc, link.direction, link.message);
+            if (ok !== false)
+                continue;
+            const other = await lookups.messageDefinedElsewhere(svc, link.message);
+            if (other !== undefined) {
+                issues.push({
+                    severity: "warn",
+                    code: "spec-event.message-pending",
+                    subject: svc,
+                    message: `${svc}: requirement '${link.requirement}' ${link.direction} '${link.message}', defined by in-flight ${other} — archive it first`,
+                });
+            }
+            else {
+                issues.push({
+                    severity: "error",
+                    code: "spec-event.message-undefined",
+                    subject: svc,
+                    message: `${svc}: requirement '${link.requirement}' ${link.direction} '${link.message}', but ${svc}'s asyncapi.yaml declares no operation with action: ${action(link.direction)} for it`,
+                });
+            }
+        }
+    }
+    issues.push(...(await unproducedIssues({ scope, declared, consumers, lookups, claims, known: request.known, ...(context === undefined ? {} : { context }) })));
+    return issues;
+}
+//# sourceMappingURL=events.js.map