@neat.is/core 0.7.8 → 0.7.10

package/dist/index.d.cts

@@ -1,5 +1,5 @@
 import { MultiDirectedGraph } from 'graphology';
-import { GraphNode, GraphEdge, EdgeTypeValue, StaleEvent, ErrorEvent, BlastRadiusResult, RootCauseResult, RegistryEntry, RegistryStatus, RegistryFile } from '@neat.is/types';
+import { GraphNode, GraphEdge, SpanAttributes, EdgeTypeValue, StaleEvent, ErrorEvent, BlastRadiusResult, RootCauseResult, RegistryEntry, RegistryStatus, RegistryFile } from '@neat.is/types';
 export { StaleEvent } from '@neat.is/types';
 import { FastifyInstance } from 'fastify';
 
@@ -134,6 +134,7 @@ interface ConnectorContext {
     projectDir: string;
     credentials: Record<string, unknown>;
     since?: string;
+    errorsPath?: string;
 }
 /**
  * `file:line` the provider's own signal carries, when it does (rare — see
@@ -146,6 +147,27 @@ interface ConnectorCallSite {
     file: string;
     line: number;
 }
+/**
+ * A failure the provider already recorded, carried on a signal so the shared
+ * pipeline can mint it as an OBSERVED incident on the repo node the failure
+ * implicates — the incident-emitting connector shape (connectors.md §10,
+ * ADR-185). EAS is the first user: an `ERRORED` build becomes one of these.
+ *
+ * It is a *pre-built* incident minus its `affectedNode`: the connector's
+ * mapping layer fills every field here, and the shared pipeline sets the
+ * `affectedNode` from `resolveTarget` and derives the `traceId`/`spanId` the
+ * `ErrorEvent` shape requires from the stable `id`. So the terminal write is
+ * an `ErrorEvent` on the incident ledger (the same store OTLP-derived
+ * incidents use), not an `upsertObservedEdge`.
+ */
+interface ConnectorIncident {
+    id: string;
+    timestamp: string;
+    service: string;
+    errorType: string;
+    errorMessage: string;
+    attributes?: SpanAttributes;
+}
 /**
  * One provider-agnostic observation. `targetKind`/`targetName` are the
  * provider's own vocabulary (`'supabase-table'`/`'orders'`,
@@ -163,6 +185,7 @@ interface ObservedSignal {
     lastObservedIso: string;
     callSite?: ConnectorCallSite;
     columns?: string[];
+    incident?: ConnectorIncident;
 }
 
 /**
@@ -302,6 +325,10 @@ interface BuildOtelReceiverOptions {
     onProjectSpan?: ProjectSpanHandler;
     onProjectErrorSpanSync?: (project: string, span: ParsedSpan) => Promise<void>;
     isProjectRegistered?: (project: string) => boolean;
+    classifyBareRoutability?: (spans: ParsedSpan[]) => {
+        rejected: number;
+        message?: string;
+    };
     bodyLimit?: number;
     authToken?: string;
     trustProxy?: boolean;

package/dist/index.d.ts

@@ -1,5 +1,5 @@
 import { MultiDirectedGraph } from 'graphology';
-import { GraphNode, GraphEdge, EdgeTypeValue, StaleEvent, ErrorEvent, BlastRadiusResult, RootCauseResult, RegistryEntry, RegistryStatus, RegistryFile } from '@neat.is/types';
+import { GraphNode, GraphEdge, SpanAttributes, EdgeTypeValue, StaleEvent, ErrorEvent, BlastRadiusResult, RootCauseResult, RegistryEntry, RegistryStatus, RegistryFile } from '@neat.is/types';
 export { StaleEvent } from '@neat.is/types';
 import { FastifyInstance } from 'fastify';
 
@@ -134,6 +134,7 @@ interface ConnectorContext {
     projectDir: string;
     credentials: Record<string, unknown>;
     since?: string;
+    errorsPath?: string;
 }
 /**
  * `file:line` the provider's own signal carries, when it does (rare — see
@@ -146,6 +147,27 @@ interface ConnectorCallSite {
     file: string;
     line: number;
 }
+/**
+ * A failure the provider already recorded, carried on a signal so the shared
+ * pipeline can mint it as an OBSERVED incident on the repo node the failure
+ * implicates — the incident-emitting connector shape (connectors.md §10,
+ * ADR-185). EAS is the first user: an `ERRORED` build becomes one of these.
+ *
+ * It is a *pre-built* incident minus its `affectedNode`: the connector's
+ * mapping layer fills every field here, and the shared pipeline sets the
+ * `affectedNode` from `resolveTarget` and derives the `traceId`/`spanId` the
+ * `ErrorEvent` shape requires from the stable `id`. So the terminal write is
+ * an `ErrorEvent` on the incident ledger (the same store OTLP-derived
+ * incidents use), not an `upsertObservedEdge`.
+ */
+interface ConnectorIncident {
+    id: string;
+    timestamp: string;
+    service: string;
+    errorType: string;
+    errorMessage: string;
+    attributes?: SpanAttributes;
+}
 /**
  * One provider-agnostic observation. `targetKind`/`targetName` are the
  * provider's own vocabulary (`'supabase-table'`/`'orders'`,
@@ -163,6 +185,7 @@ interface ObservedSignal {
     lastObservedIso: string;
     callSite?: ConnectorCallSite;
     columns?: string[];
+    incident?: ConnectorIncident;
 }
 
 /**
@@ -302,6 +325,10 @@ interface BuildOtelReceiverOptions {
     onProjectSpan?: ProjectSpanHandler;
     onProjectErrorSpanSync?: (project: string, span: ParsedSpan) => Promise<void>;
     isProjectRegistered?: (project: string) => boolean;
+    classifyBareRoutability?: (spans: ParsedSpan[]) => {
+        rejected: number;
+        message?: string;
+    };
     bodyLimit?: number;
     authToken?: string;
     trustProxy?: boolean;

package/dist/index.js

@@ -1,7 +1,7 @@
 import {
   routeSpanToProject,
   startDaemon
-} from "./chunk-OVRVDSUO.js";
+} from "./chunk-D4OX6MUX.js";
 import {
   ProjectNameCollisionError,
   addProject,
@@ -37,15 +37,15 @@ import {
   thresholdForEdgeType,
   touchLastSeen,
   writeAtomically
-} from "./chunk-LN75Z624.js";
+} from "./chunk-6T7ZHODF.js";
 import {
   startOtelGrpcReceiver
-} from "./chunk-4GCV46AP.js";
+} from "./chunk-FCO5Z3RW.js";
 import {
   buildOtelReceiver,
   logSpanHandler,
   parseOtlpRequest
-} from "./chunk-Y43UCVZS.js";
+} from "./chunk-UUYCTH2E.js";
 export {
   ProjectNameCollisionError,
   addProject,