@tickernelz/paperclip-pro-adapter-codex-local 2026.930.1 → 2026.930.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tickernelz/paperclip-pro-adapter-codex-local",
-  "version": "2026.930.1",
+  "version": "2026.930.2",
   "license": "MIT",
   "homepage": "https://github.com/tickernelz/paperclip-pro",
   "bugs": {
@@ -39,8 +39,8 @@
   ],
   "dependencies": {
     "@agentclientprotocol/codex-acp": "^1.6.2",
-    "@tickernelz/paperclip-pro-adapter-utils": "2026.930.1",
-    "@tickernelz/paperclip-pro-shared": "2026.930.1",
+    "@tickernelz/paperclip-pro-adapter-utils": "2026.930.2",
+    "@tickernelz/paperclip-pro-shared": "2026.930.2",
     "picocolors": "^1.1.1"
   },
   "devDependencies": {

package/skills/paperclip/SKILL.md

@@ -255,6 +255,8 @@ This is the only way an agent hands its own work to a reviewer: create the revie
 
 **Courier pattern (lateral coordination):** to nudge or hand context to an agent whose issues you cannot write to, create a new issue assigned to that agent carrying complete, self-contained instructions. Issue-CREATE is company-scoped and always available; commenting into another agent's boundary is not.
 
+**Messages into a running turn:** a comment you post on another agent's task is steered into its current turn by default, so a scope change or correction lands while that agent is still working instead of after it finishes. Pass `deliver: "queue"` only when the message must wait for the current turn to end. Check `deliveredAs` in the result: `queued` with `steeringUnavailable` names why a steer did not land. A queued message is read at the assignee's next turn, and an unsteered message from another agent reopens a task that was closed as `done` in the meantime; on a `cancelled` task it stays in the thread and is never delivered, so raise anything urgent on a live task instead.
+
 ## Managing A User's Inbox
 
 Agents may archive an issue from a user's Mine inbox with `paperclipInboxArchiveIssue` and reverse it with `paperclipDeleteIssueInboxArchive`. Both are available when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`; otherwise use `paperclipApiRequest` with `method: "POST"` or `method: "DELETE"` and `path: "/issues/<issueId>/inbox-archive"`. Omit `userId` for the normal case: Paperclip resolves the responsible user from the agent's run context. An explicit `userId` targets another user and requires either that user's saved opt-in policy (`open` or an allowlist containing the agent) or a matching `inbox:manage` grant. The implicit default-open policy for a user who has never saved the control does not authorize explicit cross-user targeting.
@@ -647,7 +649,7 @@ If `plan` already exists, first call `paperclipGetDocument` (`issueId`, `key: "p
 | Compact heartbeat context             | `paperclipGetHeartbeatContext`                                                                                                                                    |
 | Update task                           | `paperclipUpdateIssue` (optional `comment` argument)                                                                                                              |
 | Get comments / delta / single         | `paperclipListComments` • `paperclipGetComment`                                                                                                                   |
-| Add comment                           | `paperclipAddComment` (`deliver: "queue"` or `"steer"`; steering a running turn is board-only, so an agent's steer is queued; read `deliveredAs` in the result)         |
+| Add comment                           | `paperclipAddComment` (a message on another agent's task steers its running turn by default; `deliver: "queue"` makes it wait for the turn boundary; read `deliveredAs` in the result)         |
 | Issue-thread interactions             | `paperclipListIssueInteractions` • `paperclipAskUserQuestions` • `paperclipRequestConfirmation` • `paperclipRequestCheckboxConfirmation` • `paperclipSuggestTasks` |
 | Create task / subtask                 | `paperclipCreateIssue` • `paperclipCreateChildIssue`                                                                                                              |
 | Release task                          | `paperclipReleaseIssue`                                                                                                                                           |

package/skills/paperclip/references/api-reference.md

@@ -640,6 +640,8 @@ The reliable machine-authored format is `[@Display Name](agent://<agent-id>)`. T
 
 Raw `@AgentName` text may still work for some single-token names, but treat it as a fallback only, not the default.
 
+**Message delivery:** a comment on a task assigned to another agent steers into that agent's running turn by default, so cross-task corrections and scope changes are read immediately. Set `deliver: "queue"` (or `commentDeliver: "queue"` on `paperclipUpdateIssue`) only when the message must wait for the current turn to finish. Comments on your own assigned task always wait for your next turn. The response carries `deliveredAs` (`steered` or `queued`) and, when queued, `steeringUnavailable`: `not_requested`, `identity_mismatch` (the message answers to a different user than the running turn), `board_only`, `no_active_run`, `legacy_protocol`, `conversation_order`, or `steering_failed`. A queued message is delivered at the assignee's next turn, and an unread message from another agent reopens a task the assignee closed as `done` in the meantime. On a `cancelled` task the comment stays in the thread but is never delivered, and a quarantined low-trust comment is delivered in its redacted form.
+
 **Do NOT:**
 
 - Use @-mentions as your default assignment mechanism. If you need someone to do work, create/assign a task.