antechamber 1.0.41 → 2.0.1

package/extensions/antechamber/README.md

@@ -0,0 +1,100 @@
+# antechamber: OpenChamber extension
+
+One OpenChamber 2.x extension that installs [antechamber](../../README.md) and OmO, keeps them at the versions this
+release pins, and adds the OmO views to OpenChamber:
+
+- **OmO Graph**, a rail panel (and a full-screen page) drawing the OmO sub-agents behind the open session as a live
+  graph. See [docs/GRAPH.md](docs/GRAPH.md).
+- **OmO Work**, a section of the Work Status panel with the session's todo phases, goal timer and other wake
+  sources. See [docs/WORK.md](docs/WORK.md).
+- **OmO tool headers**: eval cells read `JS Eval` (or `Python Eval`) and their summary instead of "Shell Command",
+  and a sub-agent card reads its agent type and description instead of "Agent Task".
+- **The runtime**: `bin/opencode-antechamber`, the program OpenChamber runs as its OpenCode server. Its first start
+  installs, with Bun, the antechamber release whose version is this extension's version, and the `omo-ai` that
+  release pins, into `~/.antechamber/runtime/<version>`.
+
+It replaces the separate OmO Graph, OmO Work and OmO Compatibility extensions of antechamber 1.x.
+
+## Requirements
+
+- OpenChamber **2.3.2 or newer**, web or desktop. VS Code and mobile load no extensions.
+- [Bun](https://bun.sh) 1.4 or newer on the machine OpenChamber runs on, on `PATH` or in `~/.bun/bin`.
+- Network access to the npm registry the first time each version starts.
+
+## Install
+
+1. In OpenChamber, open **Settings → Extensions → Add → URL** and enter `https://github.com/eliottness/antechamber`.
+   The repository root carries this extension's manifest (paths rebased into `extensions/antechamber/`) and the
+   built files are committed, so the clone is the extension. `https://github.com/eliottness/antechamber#extension/antechamber`
+   installs the same extension from a branch holding only its files.
+2. Approve what it asks for: **sessions**, to follow the open session and open sub-agent sessions, and **a local
+   service that runs `bun`**, which installs the runtime and reads the OmO task store and antechamber's run records.
+3. Open the **OmO** rail panel and its settings (the sliders icon). The **Runtime** block shows the install and the
+   launcher's path. The service starts installing as soon as a panel or the Work section opens.
+4. In **Settings → OpenCode CLI**, set the path to that launcher: the path the Runtime block shows,
+   `<OpenChamber data dir>/extensions/antechamber/extensions/antechamber/bin/opencode-antechamber` for the repository URL. OpenChamber restarts its server on
+   antechamber.
+
+Other ways to add it: a **Folder** (`extensions/antechamber` of an npm install or a built checkout; `antechamber
+setup` prints it), or the release **ZIP**
+(`https://github.com/eliottness/antechamber/releases/latest/download/antechamber-openchamber.zip`). OpenChamber
+checks only Git installs for updates.
+
+For a server you reach over HTTP:
+
+```bash
+curl -sX POST "$OC/api/guests" -H 'content-type: application/json' \
+  -d '{"url":"https://github.com/eliottness/antechamber"}'
+curl -sX PUT "$OC/api/guests/antechamber/capabilities" -H 'content-type: application/json' \
+  -d '{"granted":["sessions","service"]}'
+```
+
+## Updating
+
+Every antechamber release publishes the extension at its own version to the `extension/antechamber` branch, and
+OpenChamber offers it under **Update** in Settings → Extensions. Updating the extension is updating antechamber and
+OmO: the next time OpenChamber starts its server, the launcher installs the new pair. OpenChamber's own OpenCode
+Update action runs the launcher's `upgrade`, which only points here.
+
+The previous runtime stays installed for an adapter that is still running from it; older ones are removed.
+
+## Settings
+
+The launcher reads these from OpenChamber's environment (the service never sees them, because OpenChamber starts
+extension services with a minimal environment):
+
+| Variable | Default | Effect |
+|---|---|---|
+| `ANTECHAMBER_RUNTIME_DIR` | `~/.antechamber/runtime` | Where runtimes are installed |
+| `ANTECHAMBER_RUNTIME_SPEC` | unset | A local antechamber tarball or folder to run instead of the pinned release (development) |
+
+Every other antechamber setting (`ANTECHAMBER_PI_BINARY`, `ANTECHAMBER_STATE_DIR`, ...) works as documented in
+[docs/configuration.md](../../docs/configuration.md). If your deployment moves the state or agent directories, enter the
+same paths in the Graph panel's settings and the Work section's **Data path**.
+
+## How it works
+
+```
+OpenChamber --spawn--> bin/opencode-antechamber --exec--> bun <runtime>/node_modules/antechamber/dist/cli.js serve
+                          |                                   `--spawn--> <runtime>/node_modules/omo-ai/bin/omo.js --mode rpc
+                          `--bun runtime/launcher.js resolve (install when missing)
+
+panel / section (sandboxed iframes) --serviceRequest--> OpenChamber host --loopback + token--> service/main.js
+                                                         /graph   reads the OmO task store and the session registry
+                                                         /status  relays antechamber's /antechamber/work-status routes
+                                                         /runtime reports and starts the runtime install
+```
+
+The launcher and the service share one install: a lock directory beside the runtime lets whichever starts first
+install, and the other waits. `bun install` runs in a staging directory with `omo-ai` trusted (its postinstall
+prepares OmO's engine), and the runtime is moved into place only once antechamber's CLI is there.
+
+## Development
+
+From the repository root: `npm run build:extension` syncs the root `package.json` manifest and bundles the panel and the section (browser IIFEs), the service
+(ESM for OpenChamber's runtime) and the launcher (ESM for Bun); `npm test`, `npm run typecheck`, `npm run lint` and
+`npm run format:check` cover it; `npm run pack:extension -- out.zip` writes the release archive. To run a local
+build through the launcher, `npm pack` antechamber and point `ANTECHAMBER_RUNTIME_SPEC` at the tarball.
+
+Sources: `src/graph/` (panel, layout, task store, `/graph`), `src/work/` (section, `/status` relay),
+`src/runtime/` (install manager and launcher), `src/service.ts` (the one service).

package/extensions/antechamber/bin/opencode-antechamber

@@ -0,0 +1,42 @@
+#!/bin/sh
+# OpenChamber launcher: point Settings -> OpenCode CLI (settings.opencodeBinary) at this file.
+# OpenChamber runs `<binary> serve --hostname H --port P` and `<binary> --version`; its Update action
+# runs `<binary> upgrade`. The first `serve` installs the antechamber release this extension pins (and
+# the OmO it pins) with Bun; updating the extension in Settings -> Extensions updates both.
+set -eu
+SCRIPT_PATH=$0
+while [ -h "$SCRIPT_PATH" ]; do
+  SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$SCRIPT_PATH")" && pwd)"
+  LINK="$(readlink "$SCRIPT_PATH")"
+  case "$LINK" in
+    /*) SCRIPT_PATH=$LINK ;;
+    *) SCRIPT_PATH="$SCRIPT_DIR/$LINK" ;;
+  esac
+done
+SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$SCRIPT_PATH")" && pwd)"
+LAUNCHER="$SCRIPT_DIR/../runtime/launcher.js"
+# GUI apps and services often have a PATH without Bun's install directory.
+BUN=$(command -v bun || true)
+for CANDIDATE in "${BUN_INSTALL:-${HOME:-}/.bun}/bin/bun" "${HOME:-}/.bun/bin/bun"; do
+  if [ -z "$BUN" ] && [ -x "$CANDIDATE" ]; then BUN=$CANDIDATE; fi
+done
+if [ -z "$BUN" ]; then
+  echo "opencode-antechamber: bun not found on PATH or in ~/.bun/bin; install it from https://bun.sh" >&2
+  exit 1
+fi
+case "${1:-}" in
+  serve)
+    shift
+    CLI=$("$BUN" "$LAUNCHER" resolve)
+    ANTECHAMBER_MANAGED=openchamber-extension
+    export ANTECHAMBER_MANAGED
+    exec "$BUN" "$CLI" serve "$@"
+    ;;
+  --version|-v) exec "$BUN" "$LAUNCHER" version ;;
+  upgrade)
+    echo "antechamber is managed by its OpenChamber extension: update it in Settings -> Extensions."
+    exit 0
+    ;;
+esac
+echo "opencode-antechamber: unsupported command '${1:-}' (only 'serve', '--version' and 'upgrade' are implemented)" >&2
+exit 1

package/extensions/{omo-dag/docs/DESIGN.md → antechamber/docs/GRAPH.md}

@@ -25,7 +25,7 @@ does that in ~2 ms with an mtime cache and returns one JSON document.
    `description` / `name`, `agent_type` / `category`, `model`, the
    `created_at` / `started_at` / `terminal_at` timestamps,
    `final_response`, `error_message`, `run_stats`, `spawn_spec.prompt`.
-2. **Connector registry**: `<stateDir>/sessions.json`, mapping OpenChamber
+2. **Connector registry**: `<stateDir>/sessions.sqlite` (`sessions.json` before antechamber 2.0), mapping OpenChamber
    session ids to OmO session ids and titles.
 
 Task discovery reads regular `.json` files and skips directories and symlinks.
@@ -45,7 +45,7 @@ uses the same identity rules so `openSession` opens the correct child.
 Legacy deletion tombstones retain their owning parent's bare identity, even
 when they predate task metadata in the registry.
 
-## Graph model (`src/graph.ts`)
+## Graph model (`src/graph/graph.ts`)
 
 - **Run**: every task whose `root_session_id` equals the resolved root. The
   root is resolved from the open session: it is either a root itself, a
@@ -69,7 +69,7 @@ when they predate task metadata in the registry.
   failed, `cancelled`/`canceled`/`killed` → cancelled. The raw status is kept
   for the label, so `lost` reads as `lost`.
 
-## Layout (`src/layout.ts`)
+## Layout (`src/graph/layout.ts`)
 
 Columns are fixed-width, and panel CSS dimensions come from the same card-size
 constants used by the layout. Within a column, cards stack in the order of their
@@ -80,7 +80,7 @@ Béziers. Several edges sharing one side are spread over the card's middle
 band (Archify's "spread shared endpoints deterministically" rule) instead of
 piling onto one point.
 
-## Interaction (`src/panel.ts`, `panel/index.html`)
+## Interaction (`src/graph/panel.ts`, `panel/index.html`)
 
 - Hover or focus a card: direct inputs (amber) and outputs (accent) are fully
   lit, the transitive upstream/downstream reach stays half-lit, and
@@ -102,7 +102,7 @@ piling onto one point.
   and binds to `127.0.0.1` on the port the host assigns.
 - The optional `agentDir` / `stateDir` query parameters let the panel point
   it at other directories. It reads only `*.json` task records and
-  `sessions.json` under them. The service runs with the user's permissions
+  `sessions.sqlite` (or `sessions.json`) under them. The service runs with the user's permissions
   (OpenChamber's approval dialog says so), so this is not a sandbox. It just
   keeps the surface small.
 - Prompts and final responses stay local. They reach only the panel the user

package/extensions/{omo-work/docs/DESIGN.md → antechamber/docs/WORK.md}

@@ -30,11 +30,11 @@ OpenChamber host ── loopback + OPENCHAMBER_SERVICE_TOKEN ──▶ service/m
   `service`, and a `panel` block with no entry. OpenChamber 2.x's manifest
   parser requires a `panel` object, but without `panel.entry` there is no rail
   icon or panel; the section is the only surface.
-- **Frame** (`src/status.ts`, `src/view.ts`): renders the snapshot. It follows
+- **Frame** (`src/work/status.ts`, `src/work/view.ts`): renders the snapshot. It follows
   the open session through `host.onSession`, sizes itself through
   `host.setHeight`, and publishes one host header control, **Data path**, when
   the host supports status controls.
-- **Service** (`src/service.ts`, `src/discovery.ts`): stateless relay. It finds
+- **Service** (`src/work/routes.ts`, `src/work/discovery.ts`): stateless relay. It finds
   running antechamber servers through their run records and forwards the
   frame's requests.
 - **Adapter** (`src/work-status.ts` in antechamber): builds the snapshot and
@@ -58,7 +58,7 @@ The frame shows `todo`, `goal` and `wakeSources`. `monitors`, `evalCells` and
 `background` stay in the snapshot, and the adapter keeps its
 `/antechamber/work-status/<session>/eval/<cell>[/stop]` routes, for section
 versions installed before these moved to OpenChamber's background commands
-(ZIP installs never update). The frame checks the envelope (`src/model.ts`) and
+(ZIP installs never update). The frame checks the envelope (`src/work/model.ts`) and
 imports these types from the adapter, so a shape change on either side fails
 the typecheck.
 

package/extensions/antechamber/package.json

@@ -0,0 +1,60 @@
+{
+  "name": "antechamber-openchamber",
+  "version": "2.0.1",
+  "description": "OpenChamber extension for antechamber: installs and pins the antechamber server and OmO, draws the OmO Graph and the OmO Work section, and titles OmO tool cards",
+  "private": true,
+  "type": "module",
+  "license": "MIT",
+  "openchamber": {
+    "apiVersion": 1,
+    "engines": {
+      "openchamber": ">=2.3.2"
+    },
+    "contributes": {
+      "panel": {
+        "id": "antechamber",
+        "name": "OmO",
+        "icon": "icon.svg",
+        "entry": "panel/index.html"
+      },
+      "page": {
+        "entry": "panel/index.html",
+        "title": "OmO Graph"
+      },
+      "statusSection": {
+        "entry": "status/index.html",
+        "title": "OmO Work",
+        "height": 120
+      },
+      "capabilities": [
+        "sessions"
+      ],
+      "service": {
+        "entry": "service/main.js",
+        "runtime": "host",
+        "permissions": {
+          "exec": [
+            "bun"
+          ]
+        }
+      },
+      "tools": [
+        {
+          "match": "shell",
+          "title": "{metadata.evalTitle}",
+          "subtitle": "{metadata.evalSubtitle}"
+        },
+        {
+          "match": "task",
+          "title": "{metadata.agentTitle}",
+          "subtitle": "{metadata.agentSubtitle}"
+        },
+        {
+          "match": "agent",
+          "title": "{metadata.agentTitle}",
+          "subtitle": "{metadata.agentSubtitle}"
+        }
+      ]
+    }
+  }
+}

package/extensions/{omo-dag → antechamber}/panel/index.html

@@ -51,6 +51,12 @@
       #settings .row { display: flex; justify-content: flex-end; gap: 6px; }
       #settings button { padding: 5px 12px; border-radius: 6px; border: 1px solid var(--border); background: var(--surface-2); cursor: pointer; }
       #settings #btn-save { background: var(--accent); color: var(--oc-primary-fg, #001); border-color: transparent; }
+      #runtime { display: grid; gap: 4px; padding-bottom: 8px; border-bottom: 1px solid var(--border); font-size: 11px; color: var(--muted); }
+      #runtime strong { color: var(--fg); font-weight: 600; }
+      #runtime code { font: 11px var(--mono); color: var(--fg); word-break: break-all; user-select: all; -webkit-user-select: all; }
+      #runtime[data-state="failed"] { color: var(--bad); }
+      #runtime[data-state="installing"] { color: var(--run); }
+      #runtime .row { justify-content: flex-start; }
 
       #viewport { position: relative; flex: 1; overflow: hidden; cursor: grab; touch-action: none; -webkit-user-select: none; user-select: none;
         background-image: radial-gradient(color-mix(in srgb, var(--muted) 22%, transparent) 1px, transparent 1px);
@@ -151,12 +157,13 @@
           <button class="tool" id="btn-in" type="button" title="Zoom in (+)" aria-label="Zoom in">
             <svg aria-hidden="true" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M5 12h14M12 5v14"/></svg>
           </button>
-          <button class="tool" id="btn-settings" type="button" title="Data paths" aria-label="Data paths" aria-expanded="false" aria-controls="settings">
+          <button class="tool" id="btn-settings" type="button" title="Settings" aria-label="Settings" aria-expanded="false" aria-controls="settings">
             <svg aria-hidden="true" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M4 7h10M18 7h2M4 17h4M12 17h8"/><circle cx="16" cy="7" r="2"/><circle cx="10" cy="17" r="2"/></svg>
           </button>
         </div>
       </header>
       <form id="settings" hidden>
+        <section id="runtime" aria-live="polite"><strong>Runtime</strong><span id="runtime-state">Checking…</span></section>
         <label>OmO agent directory <input name="agentDir" placeholder="~/.omo/agent (default, then ~/.pi/agent)" autocomplete="off" spellcheck="false" /></label>
         <label>Connector state directory <input name="stateDir" placeholder="~/.config/antechamber (default)" autocomplete="off" spellcheck="false" /></label>
         <div class="row"><button id="btn-save" type="button">Save</button></div>