@tickernelz/paperclip-pro-adapter-codex-local 2026.1005.10 → 2026.1006.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tickernelz/paperclip-pro-adapter-codex-local",
3
- "version": "2026.1005.10",
3
+ "version": "2026.1006.0",
4
4
  "license": "MIT",
5
5
  "homepage": "https://github.com/tickernelz/paperclip-pro",
6
6
  "bugs": {
@@ -39,8 +39,8 @@
39
39
  ],
40
40
  "dependencies": {
41
41
  "@agentclientprotocol/codex-acp": "^1.6.2",
42
- "@tickernelz/paperclip-pro-adapter-utils": "2026.1005.10",
43
- "@tickernelz/paperclip-pro-shared": "2026.1005.10",
42
+ "@tickernelz/paperclip-pro-adapter-utils": "2026.1006.0",
43
+ "@tickernelz/paperclip-pro-shared": "2026.1006.0",
44
44
  "picocolors": "^1.1.1"
45
45
  },
46
46
  "devDependencies": {
@@ -192,11 +192,14 @@ of the person you answer.
192
192
  DM, an unaddressed group message in other runs, or any message when it is off
193
193
  does. When the run's triggers need `reply_outside_allowlist`, the server adds
194
194
  it to the request; that added grant is always `one_action`, whatever the
195
- request's scope. A second call from the same run asking only for `reply`
196
- and/or `reply_outside_allowlist`, while its reply-only request for this chat
197
- with the same scope is pending, sends no new bubble: it adds the missing
198
- categories and returns that `requestId` with `reused: true`. Any other
199
- category gets its own request and bubble. `scope` is `one_action`
195
+ request's scope. A call asking only for `reply` and/or
196
+ `reply_outside_allowlist`, while a reply-only request for this chat with
197
+ the same scope is pending from this run, or from an earlier run for the same
198
+ requester that already covers every pending non-owner message you see, from
199
+ anyone (for example an `owner_absent` wake on the message the first run
200
+ asked about), sends no new bubble: it adds the missing categories and
201
+ returns that `requestId` with `reused: true`. A new message from anyone,
202
+ any other category, or another requester gets its own request and bubble. `scope` is `one_action`
200
203
  (default: one gated call, made by the run created from this request; a
201
204
  `create_task` grant creates exactly one task) or `requester` (this
202
205
  requester in this chat until the grant expires). When the approved action