npm - @openrig/cli - Versions diffs - 0.3.0 → 0.3.1 - Mend

@openrig/cli 0.3.0 → 0.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (282) hide show

package/ui/dist/index.html CHANGED Viewed

@@ -6,8 +6,8 @@
     <title>OpenRig</title>
     <link rel="icon" href="data:," />
     <link href="https://fonts.googleapis.com/css2?family=Material+Symbols+Outlined:wght,FILL@100..700,0..1&display=swap" rel="stylesheet" />
-    <script type="module" crossorigin src="/assets/index-BDHU1JUK.js"></script>
-    <link rel="stylesheet" crossorigin href="/assets/index-DXTyJSqu.css">
+    <script type="module" crossorigin src="/assets/index-Rl3ZBrUg.js"></script>
+    <link rel="stylesheet" crossorigin href="/assets/index-C_Q5FczU.css">
   </head>
   <body>
     <div id="root"></div>

package/daemon/specs/agents/shared/skills/claude-compact-in-place/SKILL.md DELETED Viewed

@@ -1,100 +0,0 @@
----
-name: claude-compact-in-place
-description: Use when a Claude Code seat in an OpenRig topology needs compact-in-place recovery or marshal verification after compaction.
----
-# Claude Compact In Place
-## Purpose
-Use this skill when a Claude Code seat keeps the same OpenRig seat/session after `/compact` and must rebuild enough working context to continue safely. This is not succession, not seat handover, and not a generic memory note.
-Keep two layers separate:
-- **Restore mechanism:** seed from PreCompact output when present, Claude JSONL, touched-files inventory, active queue/session transcript or logs, root docs, and relevant source docs.
-- **Acceptance mechanism:** a marshal or peer audits the rebuilt mental model and gives explicit marshal acceptance before the seat resumes real work.
-Do not collapse these layers. A compacted Claude can sound coherent while important files were only injected, grepped, partially read, or not read.
-## Runtime Boundary
-This protocol is for Claude Code compact-in-place. It is not for Codex by default. Codex context management is different; do not intervene on Codex context percentage unless there are behavioral failure signals.
-## Policy Boundary
-The 400k token threshold is a policy target for considering preemptive Claude compaction on a 1M-context session. It is not an automatic action. Unattended compaction requires installed and dogfooded hooks, an audit path, and explicit policy or human authorization.
-Compact one Claude seat at a time unless a human or policy explicitly confirms spare marshal capacity. Do not compact multiple Claude seats at once as a convenience move.
-## Preflight
-Before restoring or auditing, recover canonical identity:
-```bash
-rig whoami --json
-rig whoami --session <target-seat> --json
-```
-The marshal verifies the target identity, seat name, runtime, active queue state, and transcript path before accepting any restore proof.
-## Required Evidence
-The target Claude should rebuild from concrete evidence, not just the compaction summary:
-- Claude JSONL transcript for the session.
-- Generated restore packet or PreCompact output, if present.
-- Touched-files inventory and recent git state.
-- Active queue file, queue packet body, session transcript, or session logs.
-- Rig bootstrap files such as `AGENTS.md`, `CLAUDE.md`, `CULTURE.md`, role guidance, and startup skills.
-- Relevant source docs, as-built docs, codemaps, and workstream trackers.
-If a required surface is absent, record it as `NOT-PRESENT`. If it exists but was skipped, record it as `NOT-READ`.
-## Required Proof
-The target must return an asked-vs-read-depth table before claiming readiness:
-| Surface | Source Of Ask | Read Depth | Evidence |
-|---|---|---|---|
-| `rig whoami --json` | marshal | FULL | canonical seat verified |
-| `<path>` | hook/marshal/touched-files | FULL / TARGETED / GREP / INJECTED / NOT-READ / NOT-PRESENT | lines, chunks, command, or reason |
-Allowed depth labels:
-- `FULL`: the whole surface was read after compaction.
-- `TARGETED`: selected ranges, head/tail, or named sections were read.
-- `GREP`: search excerpts were read.
-- `INJECTED`: content was present from hook, system, summary, or prior context, but not freshly read from disk.
-- `NOT-READ`: the surface exists but was not read.
-- `NOT-PRESENT`: the requested surface does not exist.
-The proof must also include canonical identity, JSONL or restore packet path, active queue items, selected touched files, skipped files with rationale, blockers, and exact next action.
-## Acceptance Rule
-The target may say `awaiting marshal acceptance` or `blocked`. It must not claim `RESTORED`, resume implementation, review, release, architecture, or orchestration work until marshal acceptance is explicit.
-Reject any proof that hides read depth, treats injection as a fresh read, omits queue reconciliation, or says "all docs read" without evidence.
-Accept only when:
-- The seat identity matches the target.
-- JSONL or restore artifacts were used, or their absence is explicitly explained.
-- Important recent-work files are either `FULL` or explicitly waived.
-- `INJECTED`, `TARGETED`, `GREP`, `NOT-READ`, and `NOT-PRESENT` surfaces are named honestly.
-- Active queue/session state is reconciled from durable evidence.
-- The target did not resume real work before marshal acceptance.
-## Marshal Follow-Up
-Ask these before accepting a clean-sounding proof:
-1. Which files were explicitly assigned, and which did you read in full after compaction?
-2. Which files were only injected by hook, summary, system context, or prior context?
-3. Which files were partial reads? Give line ranges or chunks.
-4. Which touched-files entries were important, and which were skipped?
-5. Did any read fail due to size? If yes, did you retry by chunk until complete?
-6. Which queue items changed between checkpoint and now?
-7. What would be unsafe for you to do before additional reads?
-If a mandatory surface is partial or injected only, ask for a corrected audit before acceptance.

package/daemon/specs/agents/shared/skills/process/containerized-e2e/SKILL.md DELETED Viewed

@@ -1,256 +0,0 @@
----
-name: containerized-e2e
-description: Run end-to-end dogfood tests inside Docker containers to simulate real user experiences. Use when you need to verify install paths, control plane functionality, UI rendering, or packaging correctness in a clean environment. Triggers include "containerized test", "Docker dogfood", "clean install test", "e2e in container", or testing that requires a fresh environment without dev-mode shortcuts.
-allowed-tools: Bash(docker:*), Bash(agent-browser:*), Bash(npx agent-browser:*)
----
-# Containerized E2E Testing
-Run OpenRig (or any npm-installable CLI + web UI project) through end-to-end testing inside Docker containers, simulating real user install and usage scenarios.
-## When to Use
-- Verifying the npm install path works from a packed tarball
-- Testing control plane functionality without live agent runtimes
-- Checking UI rendering via agent-browser in a clean environment
-- Regression testing after packaging changes
-- Phase boundary acceptance gates
-## When NOT to Use
-- Testing live agent behavior (send/capture/broadcast, whoami from inside an agent, transcript capture) — these need real claude-code/codex runtimes on the host
-- Quick feedback during active TDD cycles — too slow for the edit/test loop
-## Prerequisites
-- Docker installed and running
-- The repo builds successfully (`npm run build` for all workspaces)
-- `agent-browser` skill loaded (for UI verification commands)
-## Testing Personas
-### Fresh User
-A brand new user who has never installed OpenRig. Exercises the first-run experience.
-- Empty `~/.openrig/` directory
-- No existing rigs, snapshots, or specs
-- Tests: install, daemon start, preflight, doctor, first rig up, UI renders
-### Mature User
-A user with existing OpenRig state — rigs, snapshots, library additions, transcripts.
-- Pre-populated `~/.openrig/` via Docker volume persistence
-- Build this state organically: run the fresh-user tests first, and the volume accumulates real state
-- Tests: restore from existing snapshots, expand existing rigs, library with user-added specs, upgrade-path behaviors
-To set up a mature user volume:
-```bash
-# Create a named volume
-docker volume create openrig-mature-user
-# Run fresh-user tests with the volume mounted
-docker run -it --rm --shm-size=1g \
-  -v openrig-mature-user:/root/.openrig \
-  -v /tmp/openrig-e2e-artifacts:/artifacts \
-  openrig-e2e
-# The volume now has real state from actual rig commands
-# Subsequent runs with the same volume simulate a mature user
-```
-## Workflow
-### 1. Build the E2E Image
-Use the provided build script or do it manually:
-```bash
-# Using the build script (recommended)
-bash {SKILL_DIR}/scripts/build-e2e-image.sh /path/to/repo
-# Or manually:
-cd /path/to/repo
-npm run build --workspace @openrig/daemon
-npm run build --workspace @openrig/ui
-npm run build --workspace @openrig/cli
-bash scripts/build-package.sh
-cd packages/cli && npm pack --pack-destination /tmp/e2e-build
-cp {SKILL_DIR}/scripts/Dockerfile /tmp/e2e-build/
-mv /tmp/e2e-build/openrig-cli-*.tgz /tmp/e2e-build/openrig-cli.tgz
-cd /tmp/e2e-build && docker build -t openrig-e2e:latest .
-```
-### 2. Start the Container
-```bash
-# Fresh user (ephemeral state)
-docker run -d --rm --name openrig-e2e \
-  --shm-size=1g \
-  -v /tmp/openrig-e2e-artifacts:/artifacts \
-  openrig-e2e sleep infinity
-# Mature user (persistent volume)
-docker run -d --rm --name openrig-e2e \
-  --shm-size=1g \
-  -v openrig-mature-user:/root/.openrig \
-  -v /tmp/openrig-e2e-artifacts:/artifacts \
-  openrig-e2e sleep infinity
-```
-**Important:** Always use `--shm-size=1g` for Chromium stability during browser tests.
-### 3. Run Tests Inside the Container
-Execute commands via `docker exec`:
-```bash
-# Start the daemon
-docker exec openrig-e2e rig daemon start
-# Run preflight and doctor
-docker exec openrig-e2e rig preflight --json
-docker exec openrig-e2e rig doctor --json
-# Copy test specs into the container
-docker cp {SKILL_DIR}/templates/control-plane-test.yaml openrig-e2e:/workspace/
-docker cp {SKILL_DIR}/templates/expansion-pod-fragment.yaml openrig-e2e:/workspace/
-docker cp {SKILL_DIR}/templates/expansion-collision-fragment.yaml openrig-e2e:/workspace/
-# Launch a rig
-docker exec openrig-e2e rig up /workspace/control-plane-test.yaml --json
-# Check topology
-docker exec openrig-e2e rig ps --json
-docker exec openrig-e2e rig ps --nodes --json
-```
-### 4. Browser Testing Inside the Container
-agent-browser runs inside the container via `docker exec`:
-```bash
-# Open the daemon UI
-docker exec openrig-e2e agent-browser open http://127.0.0.1:7433
-docker exec openrig-e2e agent-browser wait --load networkidle
-# Inspect interactive elements
-docker exec openrig-e2e agent-browser snapshot -i
-# Capture screenshots
-docker exec openrig-e2e agent-browser screenshot /artifacts/screenshots/dashboard.png
-docker exec openrig-e2e agent-browser screenshot --annotate /artifacts/screenshots/dashboard-annotated.png
-# Navigate and verify specific surfaces
-docker exec openrig-e2e agent-browser click @e4  # Open specs drawer (ref from snapshot)
-docker exec openrig-e2e agent-browser wait 1000
-docker exec openrig-e2e agent-browser screenshot /artifacts/screenshots/specs-drawer.png
-```
-**ARM64 note:** The Dockerfile uses Debian's system chromium instead of Chrome for Testing, which is unavailable on Linux ARM64. The environment variables `AGENT_BROWSER_EXECUTABLE_PATH` and `AGENT_BROWSER_ARGS` are set in the image.
-### 5. Test Scenarios
-#### Control Plane Lifecycle
-```bash
-# Launch the multi-pod test spec
-docker exec openrig-e2e rig up /workspace/control-plane-test.yaml --json
-RIG_ID=$(docker exec openrig-e2e rig ps --json | jq -r '.[0].rigId')
-# Verify topology
-docker exec openrig-e2e rig ps --nodes --json
-# Expand with a new pod
-docker exec openrig-e2e rig expand "$RIG_ID" /workspace/expansion-pod-fragment.yaml --json
-# Verify expansion
-docker exec openrig-e2e rig ps --nodes --json
-# Test validation rejection (colliding namespace)
-docker exec openrig-e2e rig expand "$RIG_ID" /workspace/expansion-collision-fragment.yaml --json
-# Should fail with namespace collision error, rig unchanged
-# Snapshot
-docker exec openrig-e2e rig down "$RIG_ID" --snapshot --json
-# Restore and verify
-SNAPSHOT_ID=$(docker exec openrig-e2e rig snapshot list "$RIG_ID" | awk 'NR==2 {print $1}')
-docker exec openrig-e2e rig restore "$SNAPSHOT_ID" --rig "$RIG_ID"
-# Export
-docker exec openrig-e2e rig export "$RIG_ID" -o /artifacts/captures/exported-rig.yaml
-```
-#### UI Verification
-```bash
-# After launching a rig, verify the graph renders
-docker exec openrig-e2e agent-browser open http://127.0.0.1:7433
-docker exec openrig-e2e agent-browser wait --load networkidle
-docker exec openrig-e2e agent-browser snapshot -i
-docker exec openrig-e2e agent-browser screenshot --annotate /artifacts/screenshots/graph-with-rig.png
-# Open drawers and verify content
-docker exec openrig-e2e agent-browser snapshot -i  # Get fresh refs
-# Click through specs drawer, discovery drawer, rig detail, etc.
-# Take screenshots at each step
-```
-### 6. Cleanup
-```bash
-docker exec openrig-e2e rig daemon stop
-docker exec openrig-e2e agent-browser close
-docker stop openrig-e2e
-```
-### 7. Write Report
-Copy the report template and fill it in:
-```bash
-cp {SKILL_DIR}/templates/e2e-report-template.md /tmp/openrig-e2e-artifacts/report.md
-```
-Fill in results as tests complete — do not batch findings for the end.
-## Test Spec Templates
-| Template | Purpose |
-|----------|---------|
-| `templates/control-plane-test.yaml` | Multi-pod terminal-only rig spec (backend + frontend, 3 nodes, cross-pod edges) |
-| `templates/expansion-pod-fragment.yaml` | Pod fragment for expansion happy path (ops pod with cross-pod edge) |
-| `templates/expansion-collision-fragment.yaml` | Pod fragment that intentionally collides — for validation rejection testing |
-| `templates/e2e-report-template.md` | Structured test report template |
-## Scripts
-| Script | Purpose |
-|--------|---------|
-| `scripts/build-e2e-image.sh` | Build the Docker image from the repo (builds packages, packs tarball, builds image) |
-| `scripts/Dockerfile` | The proven Dockerfile — Node 22, tmux, system Chromium, agent-browser, OpenRig CLI |
-## Limitations
-- **No live agent runtimes.** The container does not include claude-code or codex. Use `runtime: terminal` specs for control plane testing. Test live agent behavior on the host.
-- **ARM64 browser workaround.** Chrome for Testing is unavailable on Linux ARM64. The Dockerfile uses Debian chromium. This is transparent to agent-browser commands.
-- **No GPU/display.** All browser testing is headless. Screenshots and videos capture what a user would see, but there is no visible browser window.
-## Combining with Host-Based Dogfood
-For complete coverage, use both approaches:
-| What to test | Where | Tool |
-|-------------|-------|------|
-| Install path, packaging | Container | This skill |
-| CLI commands, lifecycle | Container | This skill |
-| UI rendering, drawers | Container | This skill + agent-browser |
-| Validation/error paths | Container | This skill |
-| Live agent startup | Host | QA with /dogfood skill |
-| Communication (send/capture) | Host | QA with live agents |
-| Whoami from inside agent | Host | QA with live agents |
-| Transcript capture | Host | QA with live agents |
-| Chatroom with real participants | Host | QA with live agents |

package/daemon/specs/agents/shared/skills/process/containerized-e2e/scripts/Dockerfile DELETED Viewed

@@ -1,39 +0,0 @@
-# OpenRig Containerized E2E Testing Image
-#
-# Provides: Node 22, tmux, agent-browser (with system Chromium), OpenRig CLI
-# Usage:
-#   1. Build the CLI tarball: cd <repo>/packages/cli && npm pack
-#   2. Copy tarball to build context as openrig-cli.tgz
-#   3. docker build -t openrig-e2e .
-#   4. docker run -it --rm --shm-size=1g -v /tmp/e2e-artifacts:/artifacts openrig-e2e
-#
-# ARM64 note: Chrome for Testing is unavailable on Linux ARM64.
-# This image uses Debian's system chromium instead, pointed via
-# AGENT_BROWSER_EXECUTABLE_PATH.
-FROM node:22-bookworm
-ENV DEBIAN_FRONTEND=noninteractive
-ENV AGENT_BROWSER_ARGS=--no-sandbox
-ENV AGENT_BROWSER_EXECUTABLE_PATH=/usr/bin/chromium
-ENV OPENRIG_HOME=/root/.openrig
-RUN apt-get update \
- && apt-get install -y --no-install-recommends \
-    ca-certificates \
-    chromium \
-    curl \
-    git \
-    procps \
-    tmux \
- && rm -rf /var/lib/apt/lists/*
-RUN npm install -g agent-browser
-COPY openrig-cli.tgz /tmp/openrig-cli.tgz
-RUN npm install -g /tmp/openrig-cli.tgz \
- && rm /tmp/openrig-cli.tgz
-WORKDIR /workspace
-CMD ["/bin/bash"]

package/daemon/specs/agents/shared/skills/process/containerized-e2e/scripts/build-e2e-image.sh DELETED Viewed

@@ -1,37 +0,0 @@
-#!/bin/bash
-# Build the OpenRig containerized E2E testing image.
-#
-# Usage: ./build-e2e-image.sh [repo-root]
-#   repo-root defaults to the current directory.
-#
-# Produces: Docker image tagged openrig-e2e:latest
-set -euo pipefail
-REPO_ROOT="${1:-.}"
-SKILL_DIR="$(cd "$(dirname "$0")/.." && pwd)"
-BUILD_CTX="/tmp/openrig-e2e-build"
-echo "=== Building OpenRig packages ==="
-cd "$REPO_ROOT"
-npm run build --workspace @openrig/daemon
-npm run build --workspace @openrig/ui
-npm run build --workspace @openrig/cli
-bash scripts/build-package.sh
-echo "=== Packing CLI tarball ==="
-mkdir -p "$BUILD_CTX"
-cd "$REPO_ROOT/packages/cli"
-npm pack --pack-destination "$BUILD_CTX"
-echo "=== Preparing Docker build context ==="
-cp "$SKILL_DIR/scripts/Dockerfile" "$BUILD_CTX/Dockerfile"
-# Rename tarball to a stable name
-mv "$BUILD_CTX"/openrig-cli-*.tgz "$BUILD_CTX/openrig-cli.tgz"
-echo "=== Building Docker image ==="
-cd "$BUILD_CTX"
-docker build -t openrig-e2e:latest .
-echo "=== Done ==="
-echo "Run: docker run -it --rm --shm-size=1g -v /tmp/openrig-e2e-artifacts:/artifacts openrig-e2e"

package/daemon/specs/agents/shared/skills/process/containerized-e2e/templates/control-plane-test.yaml DELETED Viewed

@@ -1,40 +0,0 @@
-version: "0.2"
-name: control-plane-test
-summary: >
-  Multi-pod terminal-only topology for containerized control-plane testing.
-  Exercises pods, cross-pod edges, expansion targets, and snapshot/restore
-  without requiring live coding runtimes.
-pods:
-  - id: backend
-    label: Backend Team
-    members:
-      - id: api
-        runtime: terminal
-        agent_ref: "builtin:terminal"
-        profile: none
-        cwd: /tmp
-      - id: db
-        runtime: terminal
-        agent_ref: "builtin:terminal"
-        profile: none
-        cwd: /tmp
-    edges:
-      - kind: delegates_to
-        from: api
-        to: db
-  - id: frontend
-    label: Frontend Team
-    members:
-      - id: ui
-        runtime: terminal
-        agent_ref: "builtin:terminal"
-        profile: none
-        cwd: /tmp
-    edges: []
-edges:
-  - kind: delegates_to
-    from: frontend.ui
-    to: backend.api

package/daemon/specs/agents/shared/skills/process/containerized-e2e/templates/e2e-report-template.md DELETED Viewed

@@ -1,94 +0,0 @@
-# Containerized E2E Test Report
-Date: {{DATE}}
-Persona: {{PERSONA}}
-Image: openrig-e2e:latest
-## Summary
-- Tests run: {{TOTAL}}
-- Passed: {{PASSED}}
-- Failed: {{FAILED}}
-- Skipped: {{SKIPPED}}
-## Environment
-- Node: {{NODE_VERSION}}
-- tmux: {{TMUX_VERSION}}
-- Chromium: {{CHROMIUM_VERSION}}
-- OpenRig CLI: {{RIG_VERSION}}
-- Platform: {{PLATFORM}}
-## Test Results
-### Install & Boot
-| Test | Result | Notes |
-|------|--------|-------|
-| npm install -g | | |
-| rig daemon start | | |
-| rig preflight | | |
-| rig doctor | | |
-| UI loads in browser | | |
-### Rig Lifecycle
-| Test | Result | Notes |
-|------|--------|-------|
-| rig up (terminal-only spec) | | |
-| rig ps / rig ps --nodes | | |
-| Graph renders in browser | | |
-| rig down --snapshot | | |
-| rig restore | | |
-| Restored nodes match | | |
-### Expansion
-| Test | Result | Notes |
-|------|--------|-------|
-| rig expand (happy path) | | |
-| Graph updates after expand | | |
-| ps --nodes shows new nodes | | |
-| Expand with collision (rejected) | | |
-| Rig unchanged after rejection | | |
-### Snapshot/Restore with Expansion
-| Test | Result | Notes |
-|------|--------|-------|
-| Snapshot captures expanded pods | | |
-| Restore brings back expanded pods | | |
-| Cross-pod edges survive restore | | |
-| Export includes expanded topology | | |
-### CLI Surface
-| Test | Result | Notes |
-|------|--------|-------|
-| rig specs ls | | |
-| rig specs show | | |
-| rig config | | |
-| rig whoami (daemon down) | | |
-| rig export | | |
-### UI Surface (agent-browser)
-| Test | Result | Notes |
-|------|--------|-------|
-| Dashboard renders | | |
-| Explorer sidebar | | |
-| Specs drawer opens | | |
-| Discovery drawer opens | | |
-| System drawer opens | | |
-| Rig detail drawer | | |
-| Node detail in graph | | |
-## Bugs Found
-(Append each bug as discovered — do not batch)
-## Artifacts
-- Screenshots: /artifacts/screenshots/
-- Videos: /artifacts/videos/
-- CLI transcript: /artifacts/cli-transcript.txt

package/daemon/specs/agents/shared/skills/process/containerized-e2e/templates/expansion-collision-fragment.yaml DELETED Viewed

@@ -1,13 +0,0 @@
-# This fragment intentionally collides with the existing 'backend' pod.
-# Use it to verify that expansion validation rejects namespace collisions
-# and leaves the rig unchanged.
-pod:
-  id: backend
-  label: Colliding Pod
-  members:
-    - id: worker
-      runtime: terminal
-      agent_ref: "builtin:terminal"
-      profile: none
-      cwd: /tmp
-  edges: []

package/daemon/specs/agents/shared/skills/process/containerized-e2e/templates/expansion-pod-fragment.yaml DELETED Viewed

@@ -1,14 +0,0 @@
-pod:
-  id: ops
-  label: Operations
-  members:
-    - id: monitor
-      runtime: terminal
-      agent_ref: "builtin:terminal"
-      profile: none
-      cwd: /tmp
-  edges: []
-crossPodEdges:
-  - kind: delegates_to
-    from: ops.monitor
-    to: backend.api