castle-web-cli 0.4.78 → 0.4.79

package/dist/native/types.js

@@ -0,0 +1,41 @@
+// Shapes for the native (in-process, OpenRouter-backed) agent backend --
+// see the plan at native_openrouter_agent_loop_fd7d9b3e.plan.md, "Path B".
+//
+// These MIRROR the non-exported CliRunOpts / CliRunResult / CliUsage
+// interfaces in cli/src/agent.ts (see runAgentCli there), which normalize
+// the headless `claude` / `cursor-agent` CLI backends into onDelta/onActivity/
+// onThinking hooks plus a { finalText, error, usage, filesTouched, crashed }
+// result. This file is a SEPARATE set of types for now (new-files-only
+// constraint -- agent.ts is being edited concurrently by a sibling change),
+// not a re-export, so field names differ in a few places. When the native
+// backend is wired into agent.ts, expect one of these two outcomes:
+//
+//   1. CliRunOpts/CliRunResult are widened to a shape both backends share
+//      (command/args/parser and children become backend-specific extras), or
+//   2. the call site maps between the two shapes directly:
+//        - NativeRunResult.text            -> CliRunResult.finalText
+//        - NativeRunResult.error/usage/filesTouched/crashed -> same names
+//        - CliRunResult.ok                 <- derived as
+//              `!result.error && !result.crashed` (no native equivalent of
+//              a process exit code -- "ok" always follows from the other
+//              two fields)
+//        - CliRunOpts.children (Set<ChildProcess>) has no native
+//          equivalent -- runAgentNative takes `signal` (AbortSignal)
+//          instead, so a caller cancels a run the same way it would abort
+//          any other fetch-based operation. The wiring step would create one
+//          AbortController per run and adapt it to whatever cancellation
+//          registry agent.ts uses for CLI children.
+//        - CliRunOpts.command/args/parser have no native equivalent --
+//          replaced by `model` (the free-form OpenRouter model id) and
+//          `apiKey`.
+//        - CliRunOpts.logPath maps to NativeRunOpts.logPath: same file
+//          locations (tasks/<id>/log.jsonl, .castle/agent/router-log.jsonl),
+//          same append-JSONL discipline, but the native lines are STRUCTURED
+//          run events (init/assistant/tool_result/eviction/retry/result --
+//          see createRunLogger in loop.ts) rather than raw CLI stream-json.
+//
+// Turns stay stateless exactly as they are today: the caller rebuilds one big
+// prompt string per turn (buildRouterPrompt/buildTaskPrompt) and passes it as
+// `prompt`; runAgentNative holds the resulting message array only for the
+// lifetime of that one call.
+export {};

package/dist/serve.js

@@ -255,6 +255,18 @@ export async function serve(dir, options = {}) {
     const agentServer = createAgentServer({
         deckDir: projectDir,
         deckLabel: path.basename(projectDir),
+        port,
+        // Same effect as the WS server's own 'restart' branch below (invalidate
+        // then tell every connected tab to reload), called directly in-process
+        // instead of round-tripping through a WebSocket message -- this is what
+        // backs the native `restart` tool (see native/tools.ts) so a smith task
+        // agent doesn't have to spawn `npm run restart` (node + castle-web CLI +
+        // its own WS client) just to send one message to a serve it's already
+        // running inside of.
+        restart: () => {
+            invalidateModuleCaches(viteHolder.vite);
+            broadcast({ type: 'restart' });
+        },
     });
     process.on('exit', () => agentServer.shutdown());
     const vite = await createServer({