docs: update release notes draft with post-Jul-7 commits (#192-#207)

[nivinlabs]

Summary

Updates RELEASE_NOTES_DRAFT.md to include the 6 commits merged after the draft was last updated on July 7, 2026.

Added to Highlights

• feat(loop-worktree): npm publish + macOS gc path fix #204 — loop-worktree npm publish + macOS gc fix
• feat(docs): star-history page with GitHub token UI #193, feat(docs): star-history page — star-history.com look & feel #205 — Star-history docs page with GitHub token UI, later redesigned to match star-history.com

Added to Housekeeping

• chore: update star-history chart 2026-07-07 #192 — Star-history chart SVGs refreshed
• docs: reflect loop-mcp-server npm publish in QUICKSTART and README #194 — Good-first issue count refreshed to 17
• chore(loop): daily triage STATE.md 2026-07-07 #207 — Daily triage STATE.md + run log update (automated)

Other changes

• Window dates updated: 2026-07-06 → 2026-07-22
• Publish checklist and suggested publish steps sections left unchanged

Only file changed: RELEASE_NOTES_DRAFT.md (docs-only).

[cobusgreyling]

Automated fix: resolved merge conflicts and rebased onto main.

[cobusgreyling]

Hold — do not merge as-is

The narrative highlights are useful, but the npm publish checklist is stale relative to main today and would mislead release prep (#332):

Checklist says	On main now
loop-audit 1.5.3	1.7.0
loop-init 1.3.3	1.5.0
loop-worktree 1.1.0 → 1.2.0 publish	already 1.2.0
loop-gate first publish	may already be published — please re-check

Also missing recent ships that release notes should mention if the window goes to 2026-07-22: goal-init 1.0.0, readiness-core 1.0.0, loop-context 1.4.0 (+ #337 circuit breaker), loop-cost 1.1.0 / pending cache work versioning gap after #346/#347.

Suggested path

1. Rebase onto latest main
2. Refresh the publish table + highlights to match current package.json / tags
3. Coordinate scope with #332 so we do not maintain two competing release-note sources
4. Keep RELEASE_NOTES_DRAFT.md clearly "draft for human edit" (status line is fine)

Happy to re-review after the version table is current.

[cobusgreyling]

Hold — npm publish checklist is stale (loop-audit listed 1.5.3 vs 1.7.0 on main; loop-init 1.3.3 vs 1.5.0; loop-worktree already 1.2.0). Please rebase, refresh the publish table against current package.json/tags, and coordinate with #332 before merge.

[cobusgreyling]

Superseded by #352 — refreshed RELEASE_NOTES_DRAFT.md with an accurate npm publish checklist (loop-cost 1.2.0, loop-context 1.5.0, and current live versions for audit/init/worktree/gate/goal-init/readiness-core).

Thanks for the earlier draft narrative; highlights were folded into the new notes where still relevant. Please re-open a PR against the updated draft if you want to add more window history.