A reviewer's changes requested starts the builder's follow-up on its own, bounded to three rounds before a person is asked #1161

Seen on the three realtor apps tonight (trevato/speed-to-lead, listing-launch, deal-clock, autonomy on): Mason opens the pull, Sentinel reviews with changes requested, and then nothing happens until a person comments. Twice in a row the follow-up only started on the owner's steward's nudge. The review-to-fix loop is the crew's own, and a reviewer's "changes requested" is the clearest signal the forge has; it should start the builder's follow-up run on its own, in autonomous mode, with the review as the brief.

Done looks like:

• [ ] In autonomous mode, a crew reviewer's changes_requested on a crew pull starts the builder's feedback run within the next tick, with the review body as what to do; assisted does the same; off waits for a person.
• [ ] A loop is bounded: after three review rounds on one pull without an approval, the pull is handed to a person with the three reviews summarised in one card (not parked, not closed).
• [ ] An approval with a green check lands the pull in autonomous mode (as it does today) and says so.
• [ ] Tests in test/crew-loop.test.ts: review → follow-up without a comment; the third round hands over; off waits.

Files I expect: src/crew/dispatch.ts (the review event), src/crew/review.ts, src/crew/autonomy.ts.