@hasna/loops 0.4.1 → 0.4.2

package/README.md

@@ -22,7 +22,7 @@ It supports deterministic command loops, JSON-defined workflows, and guarded CLI
 OpenLoops has three deployment modes:
 
 - `local`: SQLite in `LOOPS_DATA_DIR` is authoritative and `loops-daemon` executes scheduled work.
-- `self_hosted`: a user-operated `loops-api` control plane contract. This release exposes status/API/runner foundations; claim protocol and non-local execution are follow-up work.
+- `self_hosted`: a user-operated `loops-api` control plane contract. This release exposes status, storage-backed `/v1` loop CRUD and run listing, runner claim/heartbeat/finalize protocol endpoints, and a one-shot `loops-runner run-once` execution path for embedded control-plane hosts; full fleet rollout and migration tooling are follow-up work.
 - `cloud`: a hosted control-plane contract. This release exposes client/runner status only; hosted tenant auth and infrastructure live outside this package.
 
 `local` is the default and requires no network, token, Postgres, or hosted

package/dist/api/index.d.ts

@@ -1,11 +1,17 @@
 #!/usr/bin/env bun
+import type { LoopStorageContract } from "../lib/storage/contract.js";
 export declare function apiStatus(): {
     ok: boolean;
     service: string;
     status: import("../index.js").LoopDeploymentStatus;
 };
-export declare function createLoopsApiServer(opts?: {
+export interface LoopsApiServerOptions {
     host?: string;
     port?: number;
-}): Bun.Server<undefined>;
+    storage?: LoopStorageContract;
+    bodyLimitBytes?: number;
+    evidenceLimitBytes?: number;
+    now?: () => Date;
+}
+export declare function createLoopsApiServer(opts?: LoopsApiServerOptions): Bun.Server<undefined>;
 export declare function main(argv?: string[]): Promise<void>;