@noy-db/hub 0.3.0-pre.10 → 0.3.0-pre.12

package/dist/kernel/events.d.ts

@@ -0,0 +1,11 @@
+import type { NoydbEventMap } from './types.js';
+type EventHandler<T> = (data: T) => void;
+/** Typed event emitter for NOYDB events. */
+export declare class NoydbEventEmitter {
+    private readonly listeners;
+    on<K extends keyof NoydbEventMap>(event: K, handler: EventHandler<NoydbEventMap[K]>): void;
+    off<K extends keyof NoydbEventMap>(event: K, handler: EventHandler<NoydbEventMap[K]>): void;
+    emit<K extends keyof NoydbEventMap>(event: K, data: NoydbEventMap[K]): void;
+    removeAllListeners(): void;
+}
+export {};

package/dist/kernel/memory-store.d.ts

@@ -0,0 +1,17 @@
+import type { NoydbStore } from './types.js';
+/**
+ * Built-in in-memory store — the kernel's zero-config default.
+ *
+ * Nested `Map`s: `vault → collection → id → envelope`. Non-persistent
+ * (data is lost on process exit). A conformant 6-method {@link NoydbStore}
+ * with CAS atomicity and a monotonic store clock — the kernel version of
+ * `@noy-db/to-memory`'s core, so `createNoydb()` works with no store package.
+ *
+ * Portable: imports only `types` + `errors` (no crypto primitive) — passes
+ * the `stores-ciphertext-only` architecture guard.
+ *
+ * Implements the 6-method core only (no optional `listVaults`/`ping`/`tx`),
+ * so `Noydb.listAccessibleVaults()` throws its documented capability error
+ * rather than enumerating vaults under the default store.
+ */
+export declare function memoryStore(): NoydbStore;

package/dist/kernel/mutation.d.ts

@@ -0,0 +1,14 @@
+/**
+ * Where a record mutation originated. Determines which side-effects
+ * {@link Collection._onRecordMutated} performs for a given `put`/`delete`.
+ *
+ * - `local-write` — `Collection.put` (user write; includes the CRDT branch).
+ * - `local-delete` — `Collection.delete` / `_internalDelete` (`_doDelete`).
+ * - `tab-mirror` — cross-tab BroadcastChannel relay (`_applyRemoteChange`).
+ * - `sync-apply` — `SyncEngine#applyRemote` (pull/push conflict winners,
+ *   CRDT merges, tombstone reasserts), routed via `Vault#_invalidateSyncApplied`.
+ * - `cutover` — `Collection._applyCutoverTransform` (coordinated schema migration).
+ * - `restore` — `Vault.load` / `backup.ts#loadVault`. Reserved: restore drops
+ *   the whole `collectionCache` and never reaches per-record dispatch today.
+ */
+export type MutationOrigin = 'local-write' | 'local-delete' | 'tab-mirror' | 'sync-apply' | 'cutover' | 'restore';