@scotthuang/agent-knock-knock 0.3.0-beta.2 → 0.3.1

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog
 
+## 0.3.1 - 2026-07-28
+
+### Changed
+
+- Lower the OpenClaw plugin API, Gateway, and npm peer floor to the first verified stable API release, `2026.5.12`, and the normal installation host floor to `2026.6.5`, while continuing to build against `2026.7.1-2`.
+- Add isolated compatibility coverage for the minimum and build-time OpenClaw hosts, plus an explicit failing boundary at `2026.5.10-beta.2`.
+
+## 0.3.0 - 2026-07-28
+
+### Added
+
+- Publish the complete OpenClaw plugin, bundled AKK skill, and package-local relay through ClawHub, with stable npm and ClawHub installation paths.
+- Add bounded runtime diagnostics, fail-closed session selectors, stable short references, five-minute tmux and Managed ACPX quickstarts, and opt-in live smoke scripts.
+
+### Changed
+
+- Make installation configure and verify the OpenClaw runtime while preserving unrelated plugin settings.
+- Confirm asynchronous Gateway callback runs before settling delivery, instead of treating a `started` acknowledgement as delivered.
+
+### Fixed
+
+- Find the matching Codex completion across plausible same-workspace rollouts and reconcile durable completion before a newer same-pane task can supersede it.
+- Keep uncertain terminal completion and callback delivery states retryable without duplicating callbacks or attributing a newer task's screen output to an older monitor.
+
 ## 0.3.0-beta.2 - 2026-07-28
 
 ### Added

package/README.md

@@ -45,39 +45,43 @@ The two modes intentionally use different permission models:
 
 Core requirements:
 
-- A Node.js version supported by OpenClaw (Node.js 24.15+ on the 24.x line is recommended for the compatibility floor below)
-- [OpenClaw](https://docs.openclaw.ai/) Gateway and plugin API `2026.7.1-2` or newer
+- A Node.js version supported by your OpenClaw release (Node.js 24 LTS is recommended)
+- [OpenClaw](https://docs.openclaw.ai/) `2026.6.5` or newer
 - At least one authenticated coding agent: Codex, Claude Code, or Cursor
 
+| Compatibility layer | Version | Evidence |
+| --- | --- | --- |
+| Normal OpenClaw installation | `2026.6.5`+ | The packed plugin installs, loads, registers its full runtime, and passes isolated Gateway workflows. Earlier hosts block AKK's expected local process control in their legacy install-time scanner unless an unsafe override is used. |
+| Plugin API and Gateway | `2026.5.12`+ | This is the first stable release with `api.session.workflow.enqueueNextTurnInjection`. The adjacent tested boundary, `2026.5.10-beta.2`, lacks that API. |
+| Build SDK | `2026.7.1-2` | Build metadata stays pinned to the SDK actually used; it is not the runtime floor. |
+
+The compatibility suite tests the minimum and build-time hosts with isolated state and the real packed artifact.
+
 ### Install from ClawHub (recommended)
 
 ```bash
-openclaw plugins install clawhub:@scotthuang/agent-knock-knock@beta
+openclaw plugins install clawhub:@scotthuang/agent-knock-knock
 openclaw config set plugins.entries.agent-knock-knock.config.workspace "$PWD"
 openclaw config set plugins.entries.agent-knock-knock.config.defaultAgent codex
 openclaw config set plugins.entries.agent-knock-knock.config.mode tmux
 openclaw gateway restart
 ```
 
-The explicit `@beta` selector follows the `0.3.0` prerelease channel. Remove it after the stable ClawHub release is available.
-
 ClawHub installs the OpenClaw plugin, bundled AKK skill, and package-local relay CLI together. OpenClaw invokes that bundled CLI directly, but ClawHub does not add the `agent-knock-knock` command to your shell `PATH`. Do not run `install-openclaw` after a ClawHub install; that command belongs to the npm installation path below and would repeat the plugin setup.
 
 If you also want standalone shell commands such as `agent-knock-knock doctor`, install the npm package globally without running `install-openclaw`:
 
 ```bash
-npm install -g @scotthuang/agent-knock-knock@next
+npm install -g @scotthuang/agent-knock-knock
 ```
 
-### Install from npm (beta)
+### Install from npm
 
 ```bash
-npm install -g @scotthuang/agent-knock-knock@next
+npm install -g @scotthuang/agent-knock-knock
 agent-knock-knock install-openclaw --workspace "$PWD" --default-agent codex --mode tmux --verify
 ```
 
-The npm `next` dist-tag follows the same prerelease line. Remove `@next` after `0.3.0` becomes stable.
-
 `install-openclaw` installs or updates the plugin, atomically configures the selected workspace, agent, and mode without replacing unrelated settings, installs the AKK skill template, restarts the Gateway at most once, and optionally verifies the full runtime chain. It is safe to rerun. Without `--verify`, the result remains unverified rather than claiming readiness. Use `--skill-only` to skip plugin installation; add `--no-restart` to leave an explicit pending-restart state.
 
 If OpenClaw runs from a local checkout or another nonstandard location, pass its CLI explicitly:
@@ -298,18 +302,13 @@ See [CONTRIBUTING.md](https://github.com/scotthuang/agent-knock-knock/blob/main/
 
 ### ClawHub Maintainer Release
 
-The first `0.3.0` beta publish is intentionally manual and must stay on ClawHub's `beta` tag:
+The package is configured for ClawHub trusted publishing. Dispatch the `ClawHub Publish` workflow for a release; it derives `beta` versus `latest` from the package version and defaults to a dry run:
 
 ```bash
-npm ci
-npm run build
-npm exec clawhub -- login
-npm exec clawhub -- package publish . --family code-plugin --owner scotthuang --tags beta --dry-run --json
-npm exec clawhub -- package publish . --family code-plugin --owner scotthuang --tags beta
+gh workflow run clawhub-publish.yml --ref main -f dry_run=true
+gh workflow run clawhub-publish.yml --ref main -f dry_run=false
 ```
 
-After that first release creates the package, configure this repository as its trusted publisher. Future publishes use the manually dispatched `ClawHub Publish` workflow, which defaults to a dry run and derives `beta` versus `latest` from the package version.
-
 ## Storage and Logs
 
 State lives under `~/.agent-knock-knock/`. Directories use mode `0700`; state and log files use `0600`. Runtime logs redact common secrets and default to 14-day retention. Configure storage and logging with `--store-dir`, `AKK_LOG_DIR`, `AKK_LOG_LEVEL`, and `AKK_LOG_RETENTION_DAYS`; use a dedicated custom log directory.