docs(paseo-omp): document stable release channel

paseo-omp/README.md

@@ -2,7 +2,7 @@
 
 Community OMP integration for Paseo. The plugin registers the distinct `omp-plugin` provider plus named profile providers and coexists with Paseo's bundled `omp` provider.
 
-> **Alpha preview:** persistence and protocol contracts are tested, but upgrades may still require re-importing sessions created by an earlier preview.
+> **Stable:** see [Support](SUPPORT.md) for supported versions and known limitations, and review release notes for any migration requirements before upgrading.
 
 ## Demo
 
@@ -38,7 +38,7 @@ Open the **OMP** sidebar to review the provider-profile contract, choose which c
 - [Compatibility, limitations, and support](SUPPORT.md)
 - [Test matrix and release verification](TESTING.md)
 - [Core-provider issue and parity audit](docs/core-provider-issue-audit.md)
-- [Alpha release checklist](docs/alpha-release-checklist.md)
+- [Release checklist](docs/release-checklist.md)
 
 The plugin uses public Paseo 0.9 and 0.10 provider and client contracts and registers distinct `omp-plugin` and `omp-plugin-<profile>` identities; it does not modify the bundled `omp` provider.
 

paseo-omp/SUPPORT.md

@@ -18,7 +18,7 @@ Do not put credentials, private repository paths, session transcripts, or unreda
 
 - Paseo: `^0.9.2 || ^0.10.0 || ^0.11.0` on both the daemon and every app loading the client entry. The 0.9.2 floor includes the plugin-provider request, reload-cleanup, and daemon-shutdown fixes required for reliable OMP provider operation; 0.10.1 is verified against the public plugin contracts.
 - OMP: `18.1.15` is the oldest supported release. The required full Docker canary passes with 18.1.15 and 18.2.0; the hard runtime contract remains `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.
+- Plugin release channel: stable. Every known migration requirement must be stated in the release notes; review them before upgrading.
 - Typed approvals: optional. When both peers negotiate `typedToolApprovals: 1`, the plugin uses typed tool permissions. Otherwise it retains the bounded generic extension-question flow.
 
 ## Known limitations

paseo-omp/TESTING.md

@@ -131,8 +131,10 @@ The plugin maintainer owns triage and adaptation. Escalate an isolated OMP imple
 
 `release-please.yml` creates GitHub releases and publishes every released plugin path to npm through trusted publishing. Stable versions use the `latest` distribution tag; prereleases use `next`. npm generates provenance from the GitHub Actions OIDC identity, and the workflow waits for registry propagation before succeeding.
 
-### Alpha release channel
+### Stable release channel
 
-`release-please-config.json` sets only `paseo-omp` to `prerelease: true` with `prerelease-type: alpha`. With the existing `initial-version: 0.1.0` and manifest version `0.0.0`, the first release PR is expected to prepare `0.1.0-alpha.1`, tag it as `paseo-omp-v0.1.0-alpha.1`, and mark the GitHub release as a prerelease. Other monorepo components keep their existing stable release behavior.
+The plugin is stable. Stable releases use npm's `latest` distribution tag and the `paseo-omp-v<version>` tag format. Follow the [release checklist](docs/release-checklist.md) for each release candidate.
 
-Do not manually edit `paseo-omp/package.json` or `.release-please-manifest.json` before that release PR; Release Please must update both atomically. After alpha validation, remove `prerelease` and `prerelease-type` from the `paseo-omp` package config and let Release Please prepare stable `0.1.0`. Never retag an alpha commit as stable.
+`release-please-config.json` sets no `versioning` strategy for `paseo-omp`, so Release Please uses conventional-commit bumps and produces stable versions; the repository GitHub releases are published as normal releases from `1.0.0` onward.
+
+Release Please owns package and manifest version updates. Do not edit those versions manually or retag a prerelease as stable.

paseo-omp/docs/core-provider-issue-audit.md

@@ -96,9 +96,9 @@ Status meanings:
 
 [#1176](https://github.com/getpaseo/paseo/issues/1176), [#1189](https://github.com/getpaseo/paseo/issues/1189), [PR #1177](https://github.com/getpaseo/paseo/pull/1177), [PR #1388](https://github.com/getpaseo/paseo/pull/1388), and [PR #2067](https://github.com/getpaseo/paseo/pull/2067) requested or introduced first-class OMP support. The plugin satisfies that product goal independently under `omp-plugin`; it does not replace or migrate bundled `omp` agents.
 
-## Release blockers and tracked gaps
+## Tracked gaps
 
-Before moving from alpha toward stable, track these separately:
+The plugin is stable. Track these remaining gaps separately from supported functionality:
 
 1. Decide whether native Fast mode can be represented honestly through the public provider SDK.
 2. Decide whether a first-class plan mode is possible; separately make `/handoff` reproducible in the controlled canary.

paseo-omp/docs/installation.md

@@ -8,7 +8,7 @@ Paseo plugins are trusted, unsandboxed code. Review this plugin and its package
 - 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.
+The plugin is stable. Review the release notes for any migration requirements before upgrading; supported versions and known limitations are documented in [Support](../SUPPORT.md).
 
 ## Install or update from npm
 

paseo-omp/docs/alpha-release-checklist.md → paseo-omp/docs/release-checklist.md

@@ -1,11 +1,11 @@
-# Alpha release checklist
+# Release checklist
 
-This checklist prepares `paseo-omp-v0.1.0-alpha.1`. It does not authorize publication. A maintainer must explicitly approve the tested package before any push, tag, GitHub release, or npm publication.
+This checklist prepares a `paseo-omp` release. It does not authorize publication. A maintainer must explicitly approve the tested package before any push, tag, GitHub release, or npm publication.
 
 ## Release identity
 
-- [ ] 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`.
+- [ ] Release Please proposes the expected next stable version from the previous release.
+- [ ] Package and tag names are `@omercnet/paseo-omp` and `paseo-omp-v<version>`.
 - [ ] Provider identity remains `omp-plugin`; bundled `omp` remains independent and enabled or disabled by the user.
 - [ ] Paseo requirement remains the reviewed range, currently `^0.9.2 || ^0.10.0 || ^0.11.0`.
 - [ ] Minimum tested OMP version, checksum, CI job, README, SUPPORT, and TESTING agree.
@@ -26,16 +26,16 @@ This checklist prepares `paseo-omp-v0.1.0-alpha.1`. It does not authorize public
 
 - [ ] Maintainer installs the exact `npm pack` candidate into the controlled official-Paseo Docker canary.
 - [ ] Maintainer verifies catalog, prompt, tools, configured MCP, permissions, steer, interrupt, import/resume, subagents, rewind, usage, Hub, and plugin surfaces.
-- [ ] Maintainer confirms the known limitations are acceptable for alpha.
+- [ ] Maintainer confirms the known limitations are acceptable for release.
 - [ ] Maintainer explicitly authorizes publication after testing. Silence or prior approval for development is not release authorization.
 
-## Alpha blocker
+## Release blocker
 
 - [x] `omp-audit.1`: incomplete or compacted `agent_end` frames recover success, failure, or native cancellation from complete streamed `message_end` evidence, or from bounded history whose entry IDs correlate with the streamed turn. Idle state is confirmed before and after retrieval, and concurrent interrupts remain authoritative. Missing, unavailable, non-correlatable, or conflicting terminal evidence fails closed with content-free count diagnostics.
 
-## Accepted alpha limitations
+## Accepted limitations
 
-These may remain only when called out in `SUPPORT.md`, `CHANGELOG.md`, and the GitHub prerelease notes:
+These may remain only when called out in `SUPPORT.md`, `CHANGELOG.md`, and the GitHub release notes:
 
 - Native Fast mode is not exposed.
 - No first-class plan mode; `/handoff` depends on native OMP prerequisites not reproduced by the deterministic canary.
@@ -46,15 +46,15 @@ These may remain only when called out in `SUPPORT.md`, `CHANGELOG.md`, and the G
 - The deterministic model does not implement OMP compaction summarization; protocol fixtures cover compaction behavior.
 - The tiny Ollama model is exploratory and is not a deterministic oracle.
 
-## Non-blocking post-alpha cleanup
+## Non-blocking cleanup
 
-- [ ] `omp-maintenance.1`: remove `ProviderRegistrationCompat`, both `ProviderCatalogOptionsCompat` declarations, and `parseProviderInputCompat` after the published `@getpaseo/plugin` types natively expose the registration hooks and request fields they bridge. The required upstream surface is `providerOptionsSchema`, `getCatalogCacheKey`, `checkAvailability`, catalog/session-list `providerOptions` plus `settings`, and session-open `deniedTools`. This is type/compatibility cleanup only; it must not change provider behavior and does not block alpha.
+- [ ] `omp-maintenance.1`: remove `ProviderRegistrationCompat`, both `ProviderCatalogOptionsCompat` declarations, and `parseProviderInputCompat` after the published `@getpaseo/plugin` types natively expose the registration hooks and request fields they bridge. The required upstream surface is `providerOptionsSchema`, `getCatalogCacheKey`, `checkAvailability`, catalog/session-list `providerOptions` plus `settings`, and session-open `deniedTools`. This is type/compatibility cleanup only; it must not change provider behavior and does not block a release.
 
 ## Release notes
 
-The prerelease notes must include:
+The release notes must include:
 
-1. Alpha support statement and compatibility range.
+1. Support statement, compatibility range, and any migration requirements.
 2. Permanent side-by-side `omp-plugin` identity.
 3. Provider SDK capability percentage and link to the README matrix.
 4. Link to the deduplicated [core-provider issue audit](core-provider-issue-audit.md).
@@ -65,4 +65,4 @@ The prerelease notes must include:
 
 ## Publication boundary
 
-Release Please may prepare metadata. Publication must use npm trusted publishing from the immutable release commit. Never retag an alpha commit as stable.
+Release Please may prepare metadata. Publication must use npm trusted publishing from the immutable release commit. Never retag a prerelease commit as stable.

release-please-config.json

@@ -36,8 +36,6 @@
       "package-name": "paseo-omp",
       "component": "paseo-omp",
       "initial-version": "0.1.0",
-      "prerelease": true,
-      "prerelease-type": "alpha",
       "include-component-in-tag": true,
       "extra-files": [{ "type": "generic", "path": "server/package-version.ts" }]
     },