Add loop-init validation checklist (#231)

[k-anushka14]

Summary

Adds a loop-init validation checklist (docs/loop-init-validation.md) tracking pattern × --tool Loop Ready scores, per #231.

Changes

• New pattern or starter
• Doc / example improvement
• Tool change (loop-audit)
• Story

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)

Validated one row by running loop-init in a fresh git repo:

​ mkdir C:\Temp\loop-init-test cd C:\Temp\loop-init-test git init npx @cobusgreyling/loop-init . --pattern daily-triage --tool claude ​

Output:
​ ✓ Loop Ready: 100/100 (L3) ​

Files created: .claude/skills/loop-triage/, .claude/agents/loop-verifier.md, STATE.md, LOOP.md, loop-budget.md, loop-run-log.md, loop-constraints.md, .claude/skills/loop-budget/SKILL.md, .claude/skills/loop-constraints/SKILL.md, AGENTS.md

Closes #231

[github-actions]

Thanks @k-anushka14 for contributing a docs improvement — 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