plans: row 143 round 2 adds the chief-of-staff relay bullet, and acceptance 314 needs row 128's thread (#1637)

Dewey's F5 on comment 28853: nothing tells the chief of staff to relay a
BLOCK or an accept in_reply_to the message that carried it, and the bus
refuses a relay without that link. Row 143's brief now owns one bullet in
roles/chief-of-staff.md.

Dewey's F1: the assistant is the threaded instance, so a plain talk is
refused thread-required-use-thread-send, and no CLI code creates a project
or a thread before row 128. Acceptance 314 adds row 128 to its
prerequisites and a step that creates and opens Jason's assistant thread
in the project.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

docs/acceptance/314.md

@@ -1,8 +1,16 @@
 # Acceptance run for task 314 (Q167)
 
-Jason runs this inside the Stack once rows 135 to 143 and 147 to 149 are
-live. It checks PRD version 1.5: one need goes from his spec to a landed
-commit, and only hard waits reach his inbox.
+Jason runs this inside the Stack once rows 128, 135 to 143 and 147 to 149
+are live. It checks PRD version 1.5: one need goes from his spec to a
+landed commit, and only hard waits reach his inbox.
+
+Row 128 is there because the assistant is the business's threaded
+instance. The bus refuses a plain `message.send` to it with
+`thread-required-use-thread-send` (`packages/bus/src/broker.mjs:281` at
+c550efa27), and before row 128
+no CLI or Console code creates a project or a thread. Row 143's summary
+also lands only in Jason's most recently opened assistant thread in the
+spec's project, so without one, step 9 fails.
 
 `<business>` is the business the bus host runs. `<project>` is the
 project the need belongs to, `stack` for this run. Every command runs on
@@ -34,6 +42,12 @@ bus schema.
    Pass: `check` reports the layout valid. The first commit's author is
    Jason. (REQ-PROJ-1)
 
+   Then, with row 128's commands (`docs/TOOLS.md` names them once that
+   row lands), create a bus project named for `<project>` with repo
+   `<project>`, create an assistant thread in it, and open that thread.
+   Steps 3, 6 and 9 use this thread. Pass: the thread list shows the
+   thread under the project, owned by Jason.
+
 2. Open the spec in the Console editor and write it:
 
    > North star: anyone can tell what is running in one command.
@@ -46,11 +60,10 @@ bus schema.
    tab, which still holds the old commit: the save is refused and writes
    nothing. (REQ-PROJ-2, REQ-PROJ-3)
 
-3. Tell the assistant about the need:
+3. Tell the assistant about the need, in the thread from step 1, with
+   row 128's talk command:
 
-   ```
-   mosaic talk assistant "New need: the mosaic version command in spec/north-star.md. Start it."
-   ```
+   > New need: the mosaic version command in spec/north-star.md. Start it.
 
    Pass: `talk` prints only the assistant's reply to this message.
 
@@ -86,13 +99,10 @@ bus schema.
      landed commit, and the commit is on the working repository's `main`
      (REQ-LAND-1).
 
-6. Check the inbox, then ask for one hard wait on purpose:
-
-   ```
-   mosaic inbox
-   mosaic talk assistant "Open a new account for the project on an outside service."
-   mosaic inbox
-   ```
+6. Check the inbox, then ask for one hard wait on purpose. Run
+   `mosaic inbox`, tell the assistant in the step 1 thread "Open a new
+   account for the project on an outside service.", then run
+   `mosaic inbox` again.
 
    Pass: the first `inbox` is empty, so nothing from steps 3 to 5 reached
    Jason. After the request, the inbox holds one decision for
@@ -139,7 +149,7 @@ bus schema.
 
    Pass: pm or the CTO answers with a BLOCK naming the conflict, the
    commit stays, and the assistant tells Jason about the block in its own
-   words. The assistant's message doesn't quote the chief of staff's text.
+   words, in the step 1 thread. The assistant's message doesn't quote the chief of staff's text.
    (REQ-PROJ-4, REQ-ASSIST-3) Then revert the spec in the editor with a
    new commit.
 

docs/plans/2026-10-15_q167-rows-r3.md

@@ -602,6 +602,11 @@ from the assistant, mostly repeats.
 ### Files owned
 
 - `roles/assistant.md`, `roles/pm.md`, `roles/cto.md`, contract text
+- `roles/chief-of-staff.md`, one bullet (added in round 2, Dewey's F5 on
+  comment 28853): the chief relays a BLOCK or an accept to the assistant
+  as a reply `in_reply_to` the message that carried it, because the bus
+  refuses a relay without that link. Row 149 also edits this file, so
+  whichever row lands second rebases.
 - `packages/bus/src/broker.mjs` and `packages/business/src/vocabulary.mjs`
   for the notice and the BLOCK class, if needed
 - tests and READMEs
@@ -620,7 +625,8 @@ from the assistant, mostly repeats.
   with git outside the Console sends none; PRD 1.5 REQ-PROJ-4 says so, and
   covering those commits is a later row.
 - Tests: one notice per spec commit; no notice for an agent's record
-  commit; a BLOCK reaches the assistant; a contract text test.
+  commit; a BLOCK reaches the assistant; a contract text test, which
+  covers the chief-of-staff bullet too.
 
 ### Out of scope