@lunora/platform-node 1.0.0-alpha.9 → 1.0.0-alpha.91

package/dist/conformance/index.mjs

@@ -1 +1 @@
-import{createNodeShardKvStore as f}from"../packem_shared/createNodeShardKvStore-BfKCQTjE.mjs";import{createNodeSchedulerHost as y}from"../packem_shared/createNodeSchedulerHost-DRjZhuxe.mjs";import{createNodeShardHost as k}from"../packem_shared/createNodeShardHost-DEHe5Vcm.mjs";import{createNodeShardRegistry as D}from"../packem_shared/createNodeShardRegistry-0iSMdi9-.mjs";import{createNodeSocketHost as N}from"../packem_shared/createNodeSocketHost-CytowrYN.mjs";const b=()=>{const{database:r,dispose:c,host:i}=k(),m=f(r),a=D(),{directory:n}=a,{readFrames:h,restoreSocket:l,simulateRecycle:u,socket:p}=N(r),s=new Set,{dispose:w,scheduler:d,simulateDeadLetter:S}=y(r,{onDispatch:(e,t,o)=>{s.add(o.id)}});return{awaitAlarmFired:async e=>{await new Promise(t=>{setTimeout(t,Math.max(0,e-Date.now())+30)})},awaitJobDispatched:async e=>{const t=(await d.list?.())?.find(o=>o.id===e);return t!==void 0&&await new Promise(o=>{setTimeout(o,Math.max(0,t.scheduledFor-Date.now())+30)}),s.has(e)},cleanup:()=>{w(),c(),a.close()},directory:n,kv:m,readFrames:h,restoreSocket:l,scheduler:d,shard:i,simulateDeadLetter:S,simulateRecycle:u,socket:p}};export{b as createNodeConformanceHost};
+import{createNodeShardKvStore as N}from"../packem_shared/createNodeShardKvStore-DVi1OsvH.mjs";import{createNodeSchedulerHost as k}from"../packem_shared/createNodeSchedulerHost-BEAX6I4m.mjs";import{createNodeShardHost as D}from"../packem_shared/createNodeShardHost-Da19DFX0.mjs";import{createNodeShardRegistry as H}from"../packem_shared/createNodeShardRegistry-D-KxwdUc.mjs";import{createNodeSocketHost as T}from"../packem_shared/createNodeSocketHost-DQs85G7W.mjs";const P=()=>{const{database:o,dispose:m,host:p}=D(),h=N(o),c=H(),{directory:l}=c,{readFrames:w,restoreSocket:u,simulateRecycle:S,socket:y}=T(o),d=new Set,s=new Map,{dispose:f,scheduler:i,simulateDeadLetter:g}=k(o,{onDispatch:(e,a,t)=>{d.add(t.id),s.set(e,(s.get(e)??0)+1)}}),n=()=>{f(),m(),c.close()};return{awaitAlarmFired:async e=>{await new Promise(a=>{setTimeout(a,Math.max(0,e-Date.now())+30)})},awaitJobDispatched:async e=>{const t=(await i.list?.())?.find(r=>r.id===e);return t!==void 0&&await new Promise(r=>{setTimeout(r,Math.max(0,t.scheduledFor-Date.now())+30)}),d.has(e)},cleanup:n,cronTicks:e=>s.get(e)??0,directory:l,disposeTerminally:n,kv:h,readFrames:w,restoreSocket:u,scheduler:i,shard:p,simulateDeadLetter:g,simulateRecycle:S,socket:y}};export{P as createNodeConformanceHost};

package/dist/index.d.mts

@@ -14,13 +14,14 @@ type NodeGlobalContextDatabaseOptions = Omit<SqlCtxDbOptions, "dialect" | "exec"
 /**
  * Wrap a `better-sqlite3` connection as the async exec the store core consumes.
  *
- * `batch` is deliberately **not** implemented. The contract lets an exec that
- * omits it fall back to a sequential `run()` loop, and that fallback is already
- * optimal here: `batch` exists to collapse network round trips (D1 does it
- * atomically in one request; the Hyperdrive adapters dispatch concurrently over
- * a pool), and an embedded database has no round trip to collapse. Declaring it
- * would buy nothing and would opt this exec into the "MAY reorder or
- * parallelize" licence for no reason.
+ * `batch` runs the statements in order inside one `better-sqlite3`
+ * transaction, which is synchronous, so nothing else runs between them. There is
+ * no round trip to save; atomicity is the point. The store core's FTS5 search
+ * companion writes each document as an ordered list of statements, and without
+ * this two async writers interleaved at every `await` between them: one could
+ * move a document's mapping while the other's entry was mid-write, leaving an
+ * entry no later write or purge could reach. The `sqlite` dialect's contract
+ * requires an ordered, atomic `batch` for exactly that reason.
  */
 declare const createNodeSqlExec: (database: Database.Database) => SqlCtxExec;
 /** Options for {@link createNodeGlobalStore}. */
@@ -197,9 +198,12 @@ interface NodeShardHostOptions {
    * `_lunora_alarm` when the host is constructed over an existing database,
    * including an alarm whose time elapsed while nothing was running.
    *
-   * A handler that throws is isolated to its own delivery; it never reaches
+   * A handler that throws is isolated to its own delivery — it never reaches
    * the caller that set the alarm, because by then that call has long
-   * returned.
+   * returned — and the wakeup is then re-delivered with backoff up to
+   * {@link ALARM_RETRY_LIMIT} times, the way workerd retries a throwing
+   * `alarm()`. Delivery is at-least-once, so the handler must tolerate
+   * running twice for one scheduled timestamp.
    */
   onAlarm?: () => Promise<void> | void;
   /**
@@ -218,25 +222,59 @@ interface NodeShardHostOptions {
 /**
  * Build a `ShardHost` over a real `better-sqlite3` database.
  *
- * `runSerialized` chains onto a single `tail` promise rather than the
- * reference host's explicit job-array-plus-drain-loop: every queued closure
- * runs once `tail` settles, and `tail` is reset to a version that always
- * resolves (never rejects) so one job's failure cannot wedge the queue for
- * every job after it — the same "no two closures interleave" guarantee,
- * fewer moving parts to get wrong.
+ * `runSerialized` and `transaction` share **one** boundary lock, because they
+ * write **one** `better-sqlite3` connection. `transaction` issues raw
+ * `BEGIN`/`COMMIT`/`ROLLBACK` — legal here (unlike inside a Cloudflare Durable
+ * Object, where the runtime forbids it and callers must use
+ * `storage.transaction`) because better-sqlite3 is a plain embedded database
+ * with no platform-level transaction primitive layered over it.
  *
- * `transaction` issues raw `BEGIN`/`COMMIT`/`ROLLBACK` — legal here (unlike
- * inside a Cloudflare Durable Object, where the runtime forbids it and
- * callers must use `storage.transaction`) because better-sqlite3 is a plain
- * embedded database with no platform-level transaction primitive layered over
- * it. It runs on its own private `transactionTail` chain, the same shape as
- * `runSerialized`'s but never shared with it: two bare, overlapping
- * `transaction()` calls on this host serialize against each other rather than
- * corrupting each other's commits (raw `BEGIN` on a connection already inside
- * a transaction throws, or worse, interleaves). Routing `transaction` through
- * `runSerialized` itself would deadlock, since the engine already composes
- * `runSerialized(() => transaction(work))` — the inner enqueue would then wait
- * on the outer closure awaiting it.
+ * ## Why one lane and not two
+ *
+ * This host shipped with two private tail chains, one per entry point, so each
+ * serialized against itself and neither against the other. `runSerialized`
+ * issues no `BEGIN` of its own, so one of its closures overlapping a bare
+ * `transaction()` wrote straight into that transaction's span. `assertOwnTurn`
+ * below catches the write — it is the only reason this host never silently lost
+ * one the way an unguarded connection would — but catching it is not the same
+ * as preventing it, and the refusal lands in the wrong place:
+ *
+ * 1. A `runSerialized` closure writes a row. Nothing is open, so it commits.
+ * 2. It awaits (a scheduler hop, an `onShardInit` read, any real I/O).
+ * 3. A bare `transaction()` runs `BEGIN` while it is parked. `transaction` is
+ * a public contract surface, and `./node-shard-state` re-exports it as the
+ * `storage.transaction` member `ShardDO` documents as "the platform
+ * primitive", so a subclass reaches one without going through the engine.
+ * 4. The closure resumes and its next write is refused with
+ * `SHARD_UNAVAILABLE`, so `runSerialized` **rejects** — with step 1 already
+ * durable.
+ *
+ * The boundary the contract promises is atomic-or-nothing to its caller tore in
+ * half: a rejection the caller will retry, on top of a write the retry now
+ * re-applies. That is `runSerialized`'s "no two closures interleave" guarantee
+ * broken by a `transaction` it was never serialized against.
+ *
+ * ## Why the lock is re-entrant, and why `AsyncLocalStorage` is what makes it so
+ *
+ * The engine composes the two, and stacks them: `ShardRunner.runInTransaction`
+ * is `runSerialized(() => transaction(work))` (`@lunora/shard-engine`), and
+ * `ShardDO.fetch` widens a mutation dispatch carrying `x-lunora-mutation-id`
+ * into a *further* `runSerialized` span around it (`@lunora/do`). Under two
+ * plain FIFO chains that outer span is already fatal on this host — the inner
+ * `runSerialized` waits on a `tail` that only settles when the outer closure it
+ * is running inside resolves, and because nothing ever resets that `tail`, the
+ * shard's write lane is wedged for the life of the process rather than for the
+ * life of the request.
+ *
+ * So the lock is skipped for a boundary opened from inside a boundary, and
+ * `AsyncLocalStorage` is the only thing that can tell that case from the one
+ * that must queue: its store follows a single call's own await chain without
+ * leaking into a sibling chain. A held boolean cannot — it reads `true` for an
+ * unrelated *second top-level* `transaction()` too, which would then nest a raw
+ * `BEGIN` on a connection already inside one. This is the same distinction
+ * workerd's `blockConcurrencyWhile` draws natively with "does not queue events
+ * initiated as part of the callback itself", which is what
+ * `@lunora/platform-cloudflare` leans on for the identical composition.
  *
  * The returned `dispose()` is this host's lifecycle owner: it clears the
  * pending alarm `setTimeout` (so it can never fire against a connection this
@@ -310,22 +348,64 @@ interface NodeShardRegistry {
 }
 /** Build the in-process shard registry. */
 declare const createNodeShardRegistry: (options?: NodeShardRegistryOptions) => NodeShardRegistry;
+/** Options for {@link createNodeWorkflowHost}. */
+interface NodeWorkflowHostOptions<Workflows extends Record<string, {
+  isLunoraWorkflow: true;
+}>> {
+  /** Base env merged under the derived `WORKFLOW_*` bindings — surfaced to workflow bodies as `ctx.env` and used to resolve spawned children. */
+  env?: Record<string, unknown>;
+  /** How long (ms) the engine holds a cross-process lease while an activation runs, for stores that implement `acquire`. Defaults to 30000. */
+  leaseTtlMs?: number;
+  /** Where runs are persisted. Required — see the header for why there is no default. `createNodeWorkflowStore(database)` is the durable one. */
+  store: WorkflowStore;
+  /** The declared workflows keyed by their `lunora/workflows.ts` export name (e.g. `{ orderPipeline: orderPipeline }`). Values must be `defineWorkflow` results. */
+  workflows: Workflows;
+}
+/** A fully-wired Node workflow host. */
+interface NodeWorkflowHost<Workflows extends Record<string, {
+  isLunoraWorkflow: true;
+}>> {
+  /** Per-export-name `WorkflowBindingLike` — the map `ctx.workflows` consumes. */
+  readonly bindings: { [K in keyof Workflows]: WorkflowBindingLike; };
+  /**
+   * The caller's `env` plus one `WORKFLOW_&lt;EXPORT>` binding per workflow —
+   * merge this into a worker env so `ctx.spawn`/`ctx.parallel` resolve
+   * children through the same runtime.
+   */
+  readonly env: Record<string, unknown>;
+  /** The underlying visulima runtime — `sweep`/`signal` for a dev loop or tests. */
+  readonly runtime: WorkflowRuntime;
+}
+/**
+ * Create a Node workflow host: compile every declared Lunora workflow onto the
+ * visulima engine, derive the `WORKFLOW_*` env, and expose the per-workflow
+ * `WorkflowBindingLike` handles.
+ */
+declare const createNodeWorkflowHost: <Workflows extends Record<string, {
+  isLunoraWorkflow: true;
+}>>(options: NodeWorkflowHostOptions<Workflows>) => NodeWorkflowHost<Workflows>;
 /** Every contract this package provides, composed for one Node process. */
 interface NodePlatform<Queues extends Record<string, {
   isLunoraQueue: true;
+}> = Record<string, never>, Workflows extends Record<string, {
+  isLunoraWorkflow: true;
 }> = Record<string, never>> {
   /** `using platform = createNodePlatform(...)` support — delegates to `close()`. */
   [Symbol.dispose]: () => void;
   /** What this target supports — see `NODE_CAPABILITIES` in `@lunora/platform`. */
   capabilities: PlatformCapabilities;
   /**
-   * Tear this platform instance down: clears the shard host's pending alarm
-   * timer and closes its `better-sqlite3` database (and, with it, `kv`'s
-   * table — both live on the same connection), then clears every armed
-   * scheduler job timer. Nothing in this package closes these resources on
-   * its own — a `NodePlatform` a caller stops using without calling `close()`
-   * leaks the open file handle (plus its WAL/SHM sidecar files) and keeps
-   * the process alive on outstanding timers. Safe to call more than once.
+   * Tear this platform instance down: every resource this root built, in
+   * reverse construction order — the global store's own connection, every
+   * armed scheduler job timer, the registry's live shards, and last the shard
+   * host's pending alarm timer and its `better-sqlite3` database (and, with
+   * it, `kv`'s table — both live on the same connection). Nothing in this
+   * package closes these resources on its own — a `NodePlatform` a caller
+   * stops using without calling `close()` leaks the open file handles (plus
+   * their WAL/SHM sidecar files) and keeps the process alive on outstanding
+   * timers. Safe to call more than once. A `createNodePlatform` that throws
+   * unwinds the same list itself, so a failed construction leaks nothing and
+   * leaves nothing to call this on.
    *
    * **`close()` is a terminal state, not merely a cleanup step.** After it
    * runs: `scheduler.schedule()` throws instead of arming a fresh timer
@@ -335,8 +415,10 @@ interface NodePlatform<Queues extends Record<string, {
    * benign); `shard.alarms.set()`/`delete()` throw before mutating any
    * in-memory state (checked against the connection's own open/closed state,
    * the single source of truth); `shard.alarms.get()` keeps answering
-   * whatever it last held. A no-op instead of a throw would be
-   * indistinguishable from a working call — exactly the silent-vanishing
+   * whatever it last held; `sockets.accept()`/`setTag()`/`removeTag()` throw
+   * the same way, checked against the same connection state, before touching
+   * any runtime socket map or durable row. A no-op instead of a throw would
+   * be indistinguishable from a working call — exactly the silent-vanishing
    * this lifecycle exists to end.
    */
   close: () => void;
@@ -351,8 +433,28 @@ interface NodePlatform<Queues extends Record<string, {
    * shutdown is `await platform.drain()` then `platform.close()`.
    */
   drain: () => Promise<void>;
+  /**
+   * The `.global()` backend, or `undefined` when the caller named no database
+   * file for it. There is no default path, because a global store silently
+   * rooted at `:memory:` loses every row when the process exits.
+   *
+   * **A building block, not a wiring.** Unlike its three siblings, nothing
+   * downstream of this composition root reads it: a `.global()` read or write
+   * reaches its backend through exactly one seam, `createShardCtxDb({ globalDb
+   * })`, and the only thing that passes `globalDb` is the generated `shard.ts`,
+   * from its `d1` / `hyperdriveGlobal` config thunks. `createNodePlatform`
+   * constructs no shard DO, so it cannot make that hop itself. A caller that
+   * wants `.global()` on this host makes it: after `migrate(schema)` has
+   * provisioned the tables, give the generated `createShardDO` a `d1` thunk
+   * returning `platform.globalTables.writer({ schema, … })` — `writer` builds
+   * the `createSqlCtxDb` facade that seam expects, and `node-platform.test.ts`
+   * round-trips a row through exactly that object.
+   */
+  globalTables?: NodeGlobalStore;
   /** Durable key-value storage backed by the same `better-sqlite3` database as `shard`. */
   kv: ShardKvStore;
+  /** The local-filesystem bucket, or `undefined` when the caller named no bucket directory. */
+  objectStorage?: R2BucketLike;
   /**
    * The declared queues, or `undefined` when the caller declared none.
    *
@@ -367,6 +469,12 @@ interface NodePlatform<Queues extends Record<string, {
   shard: ShardHost;
   /** Socket registry with mutable tags and SQLite-persisted attachments. */
   sockets: SocketHost;
+  /**
+   * The declared workflows, or `undefined` when the caller declared none.
+   * Runs are persisted to the same `better-sqlite3` database as the shard, so
+   * they survive a restart without a second store to configure.
+   */
+  workflows?: NodeWorkflowHost<Workflows>;
 }
 /**
  * Options for {@link createNodePlatform} — the shard host's (`path`,
@@ -376,10 +484,29 @@ interface NodePlatform<Queues extends Record<string, {
  * or job with nowhere to land is bookkeeping. `directory` makes the shards the
  * directory resolves for fan-out file-backed too, and `onAlarm` gives their
  * durable alarms somewhere to land.
+ *
+ * `queues`, `workflows`, `objectStorageDirectory` and `globalTablesPath` are the
+ * four declarations — each is absent from the returned platform when omitted.
  */
 type NodePlatformOptions<Queues extends Record<string, {
   isLunoraQueue: true;
+}> = Record<string, never>, Workflows extends Record<string, {
+  isLunoraWorkflow: true;
 }> = Record<string, never>> = {
+  /**
+   * Database file the `.global()` tables live in — its own file, never a
+   * shard's, because a table every shard reads must not be inside any one of
+   * them. Omit when the app declares no `.global()` table; there is no
+   * default, for the same reason the bucket has none.
+   */
+  globalTablesPath?: string;
+  /**
+   * Directory the object-storage bucket keeps its objects in, one file per
+   * key. Omit when the app declares no buckets — there is no default,
+   * because a bucket silently rooted at the process's working directory is
+   * worse than an absent one.
+   */
+  objectStorageDirectory?: string;
   /**
    * Deliver one assembled queue batch — wire this to `dispatchQueueBatch`.
    * Required alongside `queues`; without it the messages would be stored
@@ -388,11 +515,15 @@ type NodePlatformOptions<Queues extends Record<string, {
   onQueueBatch?: NodeQueueHostOptions<Queues>["onBatch"];
   /** The app's `defineQueue` results, keyed by export name. Omit when the app declares no queues. */
   queues?: Queues;
+  /** The app's `defineWorkflow` results, keyed by export name. Omit when the app declares no workflows. */
+  workflows?: Workflows;
 } & NodeSchedulerHostOptions & NodeShardHostOptions & NodeShardRegistryOptions;
 /** Compose every contract this package provides over one `better-sqlite3` database. */
 declare const createNodePlatform: <Queues extends Record<string, {
   isLunoraQueue: true;
-}> = Record<string, never>>(options?: NodePlatformOptions<Queues>) => NodePlatform<Queues>;
+}> = Record<string, never>, Workflows extends Record<string, {
+  isLunoraWorkflow: true;
+}> = Record<string, never>>(options?: NodePlatformOptions<Queues, Workflows>) => NodePlatform<Queues, Workflows>;
 /** Options for {@link createNodeR2Bucket}. */
 interface NodeR2BucketOptions {
   /** The bucket directory — created on first write. Objects live here, one file per key. */
@@ -400,7 +531,7 @@ interface NodeR2BucketOptions {
 }
 /**
  * Create an `R2BucketLike` over the local filesystem. Any object shape
- * `createStorage({ bucket })` accepts — `put`/`get`/`head`/`delete`/`list` —
+ * `createStorage({ bucket, bucketName })` accepts — `put`/`get`/`head`/`delete`/`list` —
  * maps directly onto a file operation.
  */
 declare const createNodeR2Bucket: (options: NodeR2BucketOptions) => R2BucketLike;
@@ -473,45 +604,135 @@ interface NodeSocketHost {
 }
 /** Build the socket registry, persisting attachments and tags to `database`. */
 declare const createNodeSocketHost: (database: Database.Database) => NodeSocketHost;
-/** Options for {@link createNodeWorkflowHost}. */
-interface NodeWorkflowHostOptions<Workflows extends Record<string, {
-  isLunoraWorkflow: true;
-}>> {
-  /** Base env merged under the derived `WORKFLOW_*` bindings — surfaced to workflow bodies as `ctx.env` and used to resolve spawned children. */
-  env?: Record<string, unknown>;
-  /** How long (ms) the engine holds a cross-process lease while an activation runs, for stores that implement `acquire`. Defaults to 30000. */
-  leaseTtlMs?: number;
-  /** Where runs are persisted. Required — see the header for why there is no default. `createNodeWorkflowStore(database)` is the durable one. */
-  store: WorkflowStore;
-  /** The declared workflows keyed by their `lunora/workflows.ts` export name (e.g. `{ orderPipeline: orderPipeline }`). Values must be `defineWorkflow` results. */
-  workflows: Workflows;
-}
-/** A fully-wired Node workflow host. */
-interface NodeWorkflowHost<Workflows extends Record<string, {
-  isLunoraWorkflow: true;
-}>> {
-  /** Per-export-name `WorkflowBindingLike` — the map `ctx.workflows` consumes. */
-  readonly bindings: { [K in keyof Workflows]: WorkflowBindingLike; };
-  /**
-   * The caller's `env` plus one `WORKFLOW_&lt;EXPORT>` binding per workflow —
-   * merge this into a worker env so `ctx.spawn`/`ctx.parallel` resolve
-   * children through the same runtime.
-   */
-  readonly env: Record<string, unknown>;
-  /** The underlying visulima runtime — `sweep`/`signal` for a dev loop or tests. */
-  readonly runtime: WorkflowRuntime;
-}
-/**
- * Create a Node workflow host: compile every declared Lunora workflow onto the
- * visulima engine, derive the `WORKFLOW_*` env, and expose the per-workflow
- * `WorkflowBindingLike` handles.
- */
-declare const createNodeWorkflowHost: <Workflows extends Record<string, {
-  isLunoraWorkflow: true;
-}>>(options: NodeWorkflowHostOptions<Workflows>) => NodeWorkflowHost<Workflows>;
 /**
  * Build a durable {@link WorkflowStore} over a `better-sqlite3` connection.
  * Pass the result as `createNodeWorkflowHost({ store })`.
  */
 declare const createNodeWorkflowStore: (database: Database.Database) => WorkflowStore;
-export { type NodeGlobalContextDatabaseOptions, type NodeGlobalStore, type NodeGlobalStoreOptions, type NodePlatform, type NodePlatformOptions, type NodeQueueHost, type NodeQueueHostOptions, type NodeR2BucketOptions, type NodeSchedulerHost, type NodeSchedulerHostOptions, type NodeShard, type NodeShardHostOptions, type NodeShardRegistry, type NodeShardRegistryOptions, type NodeShardState, type NodeSocketHost, type NodeWorkflowHost, type NodeWorkflowHostOptions, createNodeGlobalStore, createNodePlatform, createNodeQueueHost, createNodeR2Bucket, createNodeSchedulerHost, createNodeShardHost, createNodeShardKvStore, createNodeShardRegistry, createNodeShardState, createNodeSocketHost, createNodeSqlExec, createNodeWorkflowHost, createNodeWorkflowStore };
+export {
+/**
+ * `@lunora/platform-node` — a Node implementation of the `@lunora/platform`
+ * host contracts (`ShardHost`, `SocketHost`, `ShardDirectory`, `ShardKvStore`,
+ * `SchedulerHost`) over `better-sqlite3` and an in-process socket/directory/
+ * scheduler registry.
+ *
+ * Promoted from `@lunora/platform`'s `node:sqlite` reference host
+ * (`src/conformance/reference-host.ts`) under plan 234, then hardened until the
+ * durability half of each contract actually holds: alarms and scheduler jobs
+ * are persisted **and re-armed on construction**, socket attachments and tags
+ * live in SQLite rather than a `Map`, and `.global()` tables run the real
+ * `@lunora/sql-store` core (`./node-global-store`). Each of those is pinned by
+ * a restart test — a second host over the same database file — not only by the
+ * TCK's simulated recycle.
+ *
+ * Three suites run against this package: `@lunora/platform/conformance`'s host
+ * TCK, `@lunora/shard-engine/conformance`'s engine suite, and its own
+ * lifecycle/global-store tests.
+ *
+ * **Emulated here**, and rated accordingly in `NODE_CAPABILITIES`
+ * (`@lunora/platform`): queues over a durable table (`./node-queue-host`), R2
+ * buckets over the local filesystem (`./node-r2-bucket`), workflows over the
+ * `@visulima/workflow` engine (`./node-workflow-host`), and cross-shard fan-out
+ * via `@lunora/runtime`'s query coordinator over the in-process shard registry.
+ * `createNodePlatform` binds all three declarations (`queues`, `workflows`,
+ * `objectStorageDirectory`) — a capability rated `emulated` with nothing bound
+ * is the one combination that fails at runtime with no diagnostic before it.
+ *
+ * **Still missing:** a dev server. There is no `lunora dev --target node`, and
+ * nothing here owns a timer, so queue delivery is driven by an explicit
+ * `poll()`. Also absent are the Cloudflare product bindings with no local
+ * equivalent — Vectorize, Workers AI, Browser Rendering, Containers, Analytics
+ * Engine, Pipelines, Secrets Store, Hyperdrive.
+ *
+ * `@lunora/config` ships a `node` **deploy** driver, so `--target node` resolves
+ * for `provision` — which reports, once, which declared features this target
+ * cannot serve, and writes nothing: there is no hosted control plane to deploy
+ * to and no `wrangler`-equivalent to shell out to. A deploy driver is not a dev
+ * server, which is why both statements above hold at once. See
+ * `plans/234-node-host-findings.md`.
+ */
+type NodeGlobalContextDatabaseOptions,
+/**
+ * `@lunora/platform-node` — a Node implementation of the `@lunora/platform`
+ * host contracts (`ShardHost`, `SocketHost`, `ShardDirectory`, `ShardKvStore`,
+ * `SchedulerHost`) over `better-sqlite3` and an in-process socket/directory/
+ * scheduler registry.
+ *
+ * Promoted from `@lunora/platform`'s `node:sqlite` reference host
+ * (`src/conformance/reference-host.ts`) under plan 234, then hardened until the
+ * durability half of each contract actually holds: alarms and scheduler jobs
+ * are persisted **and re-armed on construction**, socket attachments and tags
+ * live in SQLite rather than a `Map`, and `.global()` tables run the real
+ * `@lunora/sql-store` core (`./node-global-store`). Each of those is pinned by
+ * a restart test — a second host over the same database file — not only by the
+ * TCK's simulated recycle.
+ *
+ * Three suites run against this package: `@lunora/platform/conformance`'s host
+ * TCK, `@lunora/shard-engine/conformance`'s engine suite, and its own
+ * lifecycle/global-store tests.
+ *
+ * **Emulated here**, and rated accordingly in `NODE_CAPABILITIES`
+ * (`@lunora/platform`): queues over a durable table (`./node-queue-host`), R2
+ * buckets over the local filesystem (`./node-r2-bucket`), workflows over the
+ * `@visulima/workflow` engine (`./node-workflow-host`), and cross-shard fan-out
+ * via `@lunora/runtime`'s query coordinator over the in-process shard registry.
+ * `createNodePlatform` binds all three declarations (`queues`, `workflows`,
+ * `objectStorageDirectory`) — a capability rated `emulated` with nothing bound
+ * is the one combination that fails at runtime with no diagnostic before it.
+ *
+ * **Still missing:** a dev server. There is no `lunora dev --target node`, and
+ * nothing here owns a timer, so queue delivery is driven by an explicit
+ * `poll()`. Also absent are the Cloudflare product bindings with no local
+ * equivalent — Vectorize, Workers AI, Browser Rendering, Containers, Analytics
+ * Engine, Pipelines, Secrets Store, Hyperdrive.
+ *
+ * `@lunora/config` ships a `node` **deploy** driver, so `--target node` resolves
+ * for `provision` — which reports, once, which declared features this target
+ * cannot serve, and writes nothing: there is no hosted control plane to deploy
+ * to and no `wrangler`-equivalent to shell out to. A deploy driver is not a dev
+ * server, which is why both statements above hold at once. See
+ * `plans/234-node-host-findings.md`.
+ */
+type NodeGlobalStore,
+/**
+ * `@lunora/platform-node` — a Node implementation of the `@lunora/platform`
+ * host contracts (`ShardHost`, `SocketHost`, `ShardDirectory`, `ShardKvStore`,
+ * `SchedulerHost`) over `better-sqlite3` and an in-process socket/directory/
+ * scheduler registry.
+ *
+ * Promoted from `@lunora/platform`'s `node:sqlite` reference host
+ * (`src/conformance/reference-host.ts`) under plan 234, then hardened until the
+ * durability half of each contract actually holds: alarms and scheduler jobs
+ * are persisted **and re-armed on construction**, socket attachments and tags
+ * live in SQLite rather than a `Map`, and `.global()` tables run the real
+ * `@lunora/sql-store` core (`./node-global-store`). Each of those is pinned by
+ * a restart test — a second host over the same database file — not only by the
+ * TCK's simulated recycle.
+ *
+ * Three suites run against this package: `@lunora/platform/conformance`'s host
+ * TCK, `@lunora/shard-engine/conformance`'s engine suite, and its own
+ * lifecycle/global-store tests.
+ *
+ * **Emulated here**, and rated accordingly in `NODE_CAPABILITIES`
+ * (`@lunora/platform`): queues over a durable table (`./node-queue-host`), R2
+ * buckets over the local filesystem (`./node-r2-bucket`), workflows over the
+ * `@visulima/workflow` engine (`./node-workflow-host`), and cross-shard fan-out
+ * via `@lunora/runtime`'s query coordinator over the in-process shard registry.
+ * `createNodePlatform` binds all three declarations (`queues`, `workflows`,
+ * `objectStorageDirectory`) — a capability rated `emulated` with nothing bound
+ * is the one combination that fails at runtime with no diagnostic before it.
+ *
+ * **Still missing:** a dev server. There is no `lunora dev --target node`, and
+ * nothing here owns a timer, so queue delivery is driven by an explicit
+ * `poll()`. Also absent are the Cloudflare product bindings with no local
+ * equivalent — Vectorize, Workers AI, Browser Rendering, Containers, Analytics
+ * Engine, Pipelines, Secrets Store, Hyperdrive.
+ *
+ * `@lunora/config` ships a `node` **deploy** driver, so `--target node` resolves
+ * for `provision` — which reports, once, which declared features this target
+ * cannot serve, and writes nothing: there is no hosted control plane to deploy
+ * to and no `wrangler`-equivalent to shell out to. A deploy driver is not a dev
+ * server, which is why both statements above hold at once. See
+ * `plans/234-node-host-findings.md`.
+ */
+type NodeGlobalStoreOptions, type NodePlatform, type NodePlatformOptions, type NodeQueueHost, type NodeQueueHostOptions, type NodeR2BucketOptions, type NodeSchedulerHost, type NodeSchedulerHostOptions, type NodeShard, type NodeShardHostOptions, type NodeShardRegistry, type NodeShardRegistryOptions, type NodeShardState, type NodeSocketHost, type NodeWorkflowHost, type NodeWorkflowHostOptions, createNodeGlobalStore, createNodePlatform, createNodeQueueHost, createNodeR2Bucket, createNodeSchedulerHost, createNodeShardHost, createNodeShardKvStore, createNodeShardRegistry, createNodeShardState, createNodeSocketHost, createNodeSqlExec, createNodeWorkflowHost, createNodeWorkflowStore };