@polderlabs/bizar-omp 0.5.0 → 0.6.0

package/README.md

@@ -10,33 +10,78 @@
     <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-18181b?style=flat-square" alt="MIT license" /></a>
   </p>
 
-  <p><strong>Native autonomous engineering workflows for oh-my-pi.</strong><br />
-  Plan proportionally, run work in durable sessions, and finish with evidence you can inspect.</p>
+  <p><strong>Native engineering workflows for oh-my-pi.</strong><br />
+  Plan the work, keep sessions alive, verify the result, and inspect the proof.</p>
 </div>
 
----
+> [!IMPORTANT]
+> BizarHarness OMP is an extension for [oh-my-pi](https://github.com/can1357/oh-my-pi), not a second agent runtime. OMP still owns models, credentials, tools, task execution, sessions, and conversation state.
 
-## What Bizar OMP is
+## Start here
 
-BizarHarness OMP is a native [oh-my-pi](https://github.com/can1357/oh-my-pi) extension for engineering work. It adds workflow intent, acceptance criteria, evidence freshness, specialist roles, scoped integration, and a durable session launcher while leaving OMP in charge of sessions, models, credentials, tools, task execution, and conversation state.
+Choose the path that matches what you are trying to do:
 
-| You need | Bizar OMP provides |
+| Your goal | Run this | What it gives you |
+| --- | --- | --- |
+| Set up the complete experience | `npx --yes @polderlabs/bizar-omp setup` | `omb`, `bizar-omp`, the OMP extension, native agents, skills, rules, prompts, tools, and model roles |
+| Preview setup before changing anything | `npx --yes @polderlabs/bizar-omp setup --dry-run` | A report of the plugin and missing settings the installer would add |
+| Start one durable engineering session | `omb` | OMP inside a Bizar-owned tmux host, with reconnect support |
+| Switch between projects and sessions | `omb agents` | The full session hub and new-session picker |
+| Watch sessions in a browser | `omb dashboard --open` | A local, loopback-only dashboard with a single-use link |
+| Install only the OMP extension | `omp plugin install @polderlabs/bizar-omp` | Extension discovery without installing the `omb` and `bizar-omp` shell commands |
+
+The shortest useful path is:
+
+```sh
+npx --yes @polderlabs/bizar-omp setup
+omb
+```
+
+The setup command is safe to preview and safe to run again. It preserves credentials, provider choices, approval policies, explicit `false` or empty settings, and project overrides. It proposes only settings that are absent.
+
+## How Bizar fits into OMP
+
+<img src="docs/assets/bizar-omp-workflow.svg" alt="Bizar OMP workflow: plan, run, verify, integrate" width="100%" />
+
+Bizar adds the engineering contract around an OMP session:
+
+| You need | Bizar adds |
 | --- | --- |
-| A sensible process | Focused, bounded, and full workflow tiers selected from task scope and risk |
-| Background work | `omb` sessions inside tmux (psmux on Windows), with reconnect and a cross-project session hub |
-| Useful specialists | Native Bizar roles for orchestration, planning, research, implementation, review, security, verification, and documentation |
-| Stronger completion signals | Host-observed checks, fresh evidence, explicit acceptance, and serialized integration |
-| A readable operator experience | Native Advisor enabled by default, visible active agents, hidden tool trace, and readable chat output |
+| A proportionate process | Focused, bounded, and full workflow tiers selected from scope and risk |
+| Durable work | `omb` sessions in tmux, or psmux on Windows, with reconnect and a cross-project hub |
+| Specialist help | Native roles for planning, research, implementation, review, security, verification, architecture, and documentation |
+| A stronger finish line | Acceptance criteria, host-observed checks, fresh evidence, review decisions, and serialized integration admission |
+| A readable operator view | OMP's native Advisor, visible agents, session activity, a local dashboard, and inspectable projections |
+
+The ownership boundary is deliberate:
 
-Bizar does not start a second agent runtime, replace OMP's task system, or include a Claude Code, MCP, or background daemon compatibility layer.
+| OMP owns | Bizar owns |
+| --- | --- |
+| Models, providers, credentials, tools, task execution, session files, and conversation state | Workflow intent, acceptance, evidence freshness, candidate lineage, resource ownership, review policy, and integration admission |
+
+Bizar does not replace OMP's task system, add a parallel scheduler, or provide a Claude Code, MCP, or background-daemon compatibility layer.
 
 ## Install
 
-### Full installation
+### Requirements
+
+- Node.js 22 or newer
+- Bun 1.3.14 or newer
+- OMP 18.2.6 on `PATH`
+- OMP 18.2.5 and 18.2.4 remain regression-qualified
+- tmux on Linux and macOS, or [psmux](https://github.com/psmux/psmux) on Windows for durable sessions
+
+Check the host before installing:
+
+```sh
+node --version
+bun --version
+omp --version
+```
 
-The supported installation path configures the complete OMP experience in one command.
+### Full installation
 
-Requires Node.js 22 or newer, Bun 1.3.14 or newer, and OMP 18.2.6 on `PATH`. OMP 18.2.5 and 18.2.4 remain regression-qualified.
+This is the supported path for a complete Bizar OMP setup:
 
 ```sh
 npx --yes @polderlabs/bizar-omp setup
@@ -44,31 +89,50 @@ npx --yes @polderlabs/bizar-omp setup
 
 The installer:
 
-1. Installs the exact Bizar version globally, providing `omb` and `bizar-omp`.
-2. Registers and enables the package through `omp plugin install`.
+1. Installs the exact Bizar package version globally, providing `omb` and `bizar-omp`.
+2. Registers and enables that same version through OMP's plugin manager.
 3. Installs the extension, eight specialist agents, skills, rules, prompts, tools, and model roles.
 4. Makes the Bizar Orchestrator the default conversation and enables OMP's native Advisor.
-5. Proposes only absent compatibility settings for background tasks, visible agents, and readable output; existing values—including approval policies and explicit false/empty settings—are preserved.
-6. Writes a recoverable receipt for values it actually added and preserves credentials, provider choices, approval policies, and project overrides.
+5. Adds only absent compatibility settings for background work, visible agents, and readable output.
+6. Writes a recoverable receipt for settings it changed and reads the result back.
+
+For a reproducible install, pin the version:
+
+```sh
+npx --yes @polderlabs/bizar-omp@0.5.0 setup
+```
 
-Interactive terminals show a phase dashboard with detected versions, applied settings, the recovery receipt, and the next commands. Preview or script the same operation with:
+For a named OMP profile or a non-standard OMP binary:
+
+```sh
+npx --yes @polderlabs/bizar-omp setup --profile bizar
+npx --yes @polderlabs/bizar-omp setup --omp /path/to/omp
+```
+
+Preview or script the same operation:
 
 ```sh
 npx --yes @polderlabs/bizar-omp setup --dry-run
 npx --yes @polderlabs/bizar-omp setup --json
 ```
 
-### Start OMP
+The interactive installer shows detected versions, each phase, settings it will add, the recovery receipt, and the next commands. `--json` produces machine-readable output for shell automation.
+
+### Extension-only installation
+
+Use this when you already manage `omb` separately or only need the OMP extension:
 
 ```sh
-omp          # normal direct OMP session
-omb          # durable tmux-backed session
-omb agents   # session hub and new-session selector
+omp plugin install @polderlabs/bizar-omp
 ```
 
-`omp` remains untouched. `omb` is the explicit durable mode. Plain `omb` reconnects to the most recently active live session in the current directory, or creates that directory's default session when none exists.
+This does not install `omb` or `bizar-omp` on `PATH`. For checkout development, link the package instead:
 
-### Verify, repair, or remove
+```sh
+omp plugin link /path/to/bizaromp
+```
+
+### Check, repair, or remove
 
 ```sh
 bizar-omp install-doctor
@@ -76,173 +140,224 @@ omp plugin list
 omp plugin doctor
 ```
 
-For a profile-scoped installation:
+`install-doctor` reports the active plugin, receipt state, settings drift, and the policies Bizar left under OMP's control. Uninstall only the Bizar integration with:
 
 ```sh
-npx --yes @polderlabs/bizar-omp setup --profile bizar
-omp --profile bizar
-bizar-omp install-doctor --profile bizar
+bizar-omp uninstall
 ```
 
-Each profile has its own OMP login and model configuration. Remove Bizar's plugin configuration with `bizar-omp uninstall`. The command restores settings only when they still contain the values Bizar applied, preserving later edits. Remove the global shell commands separately if needed:
+Uninstall restores a setting only when it still contains the value Bizar applied. If you changed that value later, Bizar preserves your change. Remove the global shell commands separately when needed:
 
 ```sh
 npm uninstall --global @polderlabs/bizar-omp
 ```
 
-### Extension-only installation
+## Your first durable session
 
-Use the native plugin command only when you already manage the shell commands yourself or only need the OMP extension:
+### 1. Start OMP through `omb`
 
 ```sh
-omp plugin install @polderlabs/bizar-omp
+omb
+```
+
+`omb` starts OMP inside a Bizar-owned tmux session from the first process. Closing the terminal client detaches from the session; it does not stop the host or its background agents. Run `omb` again in the same directory to reconnect to the most recently active live session.
+
+Use a task-specific session when you want an explicit name:
+
+```sh
+omb new "Investigate the API timeout"
+omb --session api-retries
 ```
 
-This does not install `omb` or `bizar-omp` on `PATH`. For checkout development, use `omp plugin link /path/to/bizaromp`.
+`omp` remains the direct OMP command. Use it when you do not need durable tmux or psmux behavior.
 
-## How to work with Bizar
+### 2. Ask for work in the main conversation
 
-The main OMP conversation is the Bizar Orchestrator. It chooses the smallest method that fits the work:
+The main conversation is the Bizar Orchestrator. Give it the outcome and constraints in plain language. It selects the smallest workflow tier that fits the work:
 
-| Tier | Use it for | Typical proof |
+| Tier | Good fit | Typical proof |
 | --- | --- | --- |
-| Focused | A local bug fix, styling change, typo, or narrow documentation edit | Targeted check, diff review, or smoke test |
+| Focused | A typo, small documentation edit, or narrow local fix | Targeted check, diff review, or smoke test |
 | Bounded | A contained behavior change or small feature | Acceptance criteria and focused tests |
-| Full | Security, architecture, migrations, concurrency, unknown regressions, or cross-cutting work | Planning, isolation, fresh evidence, review, and serialized integration |
+| Full | Security, architecture, migrations, concurrency, or cross-cutting work | Planning, isolation, review, fresh evidence, and serialized integration |
+
+The tier can escalate when the scope or risk changes. A focused request still gets validation.
 
-The route can escalate when scope or risk changes. A focused task is still validated; it simply avoids ceremony that does not improve the result.
+### 3. Inspect the work
 
-### Useful commands inside OMP
+Inside OMP, these commands expose the workflow state and proof:
 
 ```text
-/bizar run <objective>   start a bounded workflow
-/bizar status            inspect the active workflow
-/bizar evidence          inspect current proof
-/bizar cancel            cancel the active workflow
-/bizar-models            map available OMP models to Bizar roles
-/bizar-models health     validate Bizar role selectors without changing them
-/bizar-dashboard         open the local OMB dashboard (open | stop)
+/bizar run <objective>       Start a bounded workflow
+/bizar status                 Show the active workflow state
+/bizar evidence               List recorded checks and evidence
+/bizar inspect                Explain blockers and evidence lineage
+/bizar recipe <objective>     Preview an inspectable recipe
+/bizar capabilities          Show native qualification boundaries
+/bizar cancel [reason]        Cancel the active workflow
 ```
 
-`/bizar-models` reads OMP's authenticated model catalog locally, assigns the best available selectors to Bizar roles, validates native resolution, and preserves unrelated roles. Locally hosted models (llama.cpp, Ollama, LM Studio, vLLM, ...) are preferred for the build, verify, and docs roles when one satisfies the role's capability floor; capable cloud models remain the fallback, and high-stakes roles keep capability-first ranking.
+The tools behind these commands keep completion tied to fresh, host-observed checks. A stale check, changed candidate, missing review, or unknown native capability remains a blocker instead of being silently treated as success.
 
-## Durable sessions and the agents hub
+Useful model and dashboard commands are also available:
 
-Use `omb` when a session must keep running after the terminal client closes. OMP runs inside a Bizar-owned tmux host from the first process. The client can detach without stopping the host or its background agents. For sessions that must survive even a machine-level client restart, and for browser access, use the background daemon and dashboard below.
+```text
+/bizar-models                 Map available OMP models to Bizar roles
+/bizar-models health          Validate configured role selectors
+/bizar-dashboard              Print a single-use local dashboard link
+/bizar-dashboard open         Open the dashboard in the default browser
+/bizar-dashboard stop         Stop the dashboard daemon
+```
+
+`/bizar-models` reads OMP's authenticated model catalog locally, preserves unrelated roles, and validates the selectors it writes. It does not promise a particular provider, model family, price, or quality level.
 
-On Windows the same flows run through [psmux](https://github.com/psmux/psmux), a native tmux-compatible multiplexer. Install it with `winget install psmux`. The `BIZAR_TMUX_BIN` override wins; otherwise Bizar uses `psmux` on Windows and `tmux` elsewhere, falling back to a direct OMP spawn when no multiplexer is installed.
+## The `omb agents` hub
+
+Open the session switcher from any project:
 
 ```sh
-omb new "Investigate the API timeout"
-omb --session api-retries
 omb agents
 ```
 
-The `omb agents` hub provides:
+The hub shows every Bizar-owned session across projects. It includes:
 
-- A workspace rail and grouped session list across projects.
-- A global registry of every Bizar session, including sessions running outside the directory where `omb agents` was opened.
-- Session attach, rename, delete, refresh, settings, help, and reconnect controls.
+- One full-width, workspace-grouped session list with a compact selected-session strip.
+- Attach, rename, delete, refresh, settings, help, and reconnect controls.
 - A new-session selector opened with `n`.
-- `Tab` focus for the workspace rail. Select a workspace with `Up`/`Down`, then press `Enter` to immediately launch a new session rooted in that workspace; use `n` for the full new-session menu.
-- Workspace separators in the session list so sessions from different projects are easy to scan.
-- Inline rename from the hub with `e`; the name is saved without leaving the TUI for a separate prompt.
-- Mouse support for clicking sessions and workspaces and scrolling either list. The hub enables terminal SGR mouse reporting only while it is open.
-- Fuzzy directory search with recursive subdirectory indexing, parent navigation, recent project shortcuts, path autocomplete, and direct absolute paths.
-- A configurable Project directory root in Settings; it becomes the default new-session root and its full subdirectory tree is indexed for quick dispatch from anywhere.
-- Optional initial task text and session naming without leaving the TUI.
-- Native OMP session titles with deterministic project/task fallbacks.
-- An optional native system-tray menu for opening the hub, creating a session, attaching a named session, stopping the daemon, or quitting the tray.
-
-Key controls are `Enter` attach, `Tab` focus workspaces, workspace `Enter` immediate new session, `n` full new-session menu, `e` rename, `d` delete, `s` settings, `r` refresh, `?` help, and `q` exit. Inside a session, `Ctrl-d` or `Ctrl-c` returns to the hub without sending EOF or interrupt input to OMP. Mouse interaction in the hub supports row clicks and scrolling; mouse scrolling for attached OMP sessions remains configurable in Settings.
-
-To configure fast project picking, open `s`, select `Project directory root`, press `Enter`, enter a path such as `~/projects`, and press `s` to save. The new-session selector keeps direct absolute paths and parent navigation, while also indexing the configured folder's recursive subdirectories.
-
-The tray is opt-in. In the hub Settings (`s`), enable `system tray icon`, or run `omb tray start`; use `omb tray status` and `omb tray stop` to inspect or disable it. The tray uses the native backend on supported Linux x64/arm64, macOS x64/arm64, and Windows x64/arm64 hosts. Unsupported desktop environments keep the daemon and terminal workflows available without failing.
+- Recursive search inside the configured Project directory root, parent navigation, recent paths, autocomplete, and direct absolute paths.
+- Optional task text and an explicit session name.
+- Privacy-safe activity summaries derived from the session journal. Prompts, thinking text, shell commands, tool output, credentials, and raw terminal history are not rendered.
+- Optional native tray controls for opening the hub, creating a session, attaching a named session, stopping the daemon, and quitting the tray.
 
-### Session state and live activity
+### Hub controls
 
-The hub reports every session in one of five states:
+| Key | Action |
+| --- | --- |
+| `Enter` | Attach to the selected live session |
+| `n` | Open the full new-session menu |
+| `e` | Rename the selected session inline |
+| `d` | Delete the selected Bizar session |
+| `s` | Open settings |
+| `r` | Refresh without moving selection or scroll |
+| `?` | Open help |
+| `q` | Exit the hub |
 
-| State | Marker | Color | Meaning |
-| --- | --- | --- | --- |
-| `working` | `●` | green | The session journal shows unfinished work. |
-| `waiting` | `◐` | amber | The agent finished its turn and is waiting for input. |
-| `connected` | `◉` | blue | A client is attached and no structured activity has been journaled yet. |
-| `disconnected` | `◌` | gray | The host is live and unattached, with no work in progress. |
-| `stopped` | `○` | dim gray | No host is observed and the journal went silent. |
+Mouse clicks select sessions and a second click opens a live one. Mouse scrolling moves through the session list while the hub is open. The hub enables terminal SGR mouse reporting only for its own lifetime. Mouse behavior inside an attached OMP session follows the session's OMP and multiplexer settings.
 
-Each state renders with its own marker and color. State follows the agent, not tmux attachment alone: detach the client while the agent is still processing and the session keeps reporting `working`. Liveness comes from the journal too: a session whose tmux host is gone but whose journal was written inside the freshness window is still reported as `working`, `waiting`, or `disconnected`, and only becomes `stopped` once that journal is silent.
+To configure project discovery, open `s`, select `Project directory root`, press `Enter`, enter a path such as `~/projects`, and save. Use `Show stopped sessions in this view` when you need to inspect sessions whose host is no longer running. Deleting a session also tombstones its native journal so a recent history entry cannot reappear as an unopenable session; deleting an already unhosted row removes that stale history entry.
 
-Every row, and the inspector for the selected session, shows a live activity line: the current phase with a short safe target, such as `Editing src/cli/agents.ts` or `Running tests`. Activity that stopped advancing is labeled `· stalled`, journal silence beyond the freshness window is labeled `· stale`, and a session with nothing journaled yet reads `No recent activity`. The inspector also reports the `IN STATE` duration of the current phase.
+### Session states
 
-Activity is derived from the structure of the session journal: entry types, roles, tool names, and file paths. Prompt text, thinking text, shell command text, tool output, environment values, and raw terminal history are never rendered. A session name is identity, not activity: the hub shows OMP's own title when there is one and otherwise a seven-word, single-line compaction of the first prompt, which is the same text OMP titles are derived from.
+| State | Meaning |
+| --- | --- |
+| `working` | The journal shows unfinished work. |
+| `waiting` | The agent finished its turn and is waiting for input. |
+| `connected` | A client is attached and no structured activity has been journaled yet. |
+| `disconnected` | The host is live and unattached, with no work in progress. |
+| `stopped` | No host is observed and the journal is silent. |
 
-Stopped sessions are listed only while `Show stopped sessions in this view` is enabled in hub Settings (`s`). Status refreshes every few seconds in place, without moving the selection or the scroll position.
+State follows journal activity and host liveness, not tmux attachment alone. A detached session can remain `working`. Activity that stops advancing is marked `stalled`; old journal data is marked `stale`.
 
-## Model roles and native assets
+### Optional tray
 
-Bizar registers visible `bizar_*` roles without replacing operator-owned mappings. The Orchestrator and Advisor are enabled by default; specialist definitions are available to OMP when the orchestrator delegates work. Installation also provides the `bizar-omp` orientation skill, workflow skills, native rules, prompts, tools, and the OMP-native development reference skill.
+Enable the tray from hub Settings or use:
 
-## Security boundaries
+```sh
+omb tray start
+omb tray status
+omb tray stop
+```
 
-- Bizar is trusted in-process extension code. OMP extensions and shell commands are not an OS sandbox.
-- API keys, tokens, `.env` contents, and private control links are never written to source, logs, commits, or evidence.
-- Credentials, providers, explicit tool policies, model selections, and project overrides remain owned by OMP.
-- Managed worker changes remain isolated and are retained for explicit parent integration. Bizar does not silently apply worker patches.
-- Install only in projects and environments you trust. Review changes with `setup --dry-run` and `bizar-omp install-doctor`.
+The native tray backend is available on supported Linux, macOS, and Windows hosts. Unsupported desktop environments keep the terminal hub and daemon available.
 
-## Background daemon and the OMB dashboard
+## Browser dashboard and daemon
 
-`omb daemon` owns long-running sessions independently of any terminal client. The daemon serves the local dashboard and keeps the on-disk session snapshot fresh, so a browser can show live state without an OMP session open.
+The daemon keeps a session snapshot fresh independently of a terminal client. The dashboard binds to loopback and uses a single-use access code that expires after five minutes.
 
 ```sh
-omb daemon start     # detached, loopback only
-omb daemon status    # state, pid, port, last scan, state counts, log path
+omb daemon start
+omb daemon status
 omb daemon restart
 omb daemon stop
 ```
 
-`omb dashboard` starts the daemon when needed and prints a single-use link:
+Open the dashboard:
 
 ```sh
-omb dashboard          # prints http://127.0.0.1:<port>/dash?oc=…
-omb dashboard --open   # also opens the default browser
-omb dashboard --json   # { url, port, pid, code } for scripts
-omb dashboard stop     # stops the daemon; tmux sessions keep running
+omb dashboard          # print the local URL
+omb dashboard --open   # print and open it in the default browser
+omb dashboard --json   # emit { url, port, pid, code }
+omb dashboard stop     # stop the daemon; tmux sessions keep running
 ```
 
-Inside an OMP session, `/bizar-dashboard` dispatches the same CLI and prints the link; `/bizar-dashboard open` launches a browser, and `/bizar-dashboard stop` stops the daemon.
+The dashboard is organized around the active session. Choose a workspace session, read its live tmux console, and send a message from the composer with **Ctrl Enter**. Console output refreshes automatically without pulling you back to the bottom when you scroll up. **Open terminal** remains available for full-screen OMP interaction.
+
+Create, rename, attach, and stop actions stay alongside the selected session. Dashboard settings edit the same project-root, auto-attach, mouse-forwarding, stopped-session, and tray preferences used by the terminal hub. Attach uses a terminal emulator from `PATH`; set `BIZAR_TERMINAL` to override detection. If no emulator is available, the dashboard returns the exact attach command.
+
+The dashboard does not fetch a remote frontend. It serves one self-contained page, binds to `127.0.0.1`, and keeps the exchanged token in browser session memory. The session-list payload excludes credentials, environment values, pane commands, process ids, prompts, and terminal history. Opening a session console makes a separate authenticated request for a bounded, control-sequence-stripped capture of that exact Bizar-owned tmux pane; composer input is length-limited and sent literally to that pane.
+
+## Native roles and assets
+
+Installation registers visible `bizar_*` roles without replacing operator-owned mappings. The default package includes:
+
+- Bizar Orchestrator and Advisor integration.
+- Specialist agents for architecture, planning, research, implementation, review, security, verification, and documentation.
+- The `bizar-omp` orientation and workflow skills.
+- Native rules, prompts, tools, evidence schemas, and the OMP-native development reference skill.
 
-The dashboard is a single self-contained page that needs no network access: it binds to `127.0.0.1` only, exchanges its one-time access code for the daemon token, keeps that token in session memory, and never renders environment variables, credentials, or terminal history. Sessions are grouped by workspace, and attach, create, rename, and stop are confirmed before they act. Stopping a session is scoped to Bizar-owned tmux sessions; a foreign or unknown session is refused.
+The role names are selectors, not guarantees of speed, cost, provider, or model quality. Inspect the resolved OMP catalog when those properties matter.
 
-Attach hands `tmux attach-session` to a terminal emulator it detects on `PATH` (`$BIZAR_TERMINAL` overrides the probe). When no emulator exists, the dashboard returns the exact command instead of failing silently.
+## Safety and ownership boundaries
+
+- Bizar is trusted in-process extension code. OMP extensions and shell commands are not an OS sandbox.
+- Credentials, API keys, `.env` contents, and private control links are excluded from logs, commits, and evidence bundles.
+- OMP keeps ownership of credentials, providers, model selections, approval policies, tool policies, and project overrides.
+- Managed worker changes stay isolated and require explicit parent integration. Bizar never silently applies worker patches.
+- Git worktree cleanup is preview-first, ownership-aware, and non-forced. Ignored or uncertain content blocks cleanup.
+- Install only in projects and environments you trust. Review `setup --dry-run` and `bizar-omp install-doctor` before making changes.
+
+### Qualification boundary
+
+The 0.5.0 release qualifies candidate-bound integration, journal v2 validation and recovery, acceptance inspection, bounded resources, evidence bundles, and the packed native OMP extension contract on the declared Node, Bun, Git, and OMP environments.
+
+The release does not claim OS sandboxing, provider model quality, universal native task or eval interception, automatic cleanup of an unqualified native isolation backend, or Claude Code/AO compatibility. See the [support matrix](docs/releases/support-matrix.md) for the current boundary.
 
 ## Compatibility
 
 | Component | Qualified baseline |
 | --- | --- |
 | OMP | 18.2.6, with 18.2.5 and 18.2.4 regression-qualified |
-| Node.js | 22.x and 24.x in CI |
+| Node.js | 22.x and 24.x |
 | Bun | 1.3.14 compatibility job |
 | Package | `@polderlabs/bizar-omp@0.5.0` |
 
 Upstream OMP changes require a new compatibility baseline and contract run. The package does not widen a version range to hide an unqualified runtime.
 
-## Development
+## Development and verification
 
 ```sh
-npm install
+npm ci
+npm run typecheck
+npm test
 make verify
 ```
 
-The verification gate runs typecheck, tests, package checks, generated documentation checks, and secret scanning. A native OMP qualification run is also available when the OMP source package is installed:
+`make verify` runs typecheck, tests, package verification, generated documentation checks, and secret scanning. Build the package directly with:
+
+```sh
+npm run build
+npm run verify:package
+npm run pack:check
+```
+
+The native OMP qualification needs the OMP source package. When it is available:
 
 ```sh
 npm run verify:omp
+npm run verify:omp:registry
 ```
 
-See [CONTRIBUTING.md](CONTRIBUTING.md) for branches, Conventional Commits, release tags, and trusted publishing. Release notes live in [`docs/releases/`](docs/releases/).
+Release notes and compatibility records live in [`docs/releases/`](docs/releases/). See [CONTRIBUTING.md](CONTRIBUTING.md) for branch conventions, release tags, and trusted publishing.
 
 ## License
 

package/dist/cli/agents-ink.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"agents-ink.d.ts","sourceRoot":"","sources":["../../src/cli/agents-ink.tsx"],"names":[],"mappings":"AAEA,OAAO,EAA0C,KAAK,cAAc,EAAwB,MAAM,wBAAwB,CAAC;AAE3H,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,wBAAwB,CAAC;AAI1D,MAAM,MAAM,eAAe,GACvB;IAAE,IAAI,EAAE,MAAM,CAAA;CAAE,GAChB;IAAE,IAAI,EAAE,QAAQ,CAAC;IAAC,OAAO,EAAE,cAAc,CAAA;CAAE,GAC3C;IAAE,IAAI,EAAE,KAAK,CAAC;IAAC,UAAU,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,MAAM,CAAC;IAAC,SAAS,EAAE,MAAM,CAAA;CAAE,GACpE;IAAE,IAAI,EAAE,QAAQ,CAAC;IAAC,OAAO,EAAE,cAAc,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,GAC3D;IAAE,IAAI,EAAE,QAAQ,CAAC;IAAC,OAAO,EAAE,cAAc,CAAC;IAAC,eAAe,CAAC,EAAE,MAAM,CAAA;CAAE,GACrE;IAAE,IAAI,EAAE,UAAU,CAAC;IAAC,QAAQ,EAAE,WAAW,CAAA;CAAE,CAAC;AAkyBhD,wBAAsB,eAAe,CAAC,GAAG,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,CAAC,UAAU,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE,QAAQ,EAAE,WAAW,EAAE,mBAAmB,CAAC,EAAE,MAAM,EAAE,cAAc,UAAQ,GAAG,OAAO,CAAC,eAAe,CAAC,CAO5M"}
+{"version":3,"file":"agents-ink.d.ts","sourceRoot":"","sources":["../../src/cli/agents-ink.tsx"],"names":[],"mappings":"AAEA,OAAO,EAA0C,KAAK,cAAc,EAAwB,MAAM,wBAAwB,CAAC;AAE3H,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,wBAAwB,CAAC;AAI1D,MAAM,MAAM,eAAe,GACvB;IAAE,IAAI,EAAE,MAAM,CAAA;CAAE,GAChB;IAAE,IAAI,EAAE,QAAQ,CAAC;IAAC,OAAO,EAAE,cAAc,CAAA;CAAE,GAC3C;IAAE,IAAI,EAAE,KAAK,CAAC;IAAC,UAAU,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,MAAM,CAAC;IAAC,SAAS,EAAE,MAAM,CAAA;CAAE,GACpE;IAAE,IAAI,EAAE,QAAQ,CAAC;IAAC,OAAO,EAAE,cAAc,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,GAC3D;IAAE,IAAI,EAAE,QAAQ,CAAC;IAAC,OAAO,EAAE,cAAc,CAAC;IAAC,eAAe,CAAC,EAAE,MAAM,CAAA;CAAE,GACrE;IAAE,IAAI,EAAE,UAAU,CAAC;IAAC,QAAQ,EAAE,WAAW,CAAA;CAAE,CAAC;AAgqBhD,wBAAsB,eAAe,CAAC,GAAG,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,CAAC,UAAU,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE,QAAQ,EAAE,WAAW,EAAE,mBAAmB,CAAC,EAAE,MAAM,EAAE,cAAc,UAAQ,GAAG,OAAO,CAAC,eAAe,CAAC,CAO5M"}