chore: refresh RELEASE_NOTES_DRAFT for release prep (#332)

[cobusgreyling]

Summary

Updates release prep for #332 (changelog-drafter L1 dogfood).

• Refreshes RELEASE_NOTES_DRAFT.md for window 2026-07-16 → 2026-07-23
• Records published work (loop-cost 1.2.0, loop-context 1.5.0)
• Surfaces unpublished main-branch features that need version bumps:
  • loop-audit → 1.8.0 (feat(loop-audit): add --auto-fix command to self-heal repository structures #358/feat: implement memory-engineering bridge (--with-memory flag and readiness signals) #359)
  • loop-init → 1.6.0 (feat: implement memory-engineering bridge (--with-memory flag and readiness signals) #359)
  • loop-mcp-server → 1.2.0 (feat: expose loop-audit and circuit breaker over MCP #360)
• Adds changelog-drafter-state.md with scan window + human publish gate

Not in this PR

• No npm tags or publishes (human gate)
• No package.json version bumps (separate version PR recommended)

Human next steps

1. Review the draft wording
2. Open version-bump PR for the three packages above
3. Tag + publish, then Discussion + close Release prep — week of 2026-07-20 #332

Related: #332

Checklist

• Draft PR only
• Report-only — no tags, no Discussions post, no auto-publish

[github-actions]

Loop Readiness Audit

Score: 100/100 (L3)

Strong loop readiness — good candidate for L3 with explicit gates.

Top suggestions

• Loop Ready 80+: version this loop's memory — npx @cobusgreyling/loop-init . --with-memory
• Loop Ready 80+: version this loop as a harness — npx @cobusgreyling/loop-init . --with-foundry · showcase https://github.com/cobusgreyling/harness-foundry/blob/main/docs/showcase.md
• Scaffold a harness: npx @cobusgreyling/loop-init . --with-foundry (or npx @cobusgreyling/harness-foundry init --from loop-engineering:daily-triage)
• Scaffold memory tiers: npx @cobusgreyling/loop-init . --with-memory

_{Posted by audit.yml · loop-audit docs}