docs(core): move release process from CONTRIBUTING.md to AGENTS.md

[groksrc]

Summary

• Moves the ## Release Process section out of CONTRIBUTING.md (which is read by FOSS contributors, who don't cut releases) and into AGENTS.md under ## CODEBASE DEVELOPMENT, alongside the rest of the maintainer-facing operational guidance.
• Rewrites the content to point at the canonical just release / just beta recipes instead of bare git tag, and explicitly warns against tagging by hand.

Why

The previous CONTRIBUTING.md text documented stable releases as:

git tag v0.13.0 && git push origin v0.13.0

…and claimed "no manual version bumping required". Both are wrong. The just release recipe is the canonical command — it bumps __version__ in src/basic_memory/__init__.py and "version" in server.json (MCP registry metadata) before tagging, and runs lint + typecheck pre-flight.

A bare git tag leaves package metadata correct (uv-dynamic-versioning derives PyPI/Homebrew version from the tag) but basic-memory --version reports the previous release. That's what happened with v0.21.2 → had to re-cut as v0.21.3 today using the proper recipe.

AGENTS.md now:

• Documents just release vX.Y.Z / just beta vX.Y.Zb1 as the entry points
• Lists what the recipe does step by step
• Explicitly calls out the do-not-tag-by-hand trap with the v0.21.2 incident as context
• References .claude/commands/release/release.md for the full runbook including post-release tasks (docs site, basicmachines.co, MCP registry)

Test plan

• AGENTS.md renders correctly (markdown only, no broken refs)
• CONTRIBUTING.md still flows naturally — ## Release Process removed cleanly, ## Creating Issues now follows ## Testing Guidelines directly

🤖 Generated with Claude Code

[github-actions]

PR Review: docs(core): move release process from CONTRIBUTING.md to AGENTS.md

• Gather context and understand the request
• Read changed files (AGENTS.md, CONTRIBUTING.md)
• Apply team checklist
• Post review summary

---

This is a documentation-only PR. No code changes, so code-specific checklist items are N/A.

Team Checklist Results

Code Quality & Standards

• Follows Basic Memory's coding conventions in CLAUDE.md — docs-only, conventions N/A
• No commented-out code blocks — N/A, docs only
• CLAUDE.md/AGENTS.md updated ✅ — this IS the AGENTS.md update

Testing & Documentation

• Documentation updated — the primary purpose of this PR
• N/A — no new functions, tests, MCP tools, or coverage to check (docs-only change)

Security & Performance

• No hardcoded secrets or credentials
• No sensitive data in logs or commits

Compatibility

• No emojis or unicode in console/log output (docs use em-dashes, which is fine for markdown)

---

Review Summary

Verdict: ✅ Clean, well-motivated docs PR. Approved.

What's correct:

• The motivation is solid and concrete: the v0.21.2 → v0.21.3 re-cut incident caused by a bare git tag is exactly the kind of incident context that makes a warning stick.
• CONTRIBUTING.md is the right place for FOSS contributor onboarding; release mechanics belong in maintainer-facing AGENTS.md. The restructuring is correct.
• The new section in AGENTS.md (lines 256–279) is accurate, complete, and actionable:
  • Documents just release vX.Y.Z and just beta vX.Y.Zb1 as entry points
  • Lists what the recipe does step-by-step
  • Explicitly calls out the bare-tag trap with the real incident as context
  • References .claude/commands/release/release.md for the full runbook
• CONTRIBUTING.md still flows naturally — ## Creating Issues now follows ## Testing Guidelines directly with no awkward gap.

Minor observations (not blocking, PR is already merged):

• The hardcoded version example (v0.21.3) in the ### Release Process section will drift as new releases are cut. It's fine as a static illustration — just something to be aware of if the section is ever refreshed.
• The CONTRIBUTING.md test commands (just test-unit, just test-int) differ slightly from the canonical commands in AGENTS.md (just test-unit-sqlite, just test-unit-postgres). That's pre-existing drift unrelated to this PR, but worth a follow-up cleanup.

View job run