@sjawhar/opencode-legion-envoy 5.4.3 → 5.4.5

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": "@sjawhar/opencode-legion-envoy",
3
- "version": "5.4.3",
3
+ "version": "5.4.5",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "main": "dist/src/server.js",
@@ -82,7 +82,8 @@ because replying to an ask makes you one of its followers (see [Following](skill
82
82
  `quote` requires `artifact`; its anchor is pinned to the containing block while retaining the quote
83
83
  for display. Omit both for a floating issue comment. A reply (`reply_to`/`reply_to_ask`) takes no
84
84
  `quote`; it belongs to its parent's anchor. Reply to any comment in a thread; the server keeps
85
- threads flat. A reply to a resolved thread reopens it. Use `reply_to_ask` to reply directly under a
85
+ threads flat. A reply to a resolved thread reopens it, except a decided suggestion's: a reply joins
86
+ that thread and the suggestion stays accepted or rejected. Use `reply_to_ask` to reply directly under a
86
87
  question asked with `dispatch_ask`; `turn` (only with `reply_to_ask`) says who holds the turn after
87
88
  the reply — `agent` for a progress note that keeps the ask waiting on you, `human` (the default) when
88
89
  the human needs to act; see "Asking" in `skill://dispatch`. Comments are edited only by their author from the
@@ -99,7 +100,8 @@ dispatch_resolve_comment({ comment })
99
100
  8+ character id prefix is resolved against the owner's comments). It returns the owner details plus `comment`, and takes no reason —
100
101
  say what you did in a `reply_to` first if the thread needs it. The server lets any session or human resolve any open comment, so
101
102
  resolve only threads you opened or were asked to close; reopening a resolved thread is human-only (from the dashboard), though your
102
- reply to it reopens it. Asks are closed with `dispatch_resolve_ask` instead.
103
+ reply to it reopens it - except a decided suggestion's, which your reply joins and leaves accepted or rejected. A reply to a pending
104
+ suggestion whose text an edit removed lands as well. Asks are closed with `dispatch_resolve_ask` instead.
103
105
 
104
106
  An exact replacement for document text is a suggestion (`dispatch_suggest`), never a comment; a
105
107
  comment is for a question or a note the human answers in words. A human accepts a suggestion with