@wrongstack/core 0.301.0 → 0.302.2

package/dist/chronicle/metrics-store.d.ts

@@ -139,6 +139,20 @@ export declare class ChronicleMetricsStore {
     private ensureSchema;
     private loadOffsets;
     private pruneOffsets;
+    /**
+     * Fold everything the SQLite journal holds past this store's per-day cursor.
+     *
+     * Opened read-only on its own connection: the journal runs in WAL, so this
+     * never blocks the daemon writing to it, and metrics are best-effort — a
+     * journal that cannot be opened (mid-migration, absent, locked) leaves the
+     * cursors untouched and the next refresh retries.
+     *
+     * Rows the journal has already evicted are simply not seen. That is the
+     * intended split of responsibilities: the journal is a bounded ring, and this
+     * store is where an aggregate outlives the raw event it came from — which
+     * only holds if refresh runs more often than the ring turns over.
+     */
+    private ingestSqliteJournal;
     /** Read complete lines appended after `consumed` bytes. The trailing
      *  partial line of an actively-written partition is left for the next
      *  refresh — `ingest_state.bytes` only ever advances past full lines. */

package/dist/chronicle/project-server-protocol.d.ts

@@ -4,6 +4,19 @@ import type { ChronicleFacet, ChronicleFacetResults, ChronicleFacetValue, Chroni
 import type { ChronicleEvent, ChronicleEventInput } from './types.js';
 export declare const CHRONICLE_PROJECT_SERVER_PROTOCOL_VERSION = 2;
 export declare const CHRONICLE_PROJECT_SERVER_MAX_FRAME_CHARS: number;
+/**
+ * Most events one `append` call may carry.
+ *
+ * This lives in the protocol module because both ends must agree on it, and
+ * they did not: the server rejected anything above this bound while the client
+ * drained its entire backlog into a single call, with a backpressure ceiling ten
+ * times higher. A client that ever accumulated more than this — which only
+ * happens when the daemon is slow or restarting, exactly when the telemetry
+ * matters — had its whole batch rejected as malformed and lost every event in
+ * it, rather than persisting what it could. A shared constant is what keeps the
+ * producer's chunking and the consumer's validation from drifting apart again.
+ */
+export declare const CHRONICLE_MAX_APPEND_BATCH = 10000;
 /**
  * What the daemon tells a connecting client about itself. Carries NO secret —
  * see {@link ChronicleProjectServerMetadata}.