plugnz 0.0.17 → 0.0.19

package/README.md

@@ -3,6 +3,7 @@
 Open-source installer **and doctor** for agent plugins (Agent Plugins / OpenPlugin spec 1.0.0) and MCP configs — Claude Code, Codex, Cursor, Kimi, and more.
 
 ```
+npx plugnz install                        # current directory; compiles portable hooks
 npx plugnz add <plugin-dir-or-marketplace-or-git-url>  # native plugin stores
 npx plugnz doctor                          # dead commands, shadowed entries, stale installs
 npx plugnz pin                             # absolute command paths for GUI hosts
@@ -18,11 +19,11 @@ re-`add` from the source recorded in `state.json`, plus the pins that install
 carried. Both refuse rather than guess, and neither will touch a plugin this
 tool did not install. Details: `docs/pin-and-update.md`.
 
-**Portable context hooks:** `plugnz hooks build <plugin-dir> --target <host> --out <dir>` compiles session-start, stop, and pre/post-tool handlers for Claude Code, Codex, OMP, Pi v1, OpenCode, and ZCode. Handlers receive normalized JSON and return context; native adapters expose their delivery and continuation limits through `plugnz hooks targets`. See [the contract, usage, and native map](docs/hooks.md).
+**Portable context hooks:** run `npx plugnz install` inside a package containing `plugnz.hooks.json`, or `npx plugnz install <source>`. Installation compiles and registers session-start, stop, and pre/post-tool handlers through each supported harness's native loader. Handlers receive normalized JSON and return context; `plugnz hooks targets` exposes delivery and continuation limits. See [the contract, usage, and native map](docs/hooks.md) and [real-model Docker verification](docs/hooks-live-verification.md).
 
 Why another tool: `npx plugins` is closed-source and its Cursor target does not install into Cursor; nothing in the ecosystem checks that an installed plugin still *works*. See `docs/research/`.
 
-The published CLI runs under Node.js 22 or newer; `npx` needs npm, not Bun. `bunx` also works. Bun is used for development and building. `add` accepts a local plugin or marketplace directory as well as a Git URL. Native plugin targets currently include Claude Code, Codex, Kimi, Cursor, OMP, Hermes, Grok, DCode, and ZCode CLI. Run `plugnz targets --all` to see supported and unsupported capabilities for each host; standalone skill distribution is outside this CLI's scope.
+The published CLI runs under Node.js 22 or newer; `npx` needs npm, not Bun. `bunx` also works. Bun is used for development and building. `add` accepts a local plugin or marketplace directory as well as a Git URL. Native plugin targets currently include Claude Code, Codex, Kimi, Cursor, OMP, Hermes, Grok, DCode, and ZCode CLI. Portable hook packages also have native Pi extension and OpenCode plugin routes for install, update, and remove. Run `plugnz targets --all` to see supported and unsupported capabilities for each host; standalone skill distribution is outside this CLI's scope.
 
 `sync` tracks each Source and its complete Desired plugin set per host. It retires
 owned plugins omitted from that set while retaining plugin data, inactive metadata
@@ -30,7 +31,7 @@ and lifecycle history. A missing or invalid Source is an error, never permission
 to prune. Use an explicit `retire-source` manifest entry when the Source itself
 is gone. See [the batch manifest](docs/sync-manifest.md).
 
-General sync/update/retirement is supported. Interrupted legacy installs needing
+General sync/update/retirement is supported for the established native plugin routes. The Pi and OpenCode portable-hook routes support install, update, and remove; `sync` is unsupported for those routes. Interrupted legacy installs needing
 the unfinished fenced adoption transaction are refused loudly without writes;
 successful legacy migration and stronger cross-process exclusion are follow-up
 refinements, not delivered guarantees.