@volter/twin-runhuman 0.1.0

package/src/runhuman-server.ts

@@ -0,0 +1,32 @@
+// FETCH-FIRST (runtime contract R12b): the pack's HTTP surface is a plain
+// `(Request) => Promise<Response>` built by the kernel's ONE adaptation — a Worker/DO
+// entry mounts it in-process (no ports on workerd), and the local server is one line of
+// Bun.serve around the SAME closure. Vendor differences are VALUES on the config
+// (manifest, header extras, response headers); a wire that genuinely exceeds the common
+// shape (SSE, multipart, raw bytes) replaces the adapter with a hand-written fetch —
+// openai is that reference.
+import { handleRunhumanTwinRequest } from './runhuman-twin.ts';
+import { createTwinFetchFromHandler, serveHttp, statefulTwinManifest } from '@volter/world-core';
+
+export interface RunhumanTwinFetchOptions {
+  root?: string;
+  readOnly?: boolean;
+}
+
+export function createRunhumanTwinFetch(options: RunhumanTwinFetchOptions = {}): (request: Request) => Promise<Response> {
+  return createTwinFetchFromHandler(handleRunhumanTwinRequest, {
+    ...options,
+    manifest: statefulTwinManifest({ vendor: 'runhuman', twinOf: 'the Runhuman 1 API (runhuman.com/api)', stores: 'organizations, projects, API keys, testers, and jobs through their claim → results pipeline → completion lifecycle',
+      identity: 'Authenticate as RH1 does: `Authorization: Bearer rh_…` API keys bound to an organization, and web users (the tester side) in RH1\'s Clerk mock-mode form `Bearer clerk_<email>`; the tester\'s per-job testerToken comes from the claim. RH1 creates organizations, projects, keys and testers outside the job API, so a world seeds them with POST /_twin/organizations {name, id?}, /_twin/projects {organizationId, name, id?, defaultUrl?}, /_twin/api-keys {organizationId, key?}, /_twin/testers {email, alias?, devices?, organizationIds?}.',
+      notes: 'The AI results pipeline is folded into GET /api/tester/jobs/:jobId/processing/:processingJobId (the first read completes the run); time-driven monitors (claim-window expiry, overdue) and integrations are not modelled and answer RH1\'s JSON 404 with an x-twin-gap header.' }),
+  });
+}
+
+export async function createRunhumanTwinServer(options: { port?: number; root?: string; readOnly?: boolean } = {}): Promise<{ port: number; stop: () => void }> {
+  const server = await serveHttp({
+    port: options.port ?? 0,
+    idleTimeout: 60,
+    fetch: createRunhumanTwinFetch(options),
+  });
+  return { port: server.port ?? options.port ?? 0, stop: () => server.stop(true) };
+}