chore: publish queue — version bumps + sandbox/swarm release workflows

[cobusgreyling]

Summary

Closes the publish queue attention items from triage (2026-07-29) and refreshes release prep for #332.

Version bumps

Package	From	To	Why
loop-audit	1.7.0	1.8.0	--auto-fix, memory signals (#358/#359)
loop-init	1.5.0	1.6.0	MiniMax provider (#418) + --with-memory (#359)
loop-mcp-server	1.1.0	1.2.0	loop_audit_score, loop_check_breaker (#360)
loop-worktree	—	1.3.0	Already on main (#407) — tag only
loop-sandbox	—	1.0.0	First publish + release workflow
loop-swarm	—	1.0.0	First publish + release workflow

Also

• Refresh RELEASE_NOTES_DRAFT.md + changelog-drafter-state.md for window 2026-07-16 → 2026-07-29 (supersedes stale chore: refresh RELEASE_NOTES_DRAFT for release prep (#332) #365 draft content)
• Document sandbox/swarm in docs/RELEASE.md

Not in this PR (human gate)

• No tags / npm publishes — after merge, tag in the order listed in RELEASE_NOTES_DRAFT.md
• No Discussion post / close of Release prep — week of 2026-07-20 #332

Suggested tags after merge

git tag loop-worktree-v1.3.0 && git push origin loop-worktree-v1.3.0
git tag loop-audit-v1.8.0 && git push origin loop-audit-v1.8.0
git tag loop-init-v1.6.0 && git push origin loop-init-v1.6.0
git tag loop-mcp-server-v1.2.0 && git push origin loop-mcp-server-v1.2.0
git tag loop-sandbox-v1.0.0 && git push origin loop-sandbox-v1.0.0
# after sandbox is on npm:
git tag loop-swarm-v1.0.0 && git push origin loop-swarm-v1.0.0

Test plan

• CI green on this PR
• After merge + tags: npm view @cobusgreyling/<pkg> version matches table
• Human review of RELEASE_NOTES_DRAFT.md before Discussion

Related: #332, supersedes draft PR #365 content

[github-actions]

Thanks @cobusgreyling 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

[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 for a fleet — npx @cobusgreyling/loop-init . --with-fleet
• 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}