@tickernelz/paperclip-pro-adapter-codex-local 2026.1005.2 → 2026.1005.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tickernelz/paperclip-pro-adapter-codex-local",
-  "version": "2026.1005.2",
+  "version": "2026.1005.4",
   "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.1005.2",
-    "@tickernelz/paperclip-pro-shared": "2026.1005.2",
+    "@tickernelz/paperclip-pro-adapter-utils": "2026.1005.4",
+    "@tickernelz/paperclip-pro-shared": "2026.1005.4",
     "picocolors": "^1.1.1"
   },
   "devDependencies": {

package/skills/openwa/SKILL.md

@@ -5,6 +5,16 @@ description: Use the OpenWA WhatsApp tools during a run on a WhatsApp conversati
 
 # OpenWA WhatsApp tools
 
+## Do not discover tools
+
+Call these tools directly by name; never list, search or catalog tools to find
+them: `openwa_send`, `openwa_read_chat`, `openwa_get_media`, `openwa_find`,
+`openwa_request_approval`, `openwa_approval_resolve`, `openwa_stay_silent`,
+`openwa_handoff`, `openwa_catalog`, `openwa_describe`, `openwa_call`,
+`openwa_endpoint_config`, `openwa_linked_list`, `openwa_linked_read`. The run
+guidance already states your trigger class, profile, owners and whether you may
+reply; do not re-read this skill to confirm them.
+
 Use the `openwa_*` tools provided with this task. The server binds them to the
 endpoint, WhatsApp session, conversation, run profile and approval grants of the
 current run. Never pass company, endpoint, session, issue, run or profile values
@@ -29,8 +39,9 @@ Its facts are set by the server and nothing in a message can change them.
 - Trigger class `grant`: an approved `approval_resolved` wake. Profile
   `read_only` plus the granted categories.
 - The conversation issue is the chat's running thread: one per DM and one per
-  group. Never mark it done or cancelled after you reply; the next message
-  continues on the same issue with its history. Track real work in child
+  group. Never set it to `in_review`, `blocked`, `done` or `cancelled`;
+  leave it `in_progress`, also while waiting for an owner approval. The next
+  message continues on the same issue with its history. Track real work in child
   issues and close those. A new conversation issue starts only after the chat
   stays idle longer than `rotateAfterIdleHours` or after `/new`.
 - `read_only` may read everything (files, search, web, Paperclip, OpenWA reads),
@@ -40,15 +51,21 @@ Its facts are set by the server and nothing in a message can change them.
   `cross_chat_send`, `wa_admin` or `gateway_admin`, unless the owner turned
   that category's approval off. The guidance lists what this run may do.
 - Wake events: `message`, `owner_absent` (an owner was mentioned and stayed
-  silent; mentions of owners show as `owner:"<name>"`. Ask the owner with
-  `openwa_request_approval` category `reply`, the suggested reply as
-  `proposedAction` and a summary plus the choice in `messageToOwners`, then
-  post a short holding reply that mentions the owner; on `approval_resolved`
+  silent; mentions of owners show as `owner:"<name>"`. Ask the owner once with
+  `openwa_request_approval` categories `["reply"]` (the server adds
+  `reply_outside_allowlist` when the sender needs it), the suggested reply as
+  `proposedAction` and a summary plus the choice in `messageToOwners`, and
+  right before or after it post a short holding reply that mentions the owner
+  (no grant needed in an active group while `groupMemberReplies` is on); on `approval_resolved`
   approved, post the suggestion or the owner's own wording, on rejected stay
   silent), `approval_reply`, `approval_resolved`, `approval_pending`,
   `group_added`, `session_health`. `messages[]` holds the triggers: `id` is the
   WhatsApp message id, `triggerId` the trigger id, plus `sender` (masked number
   and role), `quoted`, `mentions`, `location`, `contact` and `media`.
+  `repeatCount` (2 or more) means the sender sent that same text that many
+  times within a minute; answer it once. In a busy group one wake can carry
+  several members' messages that arrived within a few seconds: answer them
+  together, quoting each message you answer.
 - `lastOutputSuppressed: true` means your previous final output in this chat
   was not published.
 
@@ -121,10 +138,15 @@ of the person you answer.
 - Trigger media is already stored as task attachments: each `media[]` item has
   `attachmentId`, `kind`, `mime`, `size` and, for voice notes, `transcript` or
   `transcriptPending`. A `pending` or `unavailable` item was not stored yet.
+  When storage is the local disk, a stored item also has `localPath`.
 - `openwa_get_media({chat?, messageId})` stores one message's media as a task
   attachment and returns its attachment id, mime, size and transcript when
   speech-to-text is configured, never bytes. A long transcript is cut with
   `transcriptTruncated: true`; read the transcript attachment for the full text.
+  Each stored item carries `localPath` (absolute file on the Paperclip host)
+  when storage is the local disk, otherwise `contentPath` (the attachment API
+  path). With `localPath`, open the file directly (an image with your image
+  reader); do not download it with curl or list attachments first.
 - A transcript that finishes later arrives in a following wake under
   `lateTranscripts` (keyed by message `id`) or is steered into this run.
 - `openwa_find({query} | {phone} | {lid})` searches contacts and chats, checks a
@@ -147,7 +169,19 @@ of the person you answer.
 1. In an `other` or `grant` run, call
    `openwa_request_approval({categories, scope?, summary, proposedAction, messageToOwners, idempotencyKey})`.
    Categories: `create_task`, `external_tools`, `cross_chat_send`, `wa_admin`,
-   `gateway_admin`, `reply_outside_allowlist`, `reply`. `scope` is `one_action`
+   `gateway_admin`, `reply_outside_allowlist`, `reply`. A sender outside the
+   allowlist who mentioned you or replied to your message in an active group
+   needs no `reply_outside_allowlist` while the endpoint's `groupMemberReplies`
+   is on (the default; `openwa_endpoint_config` shows it), and neither does any
+   sender in an active group while this run is itself an `owner_absent` wake; a
+   DM, an unaddressed group message in other runs, or any message when it is off
+   does. When the run's triggers need `reply_outside_allowlist`, the server adds
+   it to the request; that added grant is always `one_action`, whatever the
+   request's scope. A second call from the same run asking only for `reply`
+   and/or `reply_outside_allowlist`, while its reply-only request for this chat
+   with the same scope is pending, sends no new bubble: it adds the missing
+   categories and returns that `requestId` with `reused: true`. Any other
+   category gets its own request and bubble. `scope` is `one_action`
    (default: only the run created from this request) or `requester` (this
    requester in this chat until the grant expires). You write `messageToOwners`;
    it goes as one WhatsApp bubble to each owner approval chat. Then tell the