docs: add Cline appendix to primitives matrix (#147)

[shixi-li]

Summary

Add a Cline appendix to docs/primitives-matrix.md so Cline users can map the repository's loop primitives across the editor, CLI/SDK, and Kanban surfaces without assuming capabilities that are not first-class everywhere.

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 appendix:

• maps scheduling, skills/rules, repository state, maker/checker separation, and MCP configuration;
• distinguishes editor-extension capabilities from CLI/SDK/Kanban scheduling and persistent teams;
• calls out missing native STATE.md, machine-local team state, and approval-boundary gaps;
• adds a copy-paste, report-only week-one Daily Triage command; and
• adds an explicit human gate and independent-checker guidance for L2+ work.

Checklist (from CONTRIBUTING)

• Links work from README, patterns/README, starters/README, docs/index
• No secrets, tokens, internal company URLs
• Safety-sensitive guidance includes an explicit human gate and least-privilege tool scope
• 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 every capability claim and acceptance row against current official Cline documentation

Screenshots / Examples

Not applicable; this is a Markdown-only documentation change. The new appendix includes the copy-paste report-only command.

Closes #147

[github-actions]

Thanks @shixi-li 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