@omercnet/paseo-omp 0.2.1-next.89.1 → 0.2.1-next.90.1

package/README.md

@@ -6,7 +6,7 @@ Community OMP integration for Paseo. The plugin registers the distinct `omp-plug
 
 ## Quick start
 
-Requirements: Paseo `^0.8.0`, OMP `18.1.15` or newer, and OMP RPC protocol v2.
+Requirements: Paseo `>=0.8.0 <0.10.0`, OMP `18.1.15` or newer, and OMP RPC protocol v2. Paseo `0.9.0-beta.1` is recommended for npm-managed installation and the complete client integration.
 
 ```bash
 paseo plugin install npm:@omercnet/paseo-omp@<version>
@@ -22,7 +22,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 only public Paseo 0.8 provider 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.8 and 0.9 beta provider contracts and registers distinct `omp-plugin` and `omp-plugin-<profile>` identities; it does not modify the bundled `omp` provider.
 
 ## Named OMP profiles
 
@@ -36,7 +36,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.8.0 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.0-beta.1 provider SDK. 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.
 
@@ -99,6 +99,8 @@ 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.0-beta.1 is the canary target and provides npm-managed plugin sources, platform-owned external URL opening, and whole-item timeline transforms before Overview grouping. Paseo 0.8.x remains supported for provider operation and Git or directory installation; its clients do not provide the external URL opener and retain their older timeline presentation semantics.
+
 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.
 
 ## Output and credential boundary

package/SUPPORT.md

@@ -16,7 +16,7 @@ Do not put credentials, private repository paths, session transcripts, or unreda
 
 ## Supported versions
 
-- Paseo: `^0.8.0` on both the daemon and every app loading the client entry.
+- Paseo: `>=0.8.0 <0.10.0` on both the daemon and every app loading the client entry. The pinned SDK and controlled canary use `0.9.0-beta.1`; 0.8.x remains the compatibility line.
 - OMP: `18.1.15` is the oldest release in the required real-binary regression job. The hard runtime contract is `rpc-ui` protocol v2, not the version string alone.
 - Plugin release channel: alpha. Backward compatibility is best effort until stable `0.1.0`; every known migration requirement must be stated in the release notes.
 - Typed approvals: optional. When both peers negotiate `typedToolApprovals: 1`, the plugin uses typed tool permissions. Otherwise it retains the bounded generic extension-question flow.
@@ -33,6 +33,7 @@ Do not put credentials, private repository paths, session transcripts, or unreda
 - The deterministic mock does not implement OMP's compaction-summary contract, so `/compact` reports `OMP compaction failed` in the canary; compaction remains covered by protocol fixtures.
 - `/handoff` reports `OMP command failed` in the controlled canary even with deterministic role models configured; treat handoff as unavailable there until its native prerequisite is isolated.
 - On official Paseo 0.8.0, requesting a live approval-mode change that the plugin rejects can trigger the daemon's unhandled-rejection restart path. Create a new `full`, `write`, or `ask` session instead of changing mode in place.
+- Paseo 0.8 clients do not expose the platform-owned plugin URL opener and transform timeline items after Overview grouping. Use a 0.9.0-beta.1 app for external documentation/device-authorization actions and for reliable image-card transformation of every source tool call.
 - Native Fast mode and a first-class plan mode are not exposed. `/handoff` is implemented but is not reproducible in the controlled canary without its native OMP workflow prerequisites.
 - Terminal-started OMP sessions are discoverable and importable but are not registered automatically through a terminal hook.
 - Paseo clients do not own OMP sessions. Mobile or desktop disconnects remain subject to Paseo's reconnect grace while the daemon-owned provider and OMP child continue independently; reconnecting can reveal an existing turn but does not transfer or sever runtime ownership.

package/TESTING.md

@@ -1,6 +1,6 @@
 # OMP provider parity audit
 
-Validated against the Paseo plugin SDK versions pinned in `package.json`, official Paseo Docker image `0.8.0@sha256:5518da7cdd35f132e8a944c35e509c677a90a8f3ec8a78df98f7fb5fd5e2c6c3`, and the real OMP compatibility matrix: high-use historical releases 17.2.15, 17.3.4, 18.0.11, and 18.1.10; minimum supported release 18.1.15; latest published 18.1 patch 18.1.22; and current release 18.2.0.
+Validated against the Paseo plugin SDK versions pinned in `package.json` and the real OMP compatibility matrix: high-use historical releases 17.2.15, 17.3.4, 18.0.11, and 18.1.10; minimum supported release 18.1.15; latest published 18.1 patch 18.1.22; and current release 18.2.0. Validation against official Paseo Docker image `0.9.0-beta.1@sha256:f75a0eb3547ad3cc6bbdeaa7277d2d50eb4d06a9dd669d480371d7adf1c911b5` is partial as recorded below.
 
 Classifications:
 
@@ -105,7 +105,7 @@ Set `PASEO_CANARY_OMP_VERSION` to exercise another pinned release. The local run
 
 The Linux real-OMP CI matrix downloads checksummed `omp-linux-x64` assets for OMP 17.2.15, 17.3.4, 18.0.11, 18.1.10, 18.1.15, 18.1.22, and 18.2.0, verifies each binary's pinned GitHub release SHA-256, and runs `PASEO_OMP_REAL_E2E=1 PASEO_OMP_VERSION=<version> npm test -- tests/provider.real.e2e.test.ts`. The historical entries are the four pre-floor releases with more than 4,000 downloads shown by npm for the seven days ending 2026-09-15; they are compatibility regression probes, not a support commitment. The remaining entries cover the supported floor, newest patch in that minor line, and current release. The test uses the real OMP binary and a local deterministic OpenAI-compatible model endpoint, including three sequential prompts on one native session, a Bash tool, and oversized-image transport.
 
-The controlled canary in `canary/compose.yml` builds this plugin into that official Paseo image and installs checksummed OMP binaries for `amd64` and `arm64`. `canary/smoke.ts` passed catalog/mode discovery, text and image prompts, Bash, a configured stdio MCP tool, permission allow/deny/cancel, steering, interruption, session listing/import/resume, subagents, conversation rewind followed by another turn, Hub process visibility, usage, and every plugin RPC. Browser verification loaded the global OMP health/configuration surface and the agent-scoped Hub, Memory, and Sessions controls. The default mock returned `CANARY_MOCK_OK`, `CANARY_TOOL_OK`, and `CANARY_MCP_OK`; the optional Ollama profile pulled `qwen2.5:0.5b` and completed turns without paid credentials. The harness records the canary-only `/compact` and `/handoff` failures instead of masking them.
+The controlled canary in `canary/compose.yml` successfully built the plugin into that official Paseo image, started the daemon, loaded `paseo-omp`, and completed runtime health, catalog/mode discovery, initial text, model switching, `autocompact`, `follow-up`, and the documented compact/handoff error collection. It then failed on the first Bash scenario because the later turn ended without request-correlated terminal ownership: `OMP terminal ownership could not be confirmed`. The subsequent image, MCP, permission, steering, interruption, persistence, subagent, Hub, usage, rewind, browser, and optional Ollama scenarios were not reached and remain unverified on Paseo 0.9.0-beta.1.
 
 ## OMP RPC compatibility intake
 
@@ -142,9 +142,9 @@ The go/no-go criteria, manual acceptance boundary, and alpha limitation list are
 - `npm test -- tests/provider-conformance.test.ts`: host-boundary conformance coverage includes `prompt.command`, `session.configure`, typed and fallback permission allow/deny/cancel paths, registry-driven reload/removal, verified stubborn-descendant cleanup, and sequential turns plus interrupt races with post-turn barriers.
 - `PASEO_OMP_REAL_E2E=1 PASEO_OMP_VERSION=<version> npm test -- tests/provider.real.e2e.test.ts`: the installed matrix version's catalog and hermetic real-binary text/Bash and oversized-image scenarios run against a local deterministic model.
 - `npm run test:coverage`: Vitest enforces aggregate 85% function and 89% line coverage over loaded source modules. Generated `dist/**` trees are excluded.
-- `npm run test:integration:install`: a packed npm package retains required production dependencies and bundles successfully; a fresh Git-style checkout installs with lifecycle scripts disabled, typechecks, and loads the server contribution.
+- `npm run test:integration:install`: npm package acquisition retains required production dependencies, and a fresh Git-style checkout runs frozen production-only preparation with lifecycle scripts disabled. Both installed trees resolve runtime dependencies, compile the client and server entries with Paseo's host compiler, and load the server contribution.
 - `npm run test:integration:docker`: verifies the host/container ownership boundary.
 - `npm run test:integration:wsl`: locally skips when `wsl.exe` is unavailable; Windows CI sets `PASEO_OMP_REQUIRE_WSL=1`, so this boundary remains required there.
-- `docker compose -f canary/compose.yml`: official Paseo 0.8.0, deterministic mock, Tailscale-bound web UI, and optional Ollama `qwen2.5:0.5b` passed end-to-end.
+- `docker compose -f canary/compose.yml`: official Paseo 0.9.0-beta.1 image build, daemon startup, plugin load, and early deterministic scenarios passed; the smoke stopped at the first later-turn Bash scenario with `OMP terminal ownership could not be confirmed`, so the remaining scenarios are unverified.
 - `zizmor .github/workflows`: no findings (offline audit; six repository-wide suppressions remain).
 - Release Please 17.1.2 `config.json` and `manifest.json` schema validation: passed for `release-please-config.json` and `.release-please-manifest.json`.

package/client/external-url.ts

@@ -0,0 +1,15 @@
+import * as paseoClient from "@getpaseo/plugin/client";
+import { Linking } from "react-native";
+import { selectExternalUrlOpener, validatedHttpUrl } from "../shared/external-url";
+
+const paseoOpenExternalUrl =
+  "openExternalUrl" in paseoClient && typeof paseoClient.openExternalUrl === "function"
+    ? paseoClient.openExternalUrl
+    : undefined;
+const openExternalUrl = selectExternalUrlOpener(paseoOpenExternalUrl, (url) =>
+  Linking.openURL(url),
+);
+
+export function openOmpExternalUrl(url: string): Promise<void> {
+  return openExternalUrl(validatedHttpUrl(url));
+}

package/client/mcp-authorization.tsx

@@ -1,11 +1,12 @@
 import { type PluginTimelineItemProps, useRpc } from "@getpaseo/plugin/client";
 import { Icon } from "@getpaseo/plugin/client/react-native";
 import { useMemo, useState } from "react";
-import { Linking, Pressable, Text, View } from "react-native";
+import { Pressable, Text, View } from "react-native";
 import {
   type OmpMcpAuthorizationTimeline,
   openOmpMcpAuthorizationInPaseoBrowser,
 } from "../shared/mcp";
+import { openOmpExternalUrl } from "./external-url";
 
 function browserAuthorizationError(error: unknown): string {
   const detail = error instanceof Error ? error.message : String(error);
@@ -98,7 +99,7 @@ export function OmpMcpAuthorizationCard({
     setError(null);
     setMessage(null);
     try {
-      await Linking.openURL(item.data.url);
+      await openOmpExternalUrl(item.data.url);
     } catch {
       setError("Could not open the authorization URL. Copy the URL below into a browser.");
     } finally {

package/client/omp-config-surface.tsx

@@ -10,7 +10,7 @@ import { useIsMutating, useMutation, useQuery, useQueryClient } from "@tanstack/
 import type { ReactNode } from "react";
 import { useCallback, useMemo, useState } from "react";
 import type { TextStyle, ViewStyle } from "react-native";
-import { Linking, Pressable, ScrollView, Switch, Text, View } from "react-native";
+import { Pressable, ScrollView, Switch, Text, View } from "react-native";
 import type { ComposerPillSettings } from "../shared/composer-pill-settings";
 import { listOmpConfig, type OmpConfig } from "../shared/omp-config";
 import {
@@ -26,6 +26,7 @@ import {
 import { type OmpStore, storeLabel } from "../shared/omp-store";
 import { getOmpProviderHealth, type OmpProviderHealth } from "../shared/provider-diagnostics";
 import { ComposerPillSettingsSection } from "./composer-pill-settings";
+import { openOmpExternalUrl } from "./external-url";
 import {
   documentationForSettingCategory,
   documentationForSettingPath,
@@ -1072,7 +1073,7 @@ function OmpConfigContent({
   const openDocumentation = useCallback(async (link: OmpDocumentationLink) => {
     setDocumentationError(null);
     try {
-      await Linking.openURL(link.url);
+      await openOmpExternalUrl(link.url);
     } catch {
       setDocumentationError(`Could not open ${link.label.toLocaleLowerCase()}.`);
     }

package/client/paseo-types.ts

@@ -0,0 +1,9 @@
+import type { PluginClientContext } from "@getpaseo/plugin/client";
+
+type AsyncResult<Callable> = Callable extends (...args: never[]) => Promise<infer Result>
+  ? Result
+  : never;
+
+export type PaseoApi = PluginClientContext["paseo"];
+export type PaseoAgentListResult = AsyncResult<PaseoApi["agents"]["list"]>;
+export type PaseoProviderSnapshotResult = AsyncResult<PaseoApi["providers"]["snapshot"]>;

package/client/provider-diagnostics-state.ts

@@ -1,4 +1,3 @@
-import type { PaseoApi, PaseoProviderSnapshotResult } from "@getpaseo/client";
 import type {
   OmpLspDiagnostics,
   OmpMcpDiagnostics,
@@ -8,8 +7,8 @@ import type {
   OmpVersionStatus,
   PathState,
 } from "../shared/provider-diagnostics";
-
 import { isOmpProvider } from "./omp-store-state";
+import type { PaseoApi, PaseoProviderSnapshotResult } from "./paseo-types";
 
 export type ProviderHealthTone = "ok" | "warning" | "danger" | "muted";
 export const OMP_PROVIDER_IDS = ["omp", "omp-plugin"] as const;

package/docs/alpha-release-checklist.md

@@ -7,7 +7,7 @@ This checklist prepares `paseo-omp-v0.1.0-alpha.1`. It does not authorize public
 - [ ] Release Please proposes `0.1.0-alpha.1` from manifest version `0.0.0`.
 - [ ] Package and tag names are `@omercnet/paseo-omp` and `paseo-omp-v0.1.0-alpha.1`.
 - [ ] Provider identity remains `omp-plugin`; bundled `omp` remains independent and enabled or disabled by the user.
-- [ ] Paseo requirement remains an official released range, currently `^0.8.0`.
+- [ ] Paseo requirement remains the reviewed dual-version range, currently `>=0.8.0 <0.10.0`.
 - [ ] Minimum tested OMP version, checksum, CI job, README, SUPPORT, and TESTING agree.
 
 ## Required gates

package/docs/installation.md

@@ -4,29 +4,53 @@ Paseo plugins are trusted, unsandboxed code. Review this plugin and its producti
 
 ## Requirements
 
-- Paseo daemon and apps: `^0.8.0`
+- Paseo daemon and apps: `>=0.8.0 <0.10.0`; `0.9.0-beta.1` is recommended
 - OMP: `18.1.15` or newer is the supported floor
 - OMP RPC: protocol v2 must negotiate successfully
 
 The first public build is an alpha. Alpha releases are compatibility previews and may require deleting and re-importing agents created by an earlier preview.
 
-## Install a release
+## Install or update from npm on Paseo 0.9
 
-Install an exact published version from npm:
+Paseo 0.9.0-beta.1 can acquire the published package and its production dependencies directly from npm on the daemon host:
 
 ```bash
 paseo plugin install npm:@omercnet/paseo-omp@<version>
 paseo plugin ls paseo-omp
 ```
 
-Alternatively, install the matching reviewed Git tag:
+Check for the registry's current `latest` version and approve the proposed update, or select an exact version explicitly:
+
+```bash
+paseo plugin update paseo-omp
+paseo plugin update paseo-omp --version <new-version>
+```
+
+The daemon uses its own npm registry and authentication configuration. npm acquisition installs the artifact's production dependencies before preparation; because npm artifacts omit `package-lock.json`, the preparation helper leaves that tree unchanged. A Git checkout with the committed lockfile runs frozen `npm ci --omit=dev --ignore-scripts`. A failed download, preparation, compatibility check, or activation keeps the installed revision active. Paseo 0.8 does not support npm plugin sources; use a Git tag or local directory instead.
+
+## Install a Git release on Paseo 0.8 or 0.9
+
+Install the matching reviewed Git tag:
 
 ```bash
 paseo plugin add omercnet/paseo-plugins:paseo-omp --ref paseo-omp-v<version>
 paseo plugin ls paseo-omp
 ```
 
-A Git tag-pinned installation does not advance through `paseo plugin update`. To upgrade, record the current installation, then replace it with the new tag in one maintenance window:
+### Update a Git installation on Paseo 0.9
+
+An ordinary update reviews the remote repository's current default HEAD. To move directly to another reviewed tag or commit, select it explicitly:
+
+```bash
+paseo plugin update paseo-omp
+paseo plugin update paseo-omp --ref paseo-omp-v<new-version>
+```
+
+The install-time `--ref` does not constrain later updates. Paseo 0.9 stages and validates the selected revision before replacing the active installation, so plugin settings remain intact and a failed update leaves the previous revision running.
+
+### Update a tag-pinned Git installation on Paseo 0.8
+
+Paseo 0.8 does not provide the 0.9 non-destructive explicit-ref update flow. Record the current installation, then replace it with the new tag in one maintenance window:
 
 ```bash
 paseo plugin ls paseo-omp --json > paseo-omp-before-update.json
@@ -56,12 +80,10 @@ paseo plugin ls paseo-omp
 
 ## Track a branch
 
-Tracking `main` executes future dependency and plugin updates with the daemon user's privileges. Record the installed commit before each update:
+Tracking `main` executes future dependency and plugin updates with the daemon user's privileges:
 
 ```bash
 paseo plugin add omercnet/paseo-plugins:paseo-omp --ref main
-paseo plugin ls paseo-omp --json > paseo-omp-before-update.json
-paseo plugin update paseo-omp
 ```
 
-A failed Git build or incompatible update leaves the previous revision active. Remove and re-add the recorded commit to roll back.
+On Paseo 0.9, preview and approve the remote default HEAD with `paseo plugin update paseo-omp`, or select `main` explicitly with `paseo plugin update paseo-omp --ref main`. On Paseo 0.8, record the installed commit before its existing branch-update workflow. A failed build or compatibility check leaves the previous revision active.

package/index.client.tsx

@@ -1,4 +1,3 @@
-import type { PaseoAgentListResult, PaseoApi } from "@getpaseo/client";
 import { settingsRpc } from "@getpaseo/plugin";
 import type {
   PluginButtonRegistration,
@@ -19,6 +18,7 @@ import {
   isOmpProvider,
   ompStoreKey,
 } from "./client/omp-store-state";
+import type { PaseoAgentListResult, PaseoApi } from "./client/paseo-types";
 import { quotaProviderIcon } from "./client/provider-icon";
 import { OmpImageTimeline } from "./client/provider-image";
 import { QuotaPopover } from "./client/quota-popover";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@omercnet/paseo-omp",
-  "version": "0.2.1-next.89.1",
+  "version": "0.2.1-next.90.1",
   "type": "module",
   "description": "Paseo integration for OMP, including its direct provider and workspace tooling.",
   "license": "MIT",
@@ -57,20 +57,19 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
+    "@getpaseo/protocol": "0.9.0-beta.1",
     "@modelcontextprotocol/sdk": "1.29.0",
     "yaml": "^2.9.0"
   },
   "devDependencies": {
     "@biomejs/biome": "^2.5.10",
-    "@getpaseo/cli": "0.8.0",
-    "@getpaseo/client": "0.8.0",
-    "@getpaseo/plugin": "0.8.0",
-    "@getpaseo/protocol": "0.8.0",
+    "@getpaseo/cli": "0.9.0-beta.1",
+    "@getpaseo/client": "0.9.0-beta.1",
+    "@getpaseo/plugin": "0.9.0-beta.1",
     "@tanstack/react-query": "^5.102.3",
     "@types/node": "^24.10.1",
     "@types/react": "^19.2.18",
     "@vitest/coverage-v8": "^5.0.0",
-    "esbuild": "^0.28.0",
     "react": "19.1.0",
     "react-native": "0.81.5",
     "tsx": "^4.20.6",

package/paseo-plugin.json

@@ -1,5 +1,5 @@
 {
   "id": "paseo-omp",
-  "requirements": { "paseo": "^0.8.0" },
+  "requirements": { "paseo": ">=0.8.0 <0.10.0" },
   "build": [["node", "scripts/prepare-dependencies.mjs"]]
 }

package/scripts/prepare-dependencies.mjs

@@ -8,10 +8,14 @@ const projectRoot = dirname(dirname(fileURLToPath(import.meta.url)));
 export function prepareDependencies(root = projectRoot, execute = execFileSync) {
   if (!existsSync(join(root, "package-lock.json"))) return false;
 
-  execute(process.platform === "win32" ? "npm.cmd" : "npm", ["ci", "--ignore-scripts"], {
-    cwd: root,
-    stdio: "inherit",
-  });
+  execute(
+    process.platform === "win32" ? "npm.cmd" : "npm",
+    ["ci", "--omit=dev", "--ignore-scripts"],
+    {
+      cwd: root,
+      stdio: "inherit",
+    },
+  );
   return true;
 }
 

package/shared/external-url.ts

@@ -0,0 +1,21 @@
+export type ExternalUrlOpener = (url: string) => Promise<void>;
+
+export function selectExternalUrlOpener(
+  paseoOpener: ExternalUrlOpener | undefined,
+  fallback: ExternalUrlOpener,
+): ExternalUrlOpener {
+  return paseoOpener ?? fallback;
+}
+
+export function validatedHttpUrl(value: string): string {
+  let url: URL;
+  try {
+    url = new URL(value);
+  } catch {
+    throw new Error("Only absolute HTTP(S) URLs are supported.");
+  }
+  if (url.protocol !== "http:" && url.protocol !== "https:") {
+    throw new Error("Only absolute HTTP(S) URLs are supported.");
+  }
+  return url.href;
+}