@neat.is/core 0.4.16 → 0.4.18

package/dist/index.d.cts

@@ -238,8 +238,16 @@ interface IngestContext {
     now?: () => number;
     writeErrorEventInline?: boolean;
     onPolicyTrigger?: (graph: NeatGraph) => Promise<void> | void;
+    burstState?: Map<string, BurstState>;
 }
 declare function thresholdForEdgeType(edgeType: string, overrides?: Record<string, number>): number;
+interface BurstState {
+    count: number;
+    firstTs: string;
+    lastTs: string;
+    lastMs: number;
+    codes: Map<number, number>;
+}
 declare function stitchTrace(graph: NeatGraph, sourceServiceId: string, ts: string): void;
 declare function handleSpan(ctx: IngestContext, span: ParsedSpan): Promise<void>;
 
@@ -347,8 +355,25 @@ declare function computeGraphDiff(liveGraph: NeatGraph, baseSnapshot: PersistedS
  *  - Auto-restart on crash. PID file is the supervisor handoff.
  */
 
+interface DaemonPorts {
+    rest: number;
+    otlp: number;
+    web: number;
+}
+interface DaemonRecord {
+    project: string;
+    projectPath: string;
+    pid: number;
+    status: 'running' | 'stopped';
+    ports: DaemonPorts;
+    startedAt: string;
+    neatVersion: string;
+}
 interface DaemonOptions {
     neatHome?: string;
+    project?: string;
+    projectPath?: string;
+    webPort?: number;
     restPort?: number;
     otlpPort?: number;
     host?: string;
@@ -382,6 +407,7 @@ interface DaemonHandle {
     otlpAddress: string;
     bootstrap: BootstrapTracker;
     initialBootstrap: Promise<void>;
+    daemonRecord: DaemonRecord | null;
 }
 /**
  * Resolve which project's graph an OTel span belongs to. Looks up the
@@ -419,22 +445,34 @@ declare function routeSpanToProject(serviceName: string | undefined, projects: R
 declare function startDaemon(opts?: DaemonOptions): Promise<DaemonHandle>;
 
 /**
- * Machine-level project registry (ADR-048).
+ * Machine-level project registry + machine-wide daemon discovery.
+ *
+ * This module owns two surfaces under `~/.neat/`:
+ *
+ *  1. The legacy project registry at `~/.neat/projects.json` (ADR-048). One
+ *     file, per-user, machine-local, not synced. Under the project-daemon
+ *     contract (ADR-096) it is no longer the coordination point — it is read
+ *     once for migration and otherwise left to the additive writes the daemon
+ *     and orchestrator still perform. The read-modify-write helpers below keep
+ *     their atomic-write + exclusive-lock machinery for that legacy surface.
  *
- * One file: `~/.neat/projects.json`. Per-user, machine-local. Not synced.
- * `registry.ts` is the only module that opens it. Everything else — `init`,
- * `daemon`, `cli` — calls into the helpers below.
+ *  2. The machine-wide daemon discovery directory at `~/.neat/daemons/`
+ *     (ADR-096 §6). One file per running daemon — `<project>.json` — each owned
+ *     solely by the daemon that wrote it (on start) and removes it (on graceful
+ *     stop). Discovery is **append-only and lock-free**: a reader scans the
+ *     directory and reconciles liveness; it never acquires a shared lock, so it
+ *     can never deadlock against a daemon (#506). Losing or rebuilding the
+ *     directory costs discovery convenience, not correctness — each project's
+ *     own `neat-out/daemon.json` stays authoritative.
  *
- * Two safety properties matter:
- *  1. Atomic writes. We tmp + fsync + rename so the daemon never sees a torn
- *     file when init races against it.
- *  2. Cross-process exclusion. We hold an exclusive lock on
- *     `~/.neat/projects.json.lock` for the read-modify-write window. Two
- *     concurrent `neat init` runs cannot both win and overwrite each other.
+ * `neat ps` / `neat list` and the per-daemon `pause` / `resume` / `uninstall`
+ * verbs read discovery, falling back to the legacy registry where no daemon
+ * file is present yet (the migration window before every daemon self-describes).
  *
- * The lock is a file we exclusively-create (`O_EXCL`), hold while we mutate,
- * and unlink on the way out. Crude but cross-platform; matches what
- * `proper-lockfile` does internally without pulling the dep in.
+ * The legacy lock is a file we exclusively-create (`O_EXCL`), hold while we
+ * mutate, and unlink on the way out. Crude but cross-platform; matches what
+ * `proper-lockfile` does internally without pulling the dep in. It never sits
+ * on the discovery path.
  */
 
 declare function registryPath(): string;

package/dist/index.d.ts

@@ -238,8 +238,16 @@ interface IngestContext {
     now?: () => number;
     writeErrorEventInline?: boolean;
     onPolicyTrigger?: (graph: NeatGraph) => Promise<void> | void;
+    burstState?: Map<string, BurstState>;
 }
 declare function thresholdForEdgeType(edgeType: string, overrides?: Record<string, number>): number;
+interface BurstState {
+    count: number;
+    firstTs: string;
+    lastTs: string;
+    lastMs: number;
+    codes: Map<number, number>;
+}
 declare function stitchTrace(graph: NeatGraph, sourceServiceId: string, ts: string): void;
 declare function handleSpan(ctx: IngestContext, span: ParsedSpan): Promise<void>;
 
@@ -347,8 +355,25 @@ declare function computeGraphDiff(liveGraph: NeatGraph, baseSnapshot: PersistedS
  *  - Auto-restart on crash. PID file is the supervisor handoff.
  */
 
+interface DaemonPorts {
+    rest: number;
+    otlp: number;
+    web: number;
+}
+interface DaemonRecord {
+    project: string;
+    projectPath: string;
+    pid: number;
+    status: 'running' | 'stopped';
+    ports: DaemonPorts;
+    startedAt: string;
+    neatVersion: string;
+}
 interface DaemonOptions {
     neatHome?: string;
+    project?: string;
+    projectPath?: string;
+    webPort?: number;
     restPort?: number;
     otlpPort?: number;
     host?: string;
@@ -382,6 +407,7 @@ interface DaemonHandle {
     otlpAddress: string;
     bootstrap: BootstrapTracker;
     initialBootstrap: Promise<void>;
+    daemonRecord: DaemonRecord | null;
 }
 /**
  * Resolve which project's graph an OTel span belongs to. Looks up the
@@ -419,22 +445,34 @@ declare function routeSpanToProject(serviceName: string | undefined, projects: R
 declare function startDaemon(opts?: DaemonOptions): Promise<DaemonHandle>;
 
 /**
- * Machine-level project registry (ADR-048).
+ * Machine-level project registry + machine-wide daemon discovery.
+ *
+ * This module owns two surfaces under `~/.neat/`:
+ *
+ *  1. The legacy project registry at `~/.neat/projects.json` (ADR-048). One
+ *     file, per-user, machine-local, not synced. Under the project-daemon
+ *     contract (ADR-096) it is no longer the coordination point — it is read
+ *     once for migration and otherwise left to the additive writes the daemon
+ *     and orchestrator still perform. The read-modify-write helpers below keep
+ *     their atomic-write + exclusive-lock machinery for that legacy surface.
  *
- * One file: `~/.neat/projects.json`. Per-user, machine-local. Not synced.
- * `registry.ts` is the only module that opens it. Everything else — `init`,
- * `daemon`, `cli` — calls into the helpers below.
+ *  2. The machine-wide daemon discovery directory at `~/.neat/daemons/`
+ *     (ADR-096 §6). One file per running daemon — `<project>.json` — each owned
+ *     solely by the daemon that wrote it (on start) and removes it (on graceful
+ *     stop). Discovery is **append-only and lock-free**: a reader scans the
+ *     directory and reconciles liveness; it never acquires a shared lock, so it
+ *     can never deadlock against a daemon (#506). Losing or rebuilding the
+ *     directory costs discovery convenience, not correctness — each project's
+ *     own `neat-out/daemon.json` stays authoritative.
  *
- * Two safety properties matter:
- *  1. Atomic writes. We tmp + fsync + rename so the daemon never sees a torn
- *     file when init races against it.
- *  2. Cross-process exclusion. We hold an exclusive lock on
- *     `~/.neat/projects.json.lock` for the read-modify-write window. Two
- *     concurrent `neat init` runs cannot both win and overwrite each other.
+ * `neat ps` / `neat list` and the per-daemon `pause` / `resume` / `uninstall`
+ * verbs read discovery, falling back to the legacy registry where no daemon
+ * file is present yet (the migration window before every daemon self-describes).
  *
- * The lock is a file we exclusively-create (`O_EXCL`), hold while we mutate,
- * and unlink on the way out. Crude but cross-platform; matches what
- * `proper-lockfile` does internally without pulling the dep in.
+ * The legacy lock is a file we exclusively-create (`O_EXCL`), hold while we
+ * mutate, and unlink on the way out. Crude but cross-platform; matches what
+ * `proper-lockfile` does internally without pulling the dep in. It never sits
+ * on the discovery path.
  */
 
 declare function registryPath(): string;

package/dist/index.js

@@ -1,7 +1,7 @@
 import {
   routeSpanToProject,
   startDaemon
-} from "./chunk-VMLWUK7W.js";
+} from "./chunk-GXWBMJDJ.js";
 import {
   ProjectNameCollisionError,
   addProject,
@@ -37,15 +37,15 @@ import {
   thresholdForEdgeType,
   touchLastSeen,
   writeAtomically
-} from "./chunk-XS4CGNRO.js";
+} from "./chunk-T3X6XJPU.js";
 import {
   startOtelGrpcReceiver
-} from "./chunk-GHPHVXYM.js";
+} from "./chunk-MTXF77TN.js";
 import {
   buildOtelReceiver,
   logSpanHandler,
   parseOtlpRequest
-} from "./chunk-6CO7C4IU.js";
+} from "./chunk-BGPWBRLU.js";
 export {
   ProjectNameCollisionError,
   addProject,