spec: nudge loop guard decided — 3 nudges per expectation with no new content, then summarize to owner (#4)

CHATROOM_SPEC.md

@@ -84,6 +84,7 @@ Jev classifies and scores; it isn't an agent. The harness owns the ledger and th
 - **Check:** on each new event and on a short timer, Jev scores open expectations against the room log (met, missed, or pending, with confidence).
 - **Trigger on a miss:** the harness hands the verdict to the responsible crow as a `nudge` trigger. The crow's model decides how to proceed.
 - **Budget:** each nudge counts against the nest's exchange budget. When the budget runs out, open expectations go to the owner as a summary instead of more nudges.
+- **Nudge loop guard** [decided 2026-10-27]: **three loops max.** When a crow has received three nudges on one expectation with no new content or response data from it in between, the harness stops nudging and sends the open expectation to the owner in the summary. Three is a per-expectation constant in `guardrails.go`, counted by the harness, so the guard holds even if Jev keeps calling the expectation missed.
 
 Initial checks (from testing): promise kept, rounds completed, turn order (debate only), single owner, claims sourced, correction handled once, role adherence, requester gets an answer.