Add Amazon Q Developer CLI appendix to primitives matrix (#227)

[k-anushka14]

Summary

Adds an Amazon Q Developer CLI appendix to docs/primitives-matrix.md, mapping scheduling, context/rules, state, and maker/checker primitives, per #227.

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)

New appendix follows the same structure as the existing Gemini CLI / Zed appendices: a primitive-mapping table, a minimal transfer recipe, a custom-agent config example, and a copy-paste week-one Daily Triage prompt (report-only, --no-interactive). Placed after the Gemini CLI appendix, grouping it with the other terminal-native CLI tools (Aider, Gemini CLI, Amazon Q).

Included an explicit "Honest gaps" row per the issue's acceptance criteria: no first-class scheduler, no native maker/checker split, no dedicated state-file convention — these are manual conventions layered on top of q chat.

Also noted a caution around workspace .amazonq/mcp.json files from untrusted repos in the Connectors row, since auto-loaded MCP configs are a known trust gap in this class of tool — flagging it, not treating it as safety-doc content, since it's a usage caveat rather than a formal safety/gating policy.

Closes #227

[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

[cobusgreyling]

Landed via maintainer rebase in #265 (Amazon Q appendix) — #249 had already merged the Codeium appendix into the same region, causing a conflict. Content credited to @k-anushka14; official doc link corrected to the AWS Q Developer CLI docs. Closes #227.