@scotthuang/agent-knock-knock 0.14.14 → 0.14.16

package/docs/pi-dsh-compatibility.md

@@ -1,10 +1,65 @@
 # Pi and DeepSeek Harness connector compatibility
 
 These are independently versioned controller connectors. Installing an AKK
-core/OpenClaw release does not update an already installed connector. The
-published 2026-10-14 connectors pin AKK core `0.14.7`; DSH connector `0.1.0-rc.6`
-pins `0.14.8`. Each carries its runtime's canonical Skill and 26-tool
-capability handshake. Neither connector update requires a new core release.
+core/OpenClaw release does not update an already installed connector. Select
+npm `next` or the exact connector version below; their `latest` tags remain
+unchanged. Neither connector update requires a new core release.
+
+## Core 0.14.16 alignment — 2026-10-23
+
+| Connector | Release (`next`) | Exact core dependency | Host scope |
+| --- | --- | --- | --- |
+| Pi | `0.1.0-poc.5` | `0.14.16` | Pi `1.2.0` and `0.84.4` |
+| DeepSeek Harness | `0.1.0-rc.8` | `0.14.16` | Existing reviewed DSH/Cordis sets, including `0.2.1-rc.2` / `4.0.5` |
+
+Both connectors inherit the bounded List candidate-folding fix and unchanged
+exact Send/Watch identity rules. Core and both connectors now form one release
+set; see [the release procedure](../CONTRIBUTING.md). The connectors remain
+prereleases on `next`: installing without that tag may select an older `latest`.
+Upgrading a standalone core does not change a connector's installed dependency.
+This alignment adds no new Host compatibility claim or tclaude preview support.
+
+## Core 0.14.15 alignment — 2026-10-21
+
+| Connector | Version on `next` | Exact core dependency | Retained Host boundary |
+| --- | --- | --- | --- |
+| Pi | `0.1.0-poc.4` | `0.14.15` | Pi `1.2.0` and `0.84.4` |
+| DeepSeek Harness | `0.1.0-rc.7` | `0.14.15` | DSH `0.2.1-rc.2` / Cordis `4.0.5`; earlier reviewed RC/alpha/legacy sets below |
+
+This update aligns manifests, lockfiles, runtime version constants and
+regression checks with the published core. Both connectors dynamically
+register all **27 tools**, including `agent_knock_knock_watches`, and verify
+the bundled canonical Skill against the actual runtime capability handshake.
+The HostAdapter and handshake APIs remain compatible; this update does not
+broaden the supported Host versions or change callback admission policy.
+
+`/akk list` now returns discoverable conversations only. Use `/akk watches`
+for the separate, paginated observation inventory (recent 24 hours by default;
+older active or unresolved records remain visible). The core's lifecycle
+maintenance removes eligible healthy completed observations after 48 hours,
+while preserving unresolved records and deduplication receipts. Existing
+absolute deadlines, Store locations and callback routes are not migrated.
+The DSH-specific Store and Pi's existing Store configuration remain in effect.
+Core `0.14.13` introduced Store writer protocol 10; an older writer cannot
+continue writing that Store after activation. A downgrade requires a coherent
+backup or a compatible writer, rather than only changing the connector version.
+
+Validation uses the actual pinned core and real Host SDK dependencies in
+isolated installations: typecheck, connector fast tests (Pi 30; DSH 40),
+package/Skill parity, 27-tool registration and List/Watches command/schema
+checks. Pi `1.2.0` also passed an isolated real RPC startup and `/akk`
+registration check without a model task. Publication
+repeats each connector's own release gate on clean synchronized `main`, followed
+by a clean install of the public artifacts. The checks do not send tasks to
+business sessions or external chat channels. Full live task/model-consumption
+results below are dated historical evidence, not repeated claims for this
+core-only update. Daily Host installations are not upgraded by publication.
+
+## Historical verification
+
+The following dated records describe the Host compatibility work behind the
+retained support boundary. Their connector/core versions and test counts are
+kept as recorded at the time.
 
 ## DSH 0.2.1-rc.2 compatibility — 2026-10-17
 

package/docs/quickstart-herdr.md

@@ -1,6 +1,6 @@
 # Quick Start with Herdr
 
-AKK supports local Herdr `0.8.0` (socket protocol 19) as a terminal provider alongside tmux. AKK does not start Herdr or a coding agent.
+Starting in AKK `0.14.15`, local Herdr works alongside tmux according to the capabilities available for each operation. Herdr `0.8.0` (socket protocol 19) and `0.9.5` (socket protocol 22) are tested baselines, not a version allowlist. AKK `0.14.14` supported only `0.8.0`. AKK does not start Herdr or a coding agent.
 
 Install and open Herdr, then start Codex or Claude Code in a pane:
 
@@ -40,10 +40,22 @@ This creates an independent Terminal Watch schema-v3 record, not an AKK Session
 
 Herdr's raw `pane send-text` command is not used for task delivery. AKK uses the Unix-socket `pane.send_input` method so multiline text follows Herdr's bracketed-paste-aware path, persists the text-injected stage, resolves the stable terminal again, and then dispatches one separate Enter.
 
-Current boundary:
+## Current boundary
 
 - local Unix-domain sockets only;
-- exact Herdr `0.8.0`, protocol 19;
+- Herdr version and protocol are observed and must remain consistent during each operation; an unfamiliar pair alone does not prevent discovery;
 - the Codex and Claude Code versions in the main compatibility matrix are regression-tested; other complete `x.y.z` versions use the generic runtime protocol with a warning;
 - remote/SSH Herdr sessions and Windows named pipes are not yet supported;
 - Herdr's agent status is diagnostic only—AKK's existing screen, transcript, rollout, and native identity fences remain authoritative.
+
+Discovery must still prove the current socket, stable pane identity and process anchor. Zero-line, read-only probes independently check each pane's visible text, visible ANSI and detection text response contracts, including their source and format. A failed read capability is unavailable without disabling the other valid capabilities. No discovery or capability probe sends terminal input.
+
+For input, AKK checks `herdr api schema --json` from a CLI whose version matches the live server, requires the schema's protocol to match, and validates the request payload and acknowledgement declarations used by each input operation. The resulting `matching_cli_schema` evidence is a declaration of compatibility, not runtime negotiation or proof of atomic, single-enqueue input. An untested server without a matching declaration can expose only its verified read capabilities. Tested baselines may fall back to their reviewed input behavior when a matching schema is unavailable; an explicitly incompatible or malformed matching schema, including a protocol mismatch, does not use that fallback.
+
+Every operation revalidates current identity and capabilities. Dispatch acknowledgements do not prove that a coding agent accepted a task. For an untested server, an API error after input dispatch remains uncertain, including `pane_send_failed`; AKK does not assume it rejected input before enqueueing. Lost or unknown acknowledgements are never retried automatically.
+
+Doctor checks whether the installed Herdr command is a usable candidate without rejecting an unfamiliar version. It leaves live capabilities `not_probed`; installation readiness does not establish that a live pane can be read or controlled.
+
+The tested baselines include the official [Herdr `0.9.5` release](https://github.com/herdrdev/herdr/releases/tag/v0.9.5) of 2026-10-14 and its [protocol `22` declaration](https://github.com/herdrdev/herdr/blob/v0.9.5/src/protocol/wire.rs#L20). This does not claim live end-to-end Send/Watch validation for untested releases or every coding-agent version.
+
+Herdr's [live server handoff](https://github.com/herdrdev/herdr/blob/v0.9.5/docs/next/website/src/content/docs/session-state.mdx#L127) is experimental. This adapter does not promise uninterrupted tasks across an upgrade or restart. After a server change, refresh discovery so AKK can revalidate the current socket, terminal and process identities before further input.

package/docs/testing.md

@@ -27,7 +27,7 @@ synchronization have explicit non-regression budgets. See
 | `npm run test:affected` | Complete fast tier plus mapped integration tests; unknown or shared-core changes run the full tier | Maintainer/release diagnostics only; not an ordinary development command |
 | `npm run test:full` | The exact union of fast and integration tests | Immediate pre-publication gate for an actual npm or ClawHub release |
 | `npm test` | Compatibility alias for `test:full` | Same release-only boundary as `test:full` |
-| `npm run test:release` | Full suite, isolated current-build OpenClaw compatibility check, ClawHub runtime validation, and ClawHub publish dry-run | Immediate pre-publication gate for an actual npm or ClawHub release |
+| `npm run test:release` | Coordinated core/Pi/DSH version preflight and connector gates, full suite, isolated current-build OpenClaw compatibility check, ClawHub runtime validation, and ClawHub publish dry-run | Immediate pre-publication gate for an actual npm or ClawHub release |
 | `npm run test:release:live` | The release tier plus credentialed native Codex and Claude lifecycle smoke/attestation | Optional release-time diagnostic with dedicated prepared tmux panes |
 | `npm run compat:openclaw` | Full minimum/current/API-boundary OpenClaw compatibility matrix | Periodic maintainer check and any change to declared compatibility floors; not required for every package release |
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@scotthuang/agent-knock-knock",
-  "version": "0.14.14",
+  "version": "0.14.16",
   "description": "Delegate to existing Codex CLI, Codex Desktop, and Claude Code sessions from OpenClaw or compatible controller Hosts, with native direct control and supported terminal fallbacks.",
   "license": "MIT",
   "type": "module",

package/templates/openclaw-skills/agent-knock-knock/SKILL.md

@@ -7,7 +7,9 @@ description: Use Agent Knock Knock to discover and control Codex CLI, Codex Desk
 
 Use this skill when the user explicitly invokes `AKK`, `akk`, or `Agent Knock Knock`, or asks a supported controller Host to inspect or control a coding-agent conversation listed by AKK.
 
-AKK supports loaded local Codex CLI threads through their shared backend, local Codex Desktop conversations (with explicit creation when the Desktop Create tool is available), compatible already-open Claude Code CLIs through their native inbox, and Codex or Claude Code already running inside tmux or local Herdr `0.8.0`. It never launches a replacement coding agent. The controller Host, AKK, the coding agent, and its Desktop app or terminal host must run as the same OS user.
+AKK supports loaded local Codex CLI threads through their shared backend, local Codex Desktop conversations (with explicit creation when the Desktop Create tool is available), compatible already-open Claude Code CLIs through their native inbox, and Codex or Claude Code already running inside tmux or local Herdr with the required operation capabilities. It never launches a replacement coding agent. The controller Host, AKK, the coding agent, and its Desktop app or terminal host must run as the same OS user.
+
+Herdr `0.8.0` / protocol `19` and `0.9.5` / protocol `22` are tested baselines, not a version allowlist. Use fresh discovery and advertised actions: each pane's read capabilities are probed without input, while input requires a matching CLI schema declaration or verified baseline behavior. `matching_cli_schema` is declarative evidence from the same CLI version and server protocol, not runtime negotiation or proof of single-enqueue behavior. An untested server without that declaration exposes only verified reads; an incompatible declaration does not fall back to baseline behavior. Doctor installation readiness leaves live capabilities `not_probed`. Once input may have been dispatched, an uncertain response must not be retried automatically.
 
 Treat `AKK` and `akk` the same way.
 
@@ -21,7 +23,7 @@ Keep the user's requested scope and approval boundaries. Do not expand a task, a
 
 Present `conversations[]` as **CLI** or **Desktop** using `surface`, and keep Codex/Claude Code as the agent type. Select the displayed `conversation_id` and its advertised operation; AKK chooses the connection internally. Do not make separate user-facing backend and terminal lists, repeat raw discovery arrays, or count Watches as additional conversations or tasks. Preserve unavailable actions, current questions/approvals, and management/recovery records. Scoped controls, when present, are operations on exact targets within a row, not extra conversations.
 
-Default CLI presentation prefers the verified backend entry for a one-to-one same-agent/project discovery pair without known identity conflicts. Use that returned conversation ID and its actions directly; do not search for or choose an alternative transport. Its title, state and actions belong to the selected backend. Presentation preference does not prove a terminal alias, copy terminal permissions, or redirect a previously selected terminal ID. Multiple candidates, conflicts and terminal attention/recovery records remain visible. Proven exact aliases still combine verified controls. Use `terminalDebug: true` (CLI `list --terminal-debug`) only when connection diagnostics are needed, not as a routine selection step.
+Default CLI presentation prefers the verified backend entry for a one-to-one same-agent/project discovery pair without known identity conflicts. Use that returned conversation ID and its actions directly; do not search for or choose an alternative transport. Its title, state and actions belong to the selected backend. Presentation preference does not prove a terminal alias, copy terminal permissions, or redirect a previously selected terminal ID. Multiple candidates, conflicts and terminal attention/recovery records remain visible. Proven exact aliases still combine verified controls. Use `terminalDebug: true` (CLI `list --terminal-debug`) only when connection diagnostics are needed, not as a routine selection step. Unnamed, unstarted Codex candidates beside an established same-project conversation may be folded for display; `conversation_presentation.unstarted_candidates_omitted` reports their count and `diagnostic_query` expands them. This does not prove abandonment or an exact alias. If the requested new empty session is missing, use that query and its original exact ID; never substitute the established conversation. Sole or exactly associated new sessions remain visible, and a first task restores ordinary display.
 
 AKK prefers a reachable direct connection only after proving the exact selected native session and process or thread. An unavailable backend may retain an eligible terminal path; busy/blocked state or identity conflict cannot authorize bypass. Targeted operations on an idle terminal can use the existing advertised `/status` inspection to learn its identity; working or blocked terminals are not interrupted. List itself sends no terminal input. Keep an uncertain dispatch receipt and inspect it instead of retrying through another connection.