@sjawhar/pi-envoy 8.1.0 → 8.2.0

package/dist/envoy.js

@@ -29700,6 +29700,12 @@ var askEventPayloadFields = {
   question: exports_external.string().optional(),
   options: exports_external.array(exports_external.object({ label: exports_external.string().optional() })).optional(),
   answer: exports_external.object({ selected: exports_external.array(exports_external.string()).nullish(), text: exports_external.string().nullish() }).nullish(),
+  previous_answer: exports_external.object({
+    user: exports_external.string().optional(),
+    selected: exports_external.array(exports_external.string()).nullish(),
+    text: exports_external.string().nullish(),
+    at: exports_external.string().optional()
+  }).nullish(),
   anchor: exports_external.object({
     quote: exports_external.string().optional(),
     mark_id: exports_external.string().optional(),
@@ -31616,9 +31622,15 @@ function dispatchCompact(event, comment) {
       };
       break;
     }
-    case "ask.answered":
-      record2 = { ...record2, answer: askAnswerText(ask.data.answer) };
+    case "ask.answered": {
+      const previousAnswer = ask.data.previous_answer;
+      record2 = {
+        ...record2,
+        answer: askAnswerText(ask.data.answer),
+        ...previousAnswer === null || previousAnswer === undefined ? {} : { previous_answer: askAnswerText(previousAnswer) }
+      };
       break;
+    }
     case "ask.resolved": {
       const resolved = askResolutionText(ask.data.resolution);
       record2 = resolved === undefined ? record2 : { ...record2, resolved };
@@ -33908,8 +33920,10 @@ function eventHead(event) {
     case "ask.handed_back":
     case "ask.resolved":
       return textHead(event.payload.question);
-    case "ask.answered":
-      return `${textHead(event.payload.question)} -> ${textHead(askAnswerText(event.payload.answer))}`;
+    case "ask.answered": {
+      const previousAnswer = event.payload.previous_answer;
+      return `${textHead(event.payload.question)} -> ${textHead(askAnswerText(event.payload.answer))}${previousAnswer === undefined ? "" : ` (was: ${textHead(askAnswerText(previousAnswer))})`}`;
+    }
     case "comment.created":
     case "comment.answered":
     case "comment.anchor_refreshed":
@@ -33950,8 +33964,9 @@ function childrenSummary(issue2) {
   ].join(`
 `);
 }
-function askSummary({ ask, replies }, graph) {
+function askSummary({ ask, replies, answers }, graph) {
   const answer = ask.answer;
+  const earlierAnswers = answers.slice(0, -1);
   const chain = replies.flatMap((reply) => [
     `${reply.id} \xB7 ${actorText(reply.author)}`,
     `Body: ${reply.body}`
@@ -33968,6 +33983,10 @@ function askSummary({ ask, replies }, graph) {
       `- Selected: ${answer.selected.length === 0 ? "none" : answer.selected.join(", ")}`,
       ...answer.text === null ? [] : [`- Text: ${answer.text}`]
     ],
+    ...earlierAnswers.length === 0 ? [] : [
+      "Earlier answers:",
+      ...earlierAnswers.map((earlier) => `- ${earlier.at} \xB7 ${earlier.user} \xB7 ${askAnswerText(earlier)}`)
+    ],
     ...ask.resolution === undefined ? [] : [
       "Resolution:",
       `- By: ${ask.resolution.actor.id}`,

package/dist/skills/dispatch/SKILL.md

@@ -338,7 +338,7 @@ permission you already hold, an API that replaces the click. One ask per item, `
 when work is stopped on it; while it is open, keep working on everything that is not.
 
 Once an ask is open (who answers it, handing a human a to-do, editing, retracting or resolving it,
-answering a clarification, whose turn a reply gives), see
+answering a clarification, whose turn a reply gives, an answer the human changes), see
 [Asks after they open](skill://dispatch/references/asks.md).
 
 ## Architecture components

package/dist/skills/dispatch/references/asks.md

@@ -45,6 +45,9 @@ dispatch_edit_ask({
 At least one field besides `ask` is required. Use this only while the same decision remains open: it keeps the prior text in the event
 log and invalidates any answer draft against the prior `edited_at` revision, so the human sees the new wording and explicitly reconfirms.
 An answered or resolved ask cannot be edited. If the decision is moot or superseded, retract the old ask and open a new one.
+A human can change an answer they gave. The change arrives as another `ask.answered` frame whose
+`previous_answer` names the answer it replaced, through the same route the first answer took, and
+`dispatch_read` of the ask lists every earlier answer. Act on the newest answer.
 
 An ask that lives as an `ask` block in a document keeps its question and options in the block, and `dispatch_edit_ask` writes the
 block along with the row, so the edit stands and the document reads the same. It changes only the fields you name: pass `urgency`

package/dist/skills/dispatch/references/document-edits.md

@@ -197,6 +197,6 @@ an existing paragraph is the question that should become a decision.
 
 An ask block has two ids: the block id, shown as `:::ask{#<id> …}` in the rendered document and
 taken bare by `move`/`delete` in `block` (the `block:<id>` form is only for `before`/`after`
-anchors), and the ask id, which `dispatch_open_asks`, the dashboard's `?ask=` link, `dispatch_read`
-and `dispatch_comment({ reply_to_ask })` use. They differ; `dispatch://KEY/ask/<block-id>` answers
-`not found`.
+anchors), and the ask id, which `dispatch_open_asks`, the dashboard's ask links (`/asks/<id>`,
+`?ask=`), `dispatch_read` and `dispatch_comment({ reply_to_ask })` use. They differ;
+`dispatch://KEY/ask/<block-id>` answers `not found`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/pi-envoy",
-  "version": "8.1.0",
+  "version": "8.2.0",
   "license": "Apache-2.0",
   "type": "module",
   "omp": {