@sjawhar/opencode-legion-envoy 0.36.2 → 0.37.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.
@@ -13572,6 +13572,7 @@ var ArtifactVersionEventPayloadSchema = object({
13572
13572
  diff: string2().optional()
13573
13573
  });
13574
13574
  var AskEventPayloadSchema = object({
13575
+ opened_event_id: number2().int().positive(),
13575
13576
  question: string2().optional(),
13576
13577
  options: array(object({ label: string2().optional() })).nullish(),
13577
13578
  answer: object({ selected: array(string2()).nullish(), text: string2().nullish() }).nullish(),
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/opencode-legion-envoy",
3
- "version": "0.36.2",
3
+ "version": "0.37.0",
4
4
  "type": "module",
5
5
  "main": "dist/src/server.js",
6
6
  "exports": {
@@ -104,8 +104,8 @@ dispatch_resolve_ask({
104
104
  })
105
105
  ```
106
106
  Use `retracted` when the question is obsolete and `resolved` when you found the answer. Include the
107
- reason because the question remains in its issue log and reply thread. Resolution is not an answer:
108
- it never records a human decision, and an answered ask cannot be resolved.
107
+ reason because the question remains in its Conversation card and reply thread. Resolution is not an
108
+ answer: it never records a human decision, and an answered ask cannot be resolved.
109
109
 
110
110
  An ask is a thread, not a dead end: a human can reply to it before or after answering, and you
111
111
  (the asker) can reply too — e.g. acknowledging a clarifying question, or following up after the