From 3648c782866bd54c4d1ddcdfeb3d0eafa018e617 Mon Sep 17 00:00:00 2001 From: Bryan Van Deusen Date: Fri, 9 Oct 2026 14:32:05 -0400 Subject: [PATCH] fix(500): the completion slice says "two questions", not "two tests" - the domain guard reads the word as software (#5493) Co-Authored-By: Claude Opus 5.5 --- src/scribe/services/reply_shapes.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/scribe/services/reply_shapes.py b/src/scribe/services/reply_shapes.py index a1ef77b4..4e2df4c9 100644 --- a/src/scribe/services/reply_shapes.py +++ b/src/scribe/services/reply_shapes.py @@ -121,8 +121,8 @@ A completion report, from the `placement` the closing call returned: not the steps behind them; those belong in the task's log. - **How / why** — only the decisions worth knowing, and how it was verified. Anything \ that could not be verified is said here rather than left to read as passed. -- **Needs you** — an action, an approval, a decision, or "nothing". It takes two tests: \ -is it theirs to decide, and is work waiting on it? A question you could settle by \ +- **Needs you** — an action, an approval, a decision, or "nothing". It has to answer two \ +questions yes: is it theirs to decide, and is work waiting on it? A question you could settle by \ reading or measuring something is work not yet done — settle it, say which way you went, \ and leave them free to overrule. - **Next** — from `placement.next`, or say the plan is finished. An offer to fix \