@sjawhar/pi-legion-envoy 0.36.2 → 0.37.1

package/dist/envoy.js

@@ -29669,6 +29669,7 @@ var ArtifactVersionEventPayloadSchema = object({
   diff: string2().optional()
 });
 var AskEventPayloadSchema = object({
+  opened_event_id: number2().int().positive(),
   question: string2().optional(),
   options: array(object({ label: string2().optional() })).nullish(),
   answer: object({ selected: array(string2()).nullish(), text: string2().nullish() }).nullish(),

package/dist/legion.js

@@ -29667,6 +29667,7 @@ var ArtifactVersionEventPayloadSchema = object({
   diff: string2().optional()
 });
 var AskEventPayloadSchema = object({
+  opened_event_id: number2().int().positive(),
   question: string2().optional(),
   options: array(object({ label: string2().optional() })).nullish(),
   answer: object({ selected: array(string2()).nullish(), text: string2().nullish() }).nullish(),

package/dist/skills/dispatch/SKILL.md

@@ -104,8 +104,8 @@ dispatch_resolve_ask({
 })
 ```
 Use `retracted` when the question is obsolete and `resolved` when you found the answer. Include the
-reason because the question remains in its issue log and reply thread. Resolution is not an answer:
-it never records a human decision, and an answered ask cannot be resolved.
+reason because the question remains in its Conversation card and reply thread. Resolution is not an
+answer: it never records a human decision, and an answered ask cannot be resolved.
 
 An ask is a thread, not a dead end: a human can reply to it before or after answering, and you
 (the asker) can reply too — e.g. acknowledging a clarifying question, or following up after the
@@ -141,11 +141,16 @@ type EditOp = {
 };
 ```
 
-Target edits by quote: `replace` requires `find` and `with`; `delete` requires `find`; `insert`
-requires `markdown` and exactly one of `after` or `before`. An insert anchor is a quote,
-`"start"`, `"end"`, or `"heading:Title"`. Use zero-based `occurrence` for a repeated `find`.
-When a decision lands, pass `summary` to name the resulting version. Never paste progress into a
-message.
+Target `replace` and `delete` by the document's plain text: inline-code and link text match
+without Markdown syntax, and a table-cell anchor is its cell text. `replace` requires `find` and
+`with`; `delete` requires `find`; `insert` requires `markdown` and exactly one of `after` or
+`before`. An insert anchor is a quote, `"start"`, `"end"`, or `"heading:Title"`. Every insert
+creates a sibling block before or after the quote or heading's enclosing document block; `"start"`
+and `"end"` select the document edges. At a table-cell quote, pipe-table body-row fragments extend
+that table before or after the matched row; omit table header and delimiter rows, and do not exceed
+the table width. Use `replace` for inline continuation. Use zero-based `occurrence` for a repeated
+target. When a decision lands, pass `summary` to name the resulting version. Never paste progress
+into a message.
 
 ## Comments and suggestions
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/pi-legion-envoy",
-  "version": "0.36.2",
+  "version": "0.37.1",
   "type": "module",
   "omp": {
     "extensions": [