docs: add Cursor CI Sweeper example (#220)

[shixi-li]

Summary

Add a Cursor-specific CI Sweeper example that starts report-only and maps safe fix attempts to Automations, project skills/rules, isolated worktrees, and an independent verifier.

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)

The example:

• adds a week-one report-only Automation prompt with evidence-based failure classification;
• maps ci-triage, minimal-fix, loop-verifier, and ci-sweeper-state.md into Cursor project paths;
• distinguishes Cursor's managed Automations and local /loop skill from repository-owned scheduling;
• treats prompts and .cursor/rules as advisory, with tool and credential scopes as the enforceable boundary;
• requires loop-worktree isolation and a separate verifier for later fix attempts; and
• forbids CI retries, comments, auto-merge, and unattended fixes in week one.

The Cursor index and pattern-coverage matrix now link the example.

Checklist (from CONTRIBUTING)

• Links work from README, patterns/README, starters/README, docs/index
• No secrets, tokens, internal company URLs
• Safety-sensitive guidance references docs/safety.md and includes explicit human gates
• Ran node tools/loop-audit/dist/cli.js . and addressed findings

Testing / Dogfood

• bash scripts/ci-validate-gates.sh
• bash scripts/ci-audit-gates.sh
• bash scripts/before-after-demo.sh
• node tools/loop-audit/dist/cli.js . --json — 100/100, L3
• git diff --check
• Manually checked local links and current official Cursor Automations documentation

Screenshots / Examples

Not applicable; this is a Markdown-only documentation change. The new page contains the copy-paste report-only prompt and an example state entry.

Closes #220

[github-actions]

Thanks @shixi-li for contributing a tool example — 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