@sjawhar/pi-legion-envoy 0.8.0 → 0.8.1
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.
|
@@ -158,6 +158,15 @@ dispatch({
|
|
|
158
158
|
(`#N is not a dispatch thread`, `#N is closed; open a new thread`).
|
|
159
159
|
- Same decision → same thread. A genuinely new decision → a new thread, even if it came
|
|
160
160
|
up in the reply.
|
|
161
|
+
- **A follow-up supersedes the thread's earlier unanswered questions.** The dashboard
|
|
162
|
+
offers an answer only for the latest turn; earlier open questions read "superseded by a
|
|
163
|
+
later follow-up". If an earlier question still stands, restate it in the follow-up's
|
|
164
|
+
`ask` list. A follow-up with no `ask` list is one free-text question — the text under
|
|
165
|
+
its `## Question` — and the human answers it in prose.
|
|
166
|
+
- **Ask once.** An unanswered question is not a reason to post again. New facts that do
|
|
167
|
+
not change the decision go in a plain `gh issue comment` on the thread, not a new
|
|
168
|
+
`dispatch` call; a follow-up is for a changed question. A thread that fills with
|
|
169
|
+
restated asks is noise for the human and hides the decision it is waiting on.
|
|
161
170
|
- **Read a challenge as an answer.** "Why not the bot?" is not a request for more prose;
|
|
162
171
|
it is the human declining your framing. Say what you now know, then ask the narrowed
|
|
163
172
|
question with new options — unless the challenge itself decides ("Why not the bot? Just
|