gosalyn: C2-06 brief takes Jason's idea caps, 3 items of 120 characters per reply, tested one past each boundary, and the idea-text residual line reads 360 characters closed in Q219 (mos-1299, design 2852348d2)

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

@@ -392,14 +392,16 @@ 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).
+
 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. Each goes through the runner's RESULT path and through `send_message`, and once
+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
 
 The runner retry and the runner's notices (C2-07). The Console's rendering (C2-10b). Any classifier of
-prose. The idea-text residual is Jason's or Melanie's to accept (design 5.1, 10 step 8).
+prose. The idea-text residual is 360 characters per reply, closed by Jason in Q219 (design 5.1, 10 step 8).
 
 ### Gate