docs(stories): add CI Sweeper failure story

[DavidReque]

Summary

Adds an honest failure story for the CI Sweeper pattern, demonstrating an infinite fix loop triggered by flaky E2E tests, resolving issue #199.

Changes

• New pattern or starter (followed templates/pattern-template.md + updated registry.yaml)
• Doc / example improvement
• Tool change (loop-audit)
• Story (includes real failure or surprise + lesson)

Checklist (from CONTRIBUTING)

• All required sections present for patterns
• Links work from README, patterns/README, starters/README, docs/index
• No secrets, tokens, internal company URLs
• STATE.md* examples use .example suffix
• Safety-related content references docs/safety.md
• Ran node tools/loop-audit/dist/cli.js . (or on the starter) and addressed findings

Testing / Dogfood

• loop-audit passes on affected starters or this repo
• Manual review of generated state / skill output

Screenshots / Examples (if UI or command output)

N/A - Text only failure story.

---

This template enforces the high bar this reference is known for.

[github-actions]

Thanks @DavidReque for contributing a production story — visible, reviewable PRs like this grow the reference for everyone.

What happens next

• Maintainer aims for same-day review on story, adopter, and scoped docs/example PRs (CONTRIBUTING.md).
• good first issue PRs: comment on the linked issue so we can assign and close on merge.

More ways to help

• Contributor quickstart + open issues
• Good first issue backlog

— loop-engineering maintainers