gosalyn: C2-06 brief owns the setup sheet's reply limits paragraph, which says 3 ideas of up to 120 characters and drops the lower-limits offer, and the tests paragraph is rewrapped (webby-0139 N1, N2, Q219)

docs/plans/2026-10-20_case2-rows.md

@@ -383,6 +383,8 @@ every agent-to-human message in a library business.
   web verbs (`:1516`, `:1521`).
 - `packages/bus/src/web.mjs`, only if the page store needs the fetched text passed out.
 - Tests in `packages/library/tests` and `packages/bus/tests`.
+- `docs/case2/SETUP-SHEET.md`, the reply limits paragraph only (`:114-117` at aca16404c), so the sheet and
+  the guard land together (webby-0139 N1).
 
 ### What ships
 
@@ -392,11 +394,14 @@ The guard as design 5.2 sets it out: the JSON body, the M5 limits, the checks an
 whether to run. The page store keeps the last 20 broker fetches per session, 200 KB each, in memory,
 dropped when the session ends.
 
-The `idea` limits are 3 items per reply and 120 characters per item (Q219, mos-1299).
+The `idea` limits are 3 items per reply and 120 characters per item (Q219, mos-1299). The setup sheet's
+limits paragraph says at most 3 ideas of up to 120 characters each and drops "You or Jason can ask for
+lower limits", since Jason has set them.
 
 Tests: one pass and one refusal for each check in M5 and 5.2, each limit refused one past its boundary
-and accepted at it, so 4 ideas and a 121-character idea refuse. Each goes through the runner's RESULT path and through `send_message`, and once
-with a non-creative sender in a library business. The `messages` count is unchanged on each refusal.
+and accepted at it, so 4 ideas and a 121-character idea refuse. Each goes through the runner's RESULT
+path and through `send_message`, and once with a non-creative sender in a library business. The
+`messages` count is unchanged on each refusal.
 
 ### Out of scope