[AAASM-3849] 📝 (docs): Sync version refs to rc.2 (matrix + labels + Node @rc)#47
Conversation
Add beta.3, beta.4, rc.1 and rc.2 rows to compatibility.toml and mark rc.2 as the current product line (demoting the stale beta.2 "current" label to supported). Regenerate docs/src/compatibility.md and refresh the "Last verified" date. Closes AAASM-3849 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019mSz31RysZF6DYToUoBWLf
The product line is now v0.0.1-rc, so the status map's maturity label and every area row that read "alpha"/"v0.0.1-alpha" now read "release candidate"/"v0.0.1-rc". Refresh the "Last reviewed" footer. Closes AAASM-3850 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019mSz31RysZF6DYToUoBWLf
The hub landing page described the project as "in beta (v0.0.1-beta)"; the current line is the release candidate v0.0.1-rc. Refresh the "Last reviewed" footer. Closes AAASM-3850 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019mSz31RysZF6DYToUoBWLf
The release-candidate line publishes under npm's `rc` dist-tag (@agent-assembly/sdk@rc resolves to 0.0.1-rc.2). Update the install one-liner (manifest + regenerated requirements table), the quickstart pnpm command, the npm version badges, and the dist-tag prose from @beta to @rc. (Python --pre and Go @latest already track rc.2.) Closes AAASM-3851 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019mSz31RysZF6DYToUoBWLf
🤖 Claude Code — PR ReviewVerdict: ✅ APPROVE Scope (AAASM-3849 / 3850 / 3851): Complete. Compatibility matrix regenerated through rc.2 with rc.2 marked current (stale beta.2 "current" demoted to supported); maturity labels updated alpha→release candidate across No side-effects: Docs-only. Note for tracking: the matrix scope listed beta.3/beta.4/rc.1/rc.2 — a CI: Green. |
|



Description
Sync the documentation hub's version references to the current rc.2 release
line (PyPI
0.0.1rc2, npm@rc→0.0.1-rc.2, go-sdkv0.0.1-rc.2). Threerelated doc bugs were combined into one PR because they edit overlapping files
(
compatibility.toml/docs/src/compatibility.md/docs/src/README.md):beta.3,beta.4,rc.1,rc.2rows tocompatibility.tomland markedrc.2 as current (removing the stale
beta.2"current" mislabel),regenerated
compatibility.md, and refreshed the "Last verified" date.release candidate: the
source-of-truth.mdmaturity label + area map(
v0.0.1-alpha→v0.0.1-rc) and the hubREADME.mdprose("in beta (
v0.0.1-beta)" → "in release candidate (v0.0.1-rc)").@betato the@rcnpm dist-tag (install one-liners, quickstart
pnpm add, npm version badges,and dist-tag prose). Python
--preand Go@latestalready track rc.2.Type of Change
Related Issues
Documentation Checklist
cd docs && mdbook buildpasses locally with no warningsdocs/src/SUMMARY.md(no new pages added)docs/scripts/generate_compatibility.py --checkpasses (page matches manifest)🤖 Generated with Claude Code