@hachej/boring-agent 0.1.78 → 0.1.80

package/docs/runtime.md

@@ -2,27 +2,10 @@
 
 # Runtime Modes and Provisioning
 
-When a boring-bash filesystem/exec environment is attached, the agent supports
-three execution modes controlling how `bash` and filesystem tools run.
-
-Pure/headless agents use `runtime: 'none'` instead. That mode has no
-`Workspace`, no `Sandbox`, no cwd, no file routes, no file tools, and no bash
-tools. It is not selected with `BORING_AGENT_MODE`; the host composes a
-runtime-free agent and supplies only non-bash tools plus session/model
-configuration. If the host later attaches a filesystem/exec environment, that
-attachment enters the boring-bash runtime contract below.
-
-If a host renders the workspace frontend against `runtime: 'none'`, it must also
-exclude the default filesystem frontend plugin today: pass
-`excludeDefaults: ['filesystem']` through `WorkspaceAgentFront`/`WorkspaceProvider`
-(or the equivalent core workspace props). The frontend default is still
-`filesystemPlugin`, whose plugin id is `"filesystem"`; without that exclusion the
-file tree/editor contributions render and call file routes that pure mode does
-not register. `ChatFirstAuthenticatedShell` already supplies this exclusion by
-default. The planned end state is capability-driven auto-exclusion from an
-environment filesystem capability of `none`, owned by the P3/P4 route/tool and
-file-UI plugin move and the #391 zero-residue invariant 16; this PR does not add
-frontend gating.
+Every v1 agent is bound to an authorized workspace and an approved runtime
+adapter. The agent supports three built-in execution modes controlling how
+`bash` and filesystem tools run. A headless host may omit its UI/presentation
+surface, but it still supplies the same workspace-backed runtime contract.
 
 ## Modes
 
@@ -256,9 +239,8 @@ as the `runtimeModeAdapter` option to `createAgentApp(opts)` or
 `resolveMode()` only knows the three built-ins and throws for unknown ids,
 telling you to pass `runtimeModeAdapter`.
 
-This interface is for environments that intentionally provide a workspace,
-filesystem/search, and sandbox/execution substrate. Pure `runtime: 'none'`
-agents do not construct a `RuntimeBundle`.
+Each adapter provides a workspace, filesystem/search, and sandbox/execution
+substrate as one runtime bundle.
 
 ```ts
 interface RuntimeModeAdapter {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hachej/boring-agent",
-  "version": "0.1.78",
+  "version": "0.1.80",
   "type": "module",
   "license": "MIT",
   "description": "Pane-embeddable coding agent. Ships direct/local/vercel-sandbox execution modes behind one interface.",
@@ -27,6 +27,11 @@
       "import": "./dist/server/index.js",
       "default": "./dist/server/index.js"
     },
+    "./server/worker": {
+      "types": "./dist/server/worker/index.d.ts",
+      "import": "./dist/server/worker/index.js",
+      "default": "./dist/server/worker/index.js"
+    },
     "./front": {
       "types": "./dist/front/index.d.ts",
       "import": "./dist/front/index.js"
@@ -79,7 +84,7 @@
     "use-stick-to-bottom": "^1.1.6",
     "yaml": "^2.9.0",
     "zod": "^3.25.76",
-    "@hachej/boring-ui-kit": "0.1.78"
+    "@hachej/boring-ui-kit": "0.1.80"
   },
   "devDependencies": {
     "@antithesishq/bombadil": "0.6.1",
@@ -90,6 +95,7 @@
     "@types/react-dom": "^19.1.3",
     "@vitejs/plugin-react": "^4.7.0",
     "ajv": "^8.20.0",
+    "esbuild": "^0.25.12",
     "postcss": "^8.5.15",
     "react": "^19.2.7",
     "react-dom": "^19.2.7",