@omercnet/paseo-omp 1.0.0-next.161.1 → 1.0.0-next.163.1

package/README.md

@@ -4,6 +4,10 @@ Community OMP integration for Paseo. The plugin registers the distinct `omp-plug
 
 > **Alpha preview:** persistence and protocol contracts are tested, but upgrades may still require re-importing sessions created by an earlier preview.
 
+## Demo
+
+https://github.com/user-attachments/assets/6d7eff94-cd63-43e1-83ad-642b1b8f75b4
+
 ## Screenshots
 
 Both PNGs come from the plugin's isolated Paseo development daemon at 2× pixel density. Browser
@@ -20,7 +24,7 @@ before capture.
 
 ## Quick start
 
-Requirements: Paseo `^0.9.2`, OMP `18.1.15` or newer, and OMP RPC protocol v2. Paseo 0.9.2 is required for reliable plugin-provider request failure containment, reload cleanup, and daemon shutdown ordering, in addition to the 0.9 client APIs used by the plugin.
+Requirements: Paseo `^0.9.2 || ^0.10.0-beta.1`, OMP `18.1.15` or newer, and OMP RPC protocol v2. Paseo 0.9.2 is required for reliable plugin-provider request failure containment, reload cleanup, and daemon shutdown ordering; 0.10.0-beta.1 is verified against the same public plugin contracts.
 
 ```bash
 paseo plugin install npm:@omercnet/paseo-omp@<version>
@@ -36,7 +40,7 @@ Open the **OMP** sidebar to review the provider-profile contract, choose which c
 - [Core-provider issue and parity audit](docs/core-provider-issue-audit.md)
 - [Alpha release checklist](docs/alpha-release-checklist.md)
 
-The plugin uses public Paseo 0.9 provider and client contracts and registers distinct `omp-plugin` and `omp-plugin-<profile>` identities; it does not modify the bundled `omp` provider.
+The plugin uses public Paseo 0.9 and 0.10 beta provider and client contracts and registers distinct `omp-plugin` and `omp-plugin-<profile>` identities; it does not modify the bundled `omp` provider.
 
 ## Named OMP profiles
 
@@ -50,7 +54,7 @@ Profile selection is request-local: concurrent clients cannot change each other'
 
 ## Paseo provider SDK coverage
 
-This matrix inventories the complete capability set exported by the pinned `@getpaseo/plugin` 0.9.2 provider SDK. It measures strict SDK surface coverage, not general product quality.
+This matrix inventories the complete capability set exported by the pinned `@getpaseo/plugin` 0.9.2 provider SDK. Paseo 0.10.0-beta.1 preserves that public provider surface; compatibility is checked nightly against both SDK channels. It measures strict SDK surface coverage, not general product quality.
 
 **Current capability completeness: 61.8%.** The provider advertises 11 of 17 capabilities (64.7%); ten are complete and `session.configure` is partial.
 
@@ -113,7 +117,7 @@ Existing agents whose provider is `omp` remain owned by the bundled provider. Ne
 
 OMP `18.1.15` is the oldest version tested end to end. The direct provider's hard compatibility gate is `rpc-ui` protocol v2: metadata-free legacy ready frames and v1-only runtimes are rejected before a provider session opens because they cannot support the advertised persistence and conversation-rewind capabilities. Typed tool approvals remain capability-gated and fall back as described above. For terminal completion, a matching `agent_end.requestId` is authoritative and mismatches are ignored before state changes. Released OMP 18.2.x builds that omit that field use an ordered fallback requiring a fresh correlated native user entry followed by current-turn assistant activity, an idle non-compacting runtime, and no conflicting permission, tool, steer, or child-session work. Ambiguous events while OMP is active are ignored; unresolved ambiguity after confirmed idle fails only the Paseo turn. This trades a bounded residual same-agent stale-event risk for compatibility with released OMP instead of terminating and lazily restarting the runtime after every later prompt. Paseo clients, including mobile clients inside reconnect grace, do not own or terminate the daemon-managed OMP session.
 
-Paseo 0.9.2 is the minimum supported release. The controlled Docker canary uses the pinned official 0.9.2 image; its compatibility matrix covers OMP 18.1.15 and 18.2.0. The canary preserves nested provider-subagent ancestry and spawning-tool links, and validates npm-managed plugin sources, platform-owned external URL opening, and whole-item timeline transforms before Overview grouping.
+Paseo 0.9.2 is the minimum supported stable release, and 0.10.0-beta.1 is supported as a prerelease. The controlled Docker canary remains pinned to official 0.9.2; nightly SDK checks cover both 0.9 latest and the 0.10 beta. The canary preserves nested provider-subagent ancestry and spawning-tool links, and validates npm-managed plugin sources, platform-owned external URL opening, and whole-item timeline transforms before Overview grouping.
 
 Install, update, disable, or remove `paseo-omp` independently of the bundled provider. Verify the provider snapshot contains `omp-plugin` after installation; a bundled `omp` entry may remain present and is not modified by this plugin.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@omercnet/paseo-omp",
-  "version": "1.0.0-next.161.1",
+  "version": "1.0.0-next.163.1",
   "type": "module",
   "description": "Paseo integration for OMP, including its direct provider and workspace tooling.",
   "license": "MIT",

package/paseo-plugin.json

@@ -1,6 +1,6 @@
 {
   "id": "paseo-omp",
   "description": "Paseo integration for OMP, including its direct provider and workspace tooling.",
-  "requirements": { "paseo": "^0.9.2" },
+  "requirements": { "paseo": "^0.9.2 || ^0.10.0-beta.1" },
   "build": [["node", "scripts/prepare-dependencies.mjs"]]
 }

package/server/package-version.ts

@@ -1,2 +1,2 @@
 /** Release Please keeps this bundle-safe constant aligned with package.json. */
-export const PASEO_OMP_PACKAGE_VERSION = "1.0.0-next.161.1"; // x-release-please-version
+export const PASEO_OMP_PACKAGE_VERSION = "1.0.0-next.163.1"; // x-release-please-version