@revisium/orchestrator 0.1.0 → 0.2.0-alpha.0

package/README.md

@@ -131,6 +131,7 @@ data directory, and DBOS database.
 
 ```sh
 pnpm install
+pnpm run build
 pnpm run revo -- start --profile dev
 pnpm run revo -- status --profile dev
 pnpm run revo -- doctor --profile dev
@@ -148,16 +149,93 @@ pnpm run revo -- stop --profile dev
 Explicit environment variables override the profile: `REVO_DATA_DIR`, `REVO_PORT`, `REVO_PG_PORT`,
 `REVO_GRAPHQL_PORT`, and `REVO_DBOS_DB`.
 
+### Build and globally install a local Revo
+
+This workflow is for local development/testing of the CLI and MCP server, **not** for publishing a release.
+
+**Build from the orchestrator checkout:**
+
+```sh
+pnpm install --frozen-lockfile
+pnpm run build
+```
+
+**Pack a tarball** (preferred over a directory-symlink install):
+
+```sh
+npm pack --pack-destination /private/tmp
+```
+
+This emits `/private/tmp/revisium-orchestrator-0.0.0.tgz` (filename tracks `package.json` `version`).
+
+**Identify the active Node prefix that owns the `revo` binary:**
+
+```sh
+which revo
+```
+
+Resolve the symlink and pick the prefix that contains both `bin/revo` and
+`lib/node_modules/@revisium/orchestrator`. `npm prefix -g` may point to a *different* prefix than the active
+`revo` binary (common under nvm), so derive the prefix from `which revo`, not from `npm prefix -g`.
+
+**Install the tarball globally into that prefix:**
+
+```sh
+npm install -g --prefix <active-node-prefix> /private/tmp/revisium-orchestrator-0.0.0.tgz
+```
+
+For nvm installs, the active prefix is usually the parent directory that contains both `bin/revo` and
+`lib/node_modules/@revisium/orchestrator`. Use that prefix consistently for both `npm` and `revo`.
+
+> **Warning:** do not use `npm install -g <local-dir>` from a temporary worktree. npm may install a symlink to
+> that directory; if the worktree is later removed, the global `revo` binary breaks. The tarball install copies
+> files and avoids this.
+
+**Restart and verify health:**
+
+```sh
+revo restart
+revo status
+revo doctor
+```
+
+**Verify the MCP tool surface after a global tool/schema change:**
+
+Restart the Codex session so MCP tool schemas are reloaded. `get_capabilities` should list:
+`get_run_attention`, `get_run_status`, `get_run_digest`, `get_run_events`, `get_agent_activity`,
+`get_agent_log`, `watch_run_changes`. Legacy observation tools are absent from the current contract.
+
+If Codex cannot expose `mcp__revo` tools after restart, check `~/.codex/config.toml`: use an absolute path to
+the active `revo` binary, for example `command = "<active-node-prefix>/bin/revo"`, rather than
+`command = "revo"` — the Codex process PATH may not include nvm.
+
 ## Front Doors
 
 `revo mcp` is the agent front door. It is a local stdio bridge to the daemon and exposes product-level tools for
 runs, gates, repository diagnostics, method discovery, and PR readiness.
 
+For source-iteration MCP testing, point the MCP client at the `pnpm run revo` script:
+
 ```sh
 codex mcp add --env REVO_PROFILE=dev revo-dev -- pnpm --dir /abs/path/to/orchestrator run revo -- mcp
 claude mcp add -e REVO_PROFILE=dev revo-dev -- pnpm --dir /abs/path/to/orchestrator run revo -- mcp
 ```
 
+For testing the same built entrypoint that the package uses, point the MCP client at `bin/revo.js`:
+
+```sh
+pnpm run build
+REVO_PROFILE=dev ./bin/revo.js restart --profile dev
+REVO_PROFILE=dev ./bin/revo.js doctor --profile dev
+codex mcp add --env REVO_PROFILE=dev revo-dev -- /abs/path/to/orchestrator/bin/revo.js mcp
+claude mcp add -e REVO_PROFILE=dev revo-dev -- /abs/path/to/orchestrator/bin/revo.js mcp
+```
+
+`bin/revo.js` imports `dist/cli/index.js`, so it does not see source edits until `pnpm run build` runs. After
+changing MCP tools or capabilities, rebuild, restart the `dev` stack, and reconnect or restart the MCP client session
+so the client refreshes its tool list. A built MCP smoke should confirm `get_capabilities.tools` contains
+`get_run_attention`, `get_run_status`, and `watch_run_changes`, with no legacy observation tools.
+
 For the `dev` profile, GraphQL is available at `http://127.0.0.1:19623/graphql`.
 
 ## Verification

package/control-plane/bootstrap.config.json

@@ -703,7 +703,7 @@
           "level": {
             "type": "string",
             "default": "",
-            "description": "cheap|standard|deep"
+            "description": "cheap|standard|deep|codex-cheap|codex-standard|codex-deep"
           },
           "provider": {
             "type": "string",
@@ -1017,6 +1017,48 @@
         "updated_at": "2026-06-03T00:00:00.000Z"
       }
     },
+    {
+      "tableId": "model_profiles",
+      "rowId": "codex-standard",
+      "data": {
+        "id": "codex-standard",
+        "level": "codex-standard",
+        "provider": "openai",
+        "model_id": "gpt-5.5",
+        "params": "{}",
+        "cost_per_input": 2.0,
+        "cost_per_output": 8.0,
+        "updated_at": "2026-06-03T00:00:00.000Z"
+      }
+    },
+    {
+      "tableId": "model_profiles",
+      "rowId": "codex-cheap",
+      "data": {
+        "id": "codex-cheap",
+        "level": "codex-cheap",
+        "provider": "openai",
+        "model_id": "gpt-5.5",
+        "params": "{}",
+        "cost_per_input": 2.0,
+        "cost_per_output": 8.0,
+        "updated_at": "2026-06-03T00:00:00.000Z"
+      }
+    },
+    {
+      "tableId": "model_profiles",
+      "rowId": "codex-deep",
+      "data": {
+        "id": "codex-deep",
+        "level": "codex-deep",
+        "provider": "openai",
+        "model_id": "gpt-5.5",
+        "params": "{}",
+        "cost_per_input": 2.0,
+        "cost_per_output": 8.0,
+        "updated_at": "2026-06-03T00:00:00.000Z"
+      }
+    },
     {
       "tableId": "routing_policy",
       "rowId": "pipeline",