fix: raise Greptile re-trigger cap from 3 to 50 per PR

[carlos-alm]

Summary

• The /sweep skill's re-trigger loop (.claude/skills/sweep/SKILL.md, Step 2h) previously capped Greptile/Claude re-review rounds at 3 before forcing a PR into needs-human-review status.
• That cap of 3 was set by a prior autonomous Claude Code session without real human sign-off — it only carried the repo owner's name in git history because commits/API calls run under their authenticated gh CLI identity, not because it reflects an actual reviewed decision.
• The repo owner has now explicitly requested a budget of 50 rounds instead, since Greptile findings can legitimately require several genuine fix-and-retrigger rounds, and a cap of 3 was flagging PRs as needing human review while real, actionable bugs were still being found and fixed.

Change

Single-line change in .claude/skills/sweep/SKILL.md:

- 4. **Repeat this loop for a maximum of 3 rounds.** If after 3 rounds there are still actionable comments, mark the PR as "needs human review" in the result.
+ 4. **Repeat this loop for a maximum of 50 rounds.** If after 50 rounds there are still actionable comments, mark the PR as "needs human review" in the result.

No other content in the file was touched.

Test plan

• npm run lint passes clean on the changed file
• Confirmed this is the only occurrence of the round/trigger cap in the file (grepped for "round"/"cap"/"trigger" near a literal "3")

[greptile-apps]

Greptile Summary

Updates the sweep workflow’s Greptile re-trigger limit from 3 to 50 and consistently adjusts the associated stop conditions, status reporting, and final-check guidance.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
.claude/skills/sweep/SKILL.md	Consistently raises all Greptile re-trigger cap references from 3 to 50 without changing the surrounding workflow.

_{Reviews (2): Last reviewed commit: "fix: resolve merge conflicts with main" | Re-trigger Greptile}