@polderlabs/bizar-omp 0.6.3 → 0.6.4

package/README.md

@@ -353,7 +353,7 @@ omb help stop       # one command's usage
 omb help --json     # { commands: [{ name, names, summary, usage }] }
 ```
 
-`omb --help` and `omb -h` are omb's own tokens and print omb's table; use `omp --help` for OMP's own help. Anything else `omb` does not recognise is passed through to OMP, so `omb --resume`, `omb --session`, and `omb "fix the failing test"` keep their OMP meaning.
+`omb --help` and `omb -h` are omb's own tokens and print omb's table; use `omp --help` for OMP's own help. `--session ADDRESS`, `--session-id ADDRESS`, and `--new` are omb's launcher options and are consumed before OMP sees them; anything else `omb` does not recognise is passed through to OMP, so `omb --resume` and `omb "fix the failing test"` keep their OMP meaning.
 
 ## Native roles and assets
 

package/docs/compatibility/baseline.json

@@ -25,7 +25,7 @@
   },
   "package": {
     "name": "@polderlabs/bizar-omp",
-    "version": "0.6.3",
+    "version": "0.6.4",
     "integrity": "computed by npm pack in CI",
     "extensionEntry": "dist/extension.js"
   }

package/docs/releases/0.6.3.md

@@ -6,7 +6,7 @@
 - Every `omb stop` row is reported as `stopped`, `skipped` with a reason, `planned` for a dry run, or `failed`, both in the human summary and in `--json`, and the exit code is nonzero only when a resource failed. `omb restart` rows also use `started` for a resource it stopped and started again. Stopping something that is not running stays a success.
 - `omb restart` stops the whole runtime and starts it again: the daemon, the tray only when hub settings enable it, and a fresh single-use dashboard link. It reports one row per resource — each session, the daemon, the tray, and the dashboard — refuses every `omb stop` target flag including `--idle` with exit code 2, and `--dry-run` reports that same one-row shape with action `planned`. `--json` always carries `url`: the new dashboard link, or `null` when none was minted.
 - `omb help` lists the commands and `omb help <command>` prints one command's own usage, and `--help` works on every command. Usage text now lives beside the command that owns it, so the help table cannot drift from the implementation.
-- The OMP pass-through contract is unchanged and now stated in the help itself: anything `omb` does not recognise is handed to OMP, so `omb --resume`, `omb --session`, and a bare prompt keep their meaning. `help`, `--help`, and `-h` are omb's own tokens: `omb --help` and `omb -h` print omb's table, and `omp --help` prints OMP's.
+- The OMP pass-through contract is unchanged and now stated in the help itself: `--session ADDRESS`, `--session-id ADDRESS`, and `--new` are omb's own launcher options, consumed before OMP sees them, while anything else `omb` does not recognise is handed to OMP, so `omb --resume` and a bare prompt keep their meaning. `help`, `--help`, and `-h` are omb's own tokens: `omb --help` and `omb -h` print omb's table, and `omp --help` prints OMP's.
 
 ## Safety
 

package/docs/releases/0.6.4.md

@@ -0,0 +1,25 @@
+# 0.6.4
+
+Documentation correction. No file under `src/` changed, so the built CLI behaves exactly as it did in 0.6.3.
+
+## What was wrong
+
+`README.md` said that "anything else `omb` does not recognise is passed through to OMP, so `omb --resume`, `omb --session`, and `omb "fix the failing test"` keep their OMP meaning". `--session ADDRESS`, `--session-id ADDRESS`, and `--new` are omb's own launcher options: `parseOmbInvocation` (`src/cli/omb-invocation.ts:26-32`) consumes them before OMP is started, so `omb --session api-retries` attaches that session instead of forwarding `--session`. The README's own "Your first durable session" section documents `omb --session api-retries` as an omb feature, so the pass-through sentence contradicted the page it lives on, and the 0.6.3 changelog entry and release note repeated the same wrong example. The defect was found by an independent audit of the shipped 0.6.3 claims: 32 claims checked, 31 hold, this one contradicted.
+
+## What changed
+
+- `README.md` — the pass-through sentence names `--session ADDRESS`, `--session-id ADDRESS`, and `--new` as omb's launcher options, consumed before OMP sees them, and keeps `omb --resume` and `omb "fix the failing test"` as the examples that really do reach OMP.
+- `CHANGELOG.md` and `docs/releases/0.6.3.md` — the same correction in the 0.6.3 entry, so the released notes no longer contradict the tool.
+- `tests/omb-runtime.test.ts` — the README drift guard read the shell blocks only, which is how a prose example naming an omb-owned flag could ship. It now also reads the pass-through sentence and proves each example there survives `parseOmbInvocation` unchanged. Restoring the old sentence makes it fail (1 failed, 37 skipped); the corrected text passes.
+- `package.json`, `package-lock.json`, and `docs/compatibility/baseline.json` — version 0.6.4.
+
+## Verification
+
+- `npm run typecheck` — clean.
+- `npm test` — 215 tests across 28 files pass, including the extended README guard.
+- `npm run verify:package` — `{"ok":true,"version":"0.6.4","checked":11}`.
+- `npm run verify:docs` — `{"ok":true,"docs":5,"inventoryCategories":8}`.
+- `npm run verify:security` — 271 tracked and non-ignored files scanned, no credential material detected.
+- `npm run pack:check` — 748 files, 439.5 kB packaged.
+- `bun scripts/verify-omp-install.mjs` with `BIZAR_OMP_PACKAGE_ROOT` at an OMP 18.2.6 scratch tree — `{"ok":true,"tools":8,"agents":8,"skills":8}`, and packed install, repeat install, native discovery/tools, profile isolation, and uninstall PASS.
+- `node scripts/verify-omp-plugin-install.mjs` against the published `@polderlabs/bizar-omp@0.6.4` — registry plugin install, native discovery, and doctor PASS.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polderlabs/bizar-omp",
-  "version": "0.6.3",
+  "version": "0.6.4",
   "description": "Native oh-my-pi engineering workflow extension with typed evidence and serialized integration.",
   "type": "module",
   "engines": {