@scotthuang/agent-knock-knock 0.14.6 → 0.14.8

package/CHANGELOG.md

@@ -1,5 +1,31 @@
 # Changelog
 
+## 0.14.8 - 2026-10-14
+
+- Enable blocking and asynchronous question answers on macOS Codex Desktop `26.1007.30912` / build `20156`, independently of model/permission settings and cancellation. Use the advertised Respond action from fresh conversation or exact Watch Status.
+- Preserve exact task/request identity, one-dispatch response records and native answer confirmation. Real Desktop validation covered an asynchronous choice, free text, and a two-question Plan request; original tasks consumed the answers and completed. Local attention/completion callbacks were verified, not external chat delivery.
+
+## Connector releases - 2026-10-14
+
+- Publish Pi connector `0.1.0-poc.3` and DeepSeek Harness connector `0.1.0-rc.5` independently under npm `next`; neither changes the core `0.14.7` version or promotes a connector to stable `latest`.
+- Pin both connectors to published AKK `0.14.7`, aligning the installed HostAdapter, lockfiles, 26 registered tools and canonical Skill handshake. The connectors now expose that core's direct CLI/Desktop capabilities under the existing per-target limits.
+- Support Pi `1.2.0`, retaining the reviewed `0.84.4` runtime. Use the actual Host version in the callback profile, adapt the tool execution context, and support exact conversation/Watch approval confirmations with explicit allow/reject labels.
+- Adapt DSH `0.2.0-rc.2` and separately reviewed `0.2.1-alpha.2` package contracts: coherent Host/Cordis peers, AKK-specific message source typing, and current schema/Skill validation. DSH `latest` remains a release candidate, not a stable release.
+- Preserve exact live controller ownership, callback deduplication and conservative recovery: an accepted callback is not a model-consumption or external-chat-delivery guarantee; old routes do not migrate automatically to a restarted Host.
+
+See [connector compatibility and validation](docs/pi-dsh-compatibility.md) for the version matrix and evidence boundaries.
+
+## 0.14.7 - 2026-10-14
+
+- Enable explicit command and file approvals on macOS Codex Desktop `26.1007.30912` / build `20156`: allow once or reject from the controller, through the original Desktop conversation.
+- Advertise approvals independently from broader native controls across List, Status, Watch and interaction notifications. Question answers, model/permission changes and cancellation remain unavailable on this build; the reviewed build `13536` retains its existing controls.
+- Preserve exact owner, task and pending-request checks, one-dispatch response records and effect verification. An IPC acknowledgement alone does not confirm approval; consumed or uncertain responses are not blindly replayed.
+
+### Validation boundaries
+
+- A dedicated Desktop conversation verified real semantic Send/Status/Approve for command allow/reject and file allow/reject, including successful execution or file changes after approval and absent side effects after rejection. Local attention/completion callbacks were accepted once each; no external chat-delivery claim is made.
+- This release adds no persistent authorization rules or full-access mode changes.
+
 ## 0.14.6 - 2026-10-13
 
 - Present CLI and Desktop conversations together, with Codex/Claude Code as the agent type. Keep transport details in diagnostics instead of showing backend and terminal connections as separate user-facing categories.

package/README.md

@@ -74,24 +74,23 @@ That is the terminal first-task flow. For terminal setup and multiple panes, see
 
 ## Install for Pi
 
-Pi can be the controller Host without OpenClaw. The current connector targets Pi `0.84.4`:
-
-This connector currently depends on AKK `0.13.3`; the new 0.14 direct CLI and Desktop capabilities described above apply to the OpenClaw plugin. Follow the connector guide for its supported features.
+Pi can be the controller Host without OpenClaw. The connector supports Pi `1.2.0`
+and retains `0.84.4` compatibility. It includes AKK `0.14.7`, with direct CLI and
+Desktop capabilities governed by the same target-specific boundaries above.
 
 ```bash
-npm install -g @earendil-works/pi-coding-agent@0.84.4
+npm install -g @earendil-works/pi-coding-agent@1.2.0
 pi install npm:@scotthuang/agent-knock-knock-pi@next
 pi
 ```
 
-Pi should show `AKK ready`. With Codex or Claude Code already running in tmux or Herdr, enter `/akk list`. The connector provides `/akk`, the complete capability-handshake-verified semantic tool catalog, the bundled `agent-knock-knock` skill, callbacks to the initiating Pi session, and native approval dialogs. See the [Pi connector guide](connectors/pi/README.md).
+Pi should show `AKK ready`. With a supported coding-agent conversation open, enter `/akk list`. The connector provides `/akk`, the complete capability-handshake-verified semantic tool catalog, the bundled `agent-knock-knock` skill, callbacks to the initiating Pi session, and native approval dialogs. See the [Pi connector guide](connectors/pi/README.md).
 
 ## Install for DeepSeek Harness
 
-The connector supports DeepSeek Harness Web `0.1.1-rc.2`, `0.1.2-alpha.1`, and
-`0.1.5-rc.2`:
-
-This connector currently depends on AKK `0.13.3`; its supported features are documented separately from the OpenClaw plugin's 0.14 direct CLI and Desktop capabilities.
+The connector targets DeepSeek Harness Web `0.2.0-rc.2` (upstream `latest`,
+**still a release candidate**). It includes AKK `0.14.7`. See the connector guide
+for the separate alpha and older-version validation boundaries.
 
 ```bash
 dsh plugin --profile web add @scotthuang/agent-knock-knock-deepseek-harness@next
@@ -102,9 +101,9 @@ Open a Web conversation and enter `/akk list`. The connector gives every convers
 
 ## See It in Action
 
-[![AKK orchestrating a Claude Code-to-Codex handoff through tmux](https://raw.githubusercontent.com/scotthuang/agent-knock-knock/main/docs/assets/akk-tmux-handoff-demo.gif)](https://github.com/scotthuang/agent-knock-knock/blob/main/docs/assets/akk-tmux-handoff-demo.mp4)
+https://github.com/user-attachments/assets/cc20a609-7907-4996-977e-0b88d8ba6388
 
-*OpenClaw asks Claude Code to write a file, waits for AKK to report completion, then hands the result to Codex. Both terminals remain available for direct human control. This demo uses tmux; supported Codex CLI and Desktop connections no longer need it. Click the preview for the full-quality video.*
+*Send a task from your phone. AKK creates a Codex Desktop conversation, handles approvals with your permission, and brings the result back to chat.*
 
 ## What AKK Gives You
 
@@ -200,16 +199,16 @@ can use a supported terminal route. Claude Code direct control is available unde
 | Component | Supported boundary |
 | --- | --- |
 | Terminal hosts | tmux; local Herdr `0.8.0` protocol `19` |
-| Codex Desktop | macOS app `26.1002.52244`, build `13536`; this **exact build**, plus an open connected conversation, is required for sending and other controls. Supports Status, exact Watch, approvals/answers, settings, and cancellation. |
+| Codex Desktop | macOS, exact app/build profiles: `26.1002.52244` / `13536` supports the reviewed full controls; `26.1007.30912` / `20156` supports creation and Send/Status/Watch. AKK 0.14.7 adds command/file approvals (allow once or reject) on `20156`, and 0.14.8 adds blocking and asynchronous answers; settings and cancellation remain unavailable there. See the [operation matrix](docs/codex-desktop-compatibility.md#version-and-platform-evidence). |
 | Codex CLI shared backend | Live-tested on macOS: CLI `0.162.1` + backend `0.162.1`, and previously `0.160.0` + `0.162.0`. Requires a loaded main CLI conversation and compatible live protocol. These are tested combinations, **not a numeric minimum**. |
 | Claude Code direct connection | macOS, live-tested `2.1.296`, compatible native peer protocol `1`, and Python 3 available to AKK. Basic task sending, progress and completion observation; unsupported controls require the original terminal. See the [direct guide](docs/claude-cli-direct.md). |
 | Terminal coding agents | Reviewed Codex profiles include `0.160.0` and `0.162.1`; Claude Code `2.1.285` was tested on macOS. Unknown versions may expose limited capabilities; native controls depend on the reviewed profile and current UI. |
 | OpenClaw | `2026.6.5`+; plugin API and Gateway `2026.5.12`+ |
-| Pi connector | Pi `0.84.4`; connector currently depends on AKK `0.13.3` |
-| DeepSeek Harness connector | `0.1.1-rc.2`, `0.1.2-alpha.1`, and `0.1.5-rc.2`; connector currently depends on AKK `0.13.3` |
+| Pi connector | Pi `1.2.0` and `0.84.4`; connector `0.1.0-poc.3` (`next`), pinned AKK `0.14.7` |
+| DeepSeek Harness connector | Web `0.2.0-rc.2` (RC); connector `0.1.0-rc.5` (`next`), pinned AKK `0.14.7`. See its guide for alpha and legacy coverage. |
 | Runtime | Node.js `22.19.0`+ on macOS or Linux |
 
-The adjacent OpenClaw boundary `2026.5.10-beta.2` is intentionally unsupported. Herdr and Desktop controls depend on reviewed private protocol versions. Desktop catalog presence alone does not prove the conversation is open or controllable. See each connector guide and the Desktop guide for tested boundaries and limitations.
+The adjacent OpenClaw boundary `2026.5.10-beta.2` is intentionally unsupported. Herdr and Desktop controls depend on reviewed private protocol versions. Desktop catalog presence alone does not prove the conversation is open or controllable. See each connector guide, the [Pi/DSH validation matrix](docs/pi-dsh-compatibility.md), and the Desktop guide for tested boundaries and limitations.
 
 Codex CLI model changes and cancellation still require an eligible terminal.
 New/clear/resume operations for paginated Codex CLI `0.158+`, and creating or

package/connectors/deepseek-harness/README.md

@@ -13,26 +13,39 @@ tests, lockfile, bundle manifest, and connector-specific release tag.
 
 ## Compatibility
 
-This connector pins AKK **0.13.3** in its package and lockfile. Its terminal
-workflow is separate from the AKK 0.14.0 CLI direct, Desktop, and Recovery
-features in the [root README](../../README.md). Neither a newer core release
-nor a root checkout replaces the connector's pinned runtime automatically.
-
-This prerelease supports DeepSeek Harness `0.1.1-rc.2`, `0.1.2-alpha.1`, and
-`0.1.5-rc.2` on the resident Web Host and Node.js `>=22.19.0`. Activation locates the real
-`@deepseek-ai/dsh` launcher and requires that launcher plus its `dsh-base`,
-`dsh-agent`, `dsh-commands`, `dsh-llm`, and `dsh-tools` packages to form one
-coherent set at one reviewed version. An unsupported, missing, or split Host
-fails before mounting. The detected launcher version is also projected into the
-private AKK Host Profile instead of being replaced with a connector build-time
-version. Runtime message and schema helpers are imported from that verified
-Host package tree, so a source checkout's development dependencies cannot
-replace them.
-
-Headless/one-shot Harness processes, Host-exit callback continuity, and Windows
-named pipes are not supported in this release. AKK discovers existing Codex and
-Claude Code processes in tmux or Herdr; this connector does not start those
-processes or create terminal panes.
+This connector pins AKK **0.14.7** in its package and lockfile. It exposes
+that runtime's 26 semantic tools, including Codex CLI backend and Desktop
+operations when the selected conversation advertises them. A newer root
+checkout does not silently replace this published dependency.
+
+The development baseline is DeepSeek Harness **0.2.0-rc.2** (the upstream
+`latest` channel). **0.2.1-alpha.2** is separately reviewed preview support.
+Neither is a stable release. The older reviewed Hosts `0.1.1-rc.2`,
+`0.1.2-alpha.1`, and `0.1.5-rc.2` remain accepted. Use a resident POSIX Web Host
+and Node.js `>=22.19.0`.
+
+Activation locates the real `@deepseek-ai/dsh` launcher and requires the
+launcher, `dsh-base`, `dsh-agent`, `dsh-commands`, `dsh-llm`, `dsh-skill`, and
+`dsh-tools` to form one coherent reviewed version. Unsupported, missing, and
+split runtime sets fail before mounting. The Host's own plugin peer preflight
+must also pass without a version-risk exemption. Message and schema helpers
+come from that verified Host tree, not checkout development dependencies.
+
+Callbacks use AKK's producer-specific message source and the same live Agent's
+Inbox. Idle Agents receive a waking `followup`; running Agents receive
+`inject` context at a later step. Acceptance means Inbox admission, not proof
+that a model has consumed it or a user has seen it. Host exit or plugin unload
+invalidates that Host instance's routes; callbacks do not migrate to a new
+Agent merely because it has the same session ID.
+
+Headless/one-shot Harness processes, Host-exit callback continuity, Windows
+named pipes, and DSH Desktop's embedded launcher are outside this connector's
+validated scope. Existing Codex CLI backend and Desktop connections need no
+terminal container when their advertised capability is available. Claude Code
+and terminal-specific operations retain their documented transport conditions;
+see [core compatibility](../../README.md#compatibility) and the
+[Pi/DSH validation matrix](../../docs/pi-dsh-compatibility.md). This connector does
+not launch replacement coding processes or create terminal panes.
 
 ## Five-minute quick start
 
@@ -72,34 +85,38 @@ tool invocation.
 
 ### 3. Verify discovery in a Web conversation
 
-Make sure at least one Codex or Claude Code process is already running inside a
-tmux or Herdr pane, then enter:
+Open a supported Codex CLI or Desktop conversation, or a supported coding
+agent in tmux/Herdr for the terminal workflow, then enter:
 
 ```text
 /akk list
 ```
 
-The compact result contains that live terminal, current action names, and only
+The compact result contains the visible CLI/Desktop conversations, current action names, and only
 the dynamic inputs needed for those actions. Static action meanings and safety
 rules come from the automatically registered `agent-knock-knock` skill. AKK
 never asks callers to invent identifiers: copy only the complete
-`terminal_id`, `session_id`, `turn_id`, `watch_id`, or `native_thread_id`
+`conversation_id`, `terminal_id`, `session_id`, `turn_id`, `watch_id`, or `native_thread_id`
 returned by AKK.
 
 ### 4. Send one task and receive its callback
 
-If exactly one matching terminal is send-ready, this is a complete smoke test:
+For the terminal shortcut, if exactly one matching terminal is send-ready,
+this is a complete smoke test:
 
 ```text
 /akk codex: Inspect package.json and report the package name. Do not modify files.
 ```
 
-Use `claude:` instead when testing Claude Code. With multiple matching panes,
-run `/akk list` first and use the displayed session selector, or let the Agent
-call `agent_knock_knock_send` with the exact semantic identifier in that row's
-advertised action.
+Use `claude:` instead when testing Claude Code. For backend/Desktop routes or multiple matches,
+run `/akk list` and let the Agent call `agent_knock_knock_send` with the exact
+identifier in the selected row's advertised action. AKK chooses the available
+transport; do not reconstruct IDs from project paths.
 
-An accepted managed Send creates a `turn_id`. When the coding agent finishes,
+A backend/Desktop Send normally returns its exact task Watch. Terminal managed
+Send returns a `turn_id`; preserve the actual receipt instead of assuming one
+record type. An existing automatic Watch does not need a second subscription.
+When the coding agent finishes,
 asks a question, becomes blocked, or requests approval, AKK sends a callback to
 the same live DeepSeek Harness Agent. A running Agent receives the update via
 `inject()`; an idle Agent receives it via `followup()`.
@@ -133,24 +150,28 @@ behavior through the complete capability-handshake-verified tool catalog:
 
 | Tool | Purpose |
 | --- | --- |
-| `agent_knock_knock_list` | List live Codex/Claude terminals, managed state, Terminal Watches, and each row's currently available actions. |
-| `agent_knock_knock_watch` | Start durable, read-only observation of one exact `terminal_id`. |
+| `agent_knock_knock_list` | List CLI/Desktop conversations, monitoring records, and each row's currently available actions. |
+| `agent_knock_knock_watch` | Observe one advertised conversation or terminal, preserving its exact task anchor when available. |
 | `agent_knock_knock_unwatch` | Stop one exact `watch_id` without sending terminal input. |
 | `agent_knock_knock_list_resumable_threads` | List structurally verified native threads for one terminal. |
 | `agent_knock_knock_native_inspect` | Run only the adapter-owned native `status` inspection advertised for an idle terminal. |
 | `agent_knock_knock_model_options` | Read one exact idle terminal's native model and reasoning catalog and create a single-use typed offer. |
 | `agent_knock_knock_repair_model_control` | Dismiss only an exactly recognized stale model-control surface; it never selects a model or submits work. |
+| `agent_knock_knock_permission_options` | Read currently available permission choices for one exact target. |
+| `agent_knock_knock_set_permissions` | Apply one currently advertised permission choice. |
+| `agent_knock_knock_desktop_create` | Create a Codex Desktop conversation only when the creation capability is advertised. |
+| `agent_knock_knock_recover` | Perform an advertised recovery action on its original observation or callback record. |
 | `agent_knock_knock_set_model` | Consume the current catalog offer to choose one advertised semantic model and reasoning effort. |
 | `agent_knock_knock_identify_foreground` | Run a bounded diagnostic native identity probe without creating durable authority. |
 | `agent_knock_knock_identify_and_send` | Keep one terminal lock across identity observation and one explicit Send when foreground identity is ambiguous. |
 | `agent_knock_knock_new_thread` | Start and verify a clean native coding-agent thread after explicit user intent. |
 | `agent_knock_knock_reconcile_binding` | Detach one proven stale conflicting binding after explicit confirmation; it neither sends work nor adopts a thread. |
 | `agent_knock_knock_resume_thread` | Resume one complete `native_thread_id` from a fresh resumable-thread listing. |
-| `agent_knock_knock_status` | Inspect one AKK `turn_id` or Terminal Watch `watch_id` plus a bounded current screen. |
+| `agent_knock_knock_status` | Read one conversation, Turn, or Watch; backend progress is bounded and belongs to the exact native task. |
 | `agent_knock_knock_send` | Send a new task through the exact action advertised by `list`. |
 | `agent_knock_knock_respond` | Answer a question or unblock one existing managed Turn; it does not create a new Turn. |
 | `agent_knock_knock_respond_interaction` | Answer the current typed native questionnaire step for one exact response-capable Turn or Watch. |
-| `agent_knock_knock_approve` | Approve the current exact permission request once, only after human review and confirmation. |
+| `agent_knock_knock_approve` | Apply the advertised allow-once or reject decision to the current exact permission request, after human review. |
 | `agent_knock_knock_renew` | Renew monitoring for a still-live stalled Turn without typing into the terminal. |
 | `agent_knock_knock_retry_callback` | Retry one persisted failed callback with its original message and delivery identity. |
 | `agent_knock_knock_cancel` | Interrupt one exact active Turn while leaving the shared pane open. |
@@ -158,15 +179,15 @@ behavior through the complete capability-handshake-verified tool catalog:
 
 The ordinary closed loop is:
 
-1. Call `list` and select one exact terminal row.
+1. Call `list` and select one exact conversation or terminal row.
 2. Use only that row's advertised `send` action and semantic identifier.
-3. Retain the returned `turn_id` for managed delivery, or the `watch_id` from an
-   automatic physical-Send fallback. Completion or attention callbacks return
+3. Retain the returned `turn_id` or automatic `watch_id`. Completion or attention callbacks return
    to the originating DeepSeek Harness Agent.
 4. For a managed question or blocked callback, use `respond` with its `turn_id`.
    For a permission request, follow the approval procedure below.
-5. Use `status` when a callback is late or uncertain. Use an explicit `watch`
-   for other work that was not sent as a managed AKK Turn.
+5. Use `status` when a callback is late or uncertain. Add an explicit `watch`
+   only when the user requests monitoring of ongoing work that has no suitable
+   active monitor. A Send-created Watch already owns its completion subscription.
 
 Do not cache `available_actions` or private terminal state. Refresh `list` or
 `status` before a mutation, and never blindly retry an uncertain Send,
@@ -180,16 +201,18 @@ dialog around that tool. Explicit human confirmation is therefore a required
 calling contract for the Agent and user, not a UI gate enforced by this
 connector. With the default configuration, the manual flow is:
 
-1. Receive the approval callback, then call
-   `agent_knock_knock_status({turn_id})` to refresh the exact current request and
-   terminal screen.
+1. Receive the approval callback, then refresh Status using its exact
+   `watch_id`, `conversation_id`, or managed `turn_id`. Read the current native
+   request; terminal routes may also return a screen excerpt.
 2. Present the current request, tool name, and relevant arguments to the user.
-3. Obtain an explicit approve or reject decision in the same Web conversation.
-4. Only for an explicit approval, invoke the currently advertised
-   `agent_knock_knock_approve({turn_id})`, or let the user enter
-   `/akk approve <turn-selector>`.
-5. If approval was interrupted or returned an uncertain result, refresh status
-   and let the human inspect the live TUI. Never retry it blindly.
+3. Obtain an explicit allow-once or reject decision in the same Web conversation.
+4. Copy the currently advertised `agent_knock_knock_approve` action, keeping its
+   exact target and `interaction_id` where supplied. Pass `decision: "approve_once"`
+   or `decision: "reject"` only when that target advertises the corresponding
+   decision. The legacy `/akk approve <turn-selector>` shortcut is for managed
+   Turn approval, not a replacement for direct interaction identifiers.
+5. If the operation was interrupted or returned an uncertain result, refresh
+   Status and inspect the original conversation. Never retry it blindly.
 
 AKK's deterministic `pluginConfig.autoApprove` policy remains disabled by
 default. If an administrator deliberately enables it, only the exact configured
@@ -221,12 +244,15 @@ to the exact DeepSeek Harness Agent's inbox/session log. It does not prove that
 the model consumed the message or that asynchronous persistence reached stable
 storage. `status` and Terminal Watch are the recovery path.
 
-- If the exact Agent and Host are still live, inspect the `turn_id` with
-  `status`. A persisted callback failure can be retried with
-  `agent_knock_knock_retry_callback`; AKK reuses the original callback message
-  id and Turn identity for idempotent delivery.
-- For a Terminal Watch, inspect its `watch_id` with `status`. If the route is no
-  longer valid, `unwatch` it and start a fresh Watch from a current `list` row.
+- Inspect the original `turn_id` or `watch_id` with `status`. If that exact
+  record advertises `retry_callback`, a requested retry reuses the persisted
+  callback message and delivery identity. An uncertain result is not evidence
+  of non-delivery; do not replay it without a supported recovery action.
+- A completed Watch still provides its exact result even when the original
+  callback route is gone. Read that result; creating another Watch does not
+  recover or replay the historical notification. For work that is still
+  running, a fresh observation from a current `list` row requires the user's
+  monitoring request. Do not transfer an old record's callback ownership.
 - A Host restart creates a new private Profile revision. Existing watches retain
   their original route, so callbacks owned by the old Host incarnation fail
   closed instead of being redirected to a new Agent. There is deliberately no
@@ -292,11 +318,11 @@ The optional bundle patch mounts only the Host plugin:
 | `@next` cannot be resolved | Run `npm view @scotthuang/agent-knock-knock-deepseek-harness dist-tags --json`. Use an exact published version if your registry has no `next` tag, or use the local-development installation below. |
 | `/akk` and AKK tools are missing | Verify installation with `dsh plugin --profile web why @scotthuang/agent-knock-knock-deepseek-harness`, then fully restart the Web Host. Existing Host processes do not gain a newly added bundle. |
 | Activation reports an unsupported or split Harness | Check `dsh --version` and run `dsh plugin --profile web why @deepseek-ai/dsh-base @deepseek-ai/dsh-agent @deepseek-ai/dsh-commands @deepseek-ai/dsh-llm @deepseek-ai/dsh-tools`. Update the whole Host coherently; do not repair it with a standalone connector npm install. |
-| `/akk list` finds no terminals | Start or locate a real Codex/Claude Code process inside tmux or Herdr. AKK never launches the coding agent or creates its pane. |
+| `/akk list` finds no live conversations | Check the selected target's direct-connection or terminal discovery diagnostics and core compatibility. A supported Codex CLI backend/Desktop connection does not require tmux/Herdr; terminal-only control needs an eligible live pane. Do not infer missing identity from cwd alone. |
 | A mutation is absent or rejected | Refresh `/akk list` or structured `list` and use only the action currently advertised for that exact row. Resolve a current approval first when it blocks input. Do not reuse stale IDs or action payloads. |
-| The callback never appears | Run `/akk status <turn-or-watch-id>`. If the same route is live, use the persisted `retry_callback` tool for a failed Turn callback. After a Host restart or Agent replacement, old delivery fails closed; recreate a Watch or start new work from the current Agent. |
+| The callback never appears | Query the original Turn/Watch Status and separate task result, callback admission, and user visibility. Use only a retry/recovery action advertised for that record and requested by the user. A new Host does not inherit old callback ownership. |
 | Callback delivery reports IPC unavailable or timeout | Keep the originating Web Host alive and inspect whether it was restarted or disposed. The socket is Host-process-private and has an eight-second callback boundary; there is no cross-process fallback route. |
-| A Watch completed but its callback was missed | Query `status` by `watch_id`. Under a new Host incarnation, unwatch the old record and create a fresh Watch from a current terminal row. |
+| A Watch completed but its callback was missed | Read the original `watch_id` Status for its exact task result and callback disposition. Do not create a replacement Watch for completed work or treat it as historical-notification recovery. |
 | A tool call fails schema validation | Pass only the documented fields and complete semantic IDs returned by AKK. DeepSeek's discovery schema is a projection; the connector always enforces the full original AKK schema before execution. |
 | Windows, headless, or one-shot use fails | These surfaces are outside this prerelease's supported scope. Use the resident POSIX Web Host. |
 
@@ -313,7 +339,7 @@ Update to the registry's current prerelease, or pin an exact reviewed version:
 
 ```sh
 dsh plugin --profile web add @scotthuang/agent-knock-knock-deepseek-harness@next
-dsh plugin --profile web add @scotthuang/agent-knock-knock-deepseek-harness@0.1.0-rc.4
+dsh plugin --profile web add @scotthuang/agent-knock-knock-deepseek-harness@0.1.0-rc.5
 ```
 
 Restart the Web Host after either operation. The connector pins the exact AKK
@@ -341,14 +367,14 @@ dsh plugin --profile web add "file:$(pwd -P)/connectors/deepseek-harness"
 ```
 
 Restart `dsh web` after installation. The child package currently installs and
-tests against its pinned published AKK runtime `0.13.3`; building the current
+tests against its pinned published AKK runtime `0.14.7`; building the current
 repository root does not silently replace that dependency. Testing connector
 changes against another AKK runtime requires an explicit dependency change and
 compatibility review rather than an implicit local link.
 
 ## Tests and release status
 
-The package manifest is currently `0.1.0-rc.4`, so this remains a prerelease and
+The package manifest is currently `0.1.0-rc.5`, so this remains a prerelease and
 is published under `next`; `latest` remains on the earlier `0.1.0-rc.1` tag.
 Registry state can change independently of this source file, so the `npm view`
 commands above remain authoritative.
@@ -364,11 +390,13 @@ npm run pack:check
 
 These commands typecheck the connector, run its fast wiring/profile/IPC/schema
 tests, and inspect the package tarball. They do not publish anything. The
-`0.1.0-rc.4` compatibility work is typechecked against the published DeepSeek
-Harness `0.1.5-rc.2` SDK packages and runtime-smoked against that exact official
-launcher package tree. The reproducible development lock therefore uses
-`0.1.5-rc.2`, while peer and runtime checks retain the two older reviewed Host
-versions for existing installations.
+`0.1.0-rc.5` lockfile uses the published DeepSeek Harness `0.2.0-rc.2`
+SDK packages. The same source is checked separately against preview
+`0.2.1-alpha.2` and retained `0.1.5-rc.2`. The older `0.1.1-rc.2` and
+`0.1.2-alpha.1` compatibility policy is retained; it is not a new full Web
+acceptance claim for those releases. Deterministic Host-loop checks use the
+real upstream registries and Inbox with a scripted model provider; they are
+not evidence of a live paid model or external-channel delivery.
 
 ## Release safety
 
@@ -398,7 +426,7 @@ gate to both connectors. Their package versions are validated independently.
 Publishing additionally requires both explicit flags:
 
 ```sh
-npm run release:check -- --publish --confirm-version 0.1.0-rc.4
+npm run release:check -- --publish --confirm-version 0.1.0-rc.5
 ```
 
 Prereleases use npm tag `next`; stable versions use `latest`. Repository tags