[AAASM-3762] 🔖 (release): node-sdk v0.0.1-rc.1

[Chisanan232]

Target

• Task summary:

  Release-intent PR for node-sdk @agent-assembly/sdk@0.0.1-rc.1. Bumps the local-dev package.json version 0.0.1-beta.5 → 0.0.1-rc.1, moving from the beta line onto the first release-candidate. This is PREP ONLY — it does not tag, publish, or trigger any release. After this merges and the owner gives the go, the operator dispatches release-node.yml (see publish note below).

  The npm publish version is supplied at release time via release-node.yml's npm_version dispatch input (npm_version=0.0.1-rc.1); the package.json version field is local-dev metadata only (matching the established convention from the beta.4 / beta.5 bump commits).

• Task tickets:

  • Task ID: AAASM-3762.
  • Mirrors the prior beta.5 release-intent PR [AAASM-3707] 🔖 (release): node-sdk v0.0.1-beta.5 #191 (AAASM-3707).

• Key point change (optional):

  Root package.json "version" 0.0.1-beta.5 → 0.0.1-rc.1, plus the user-facing SDK version references in the docs/examples (install commands + "version …" prose). The 4 @agent-assembly/runtime-* sub-packages and the root optionalDependencies (workspace:*) are intentionally not touched — release-node.yml's "Bump versions across the 5 packages" step rewrites all of them to the dispatch npm_version at publish time. No pnpm-lock.yaml change is needed — the lockfile does not pin the root package's own version. The Docusaurus frozen snapshot under website/versioned_docs/version-0.0.1-beta.5/ and the channel/version registries (website/versions.json, website/versionChannels.json) are left untouched — they are the historical beta.5 release record, managed by the release-cut workflow.

Effecting Scope

• Action Types:

  • 🚀 Release

• Scopes:

  • 🚀 Building
    • 📦 Project configurations
  • 📝 Documentation

• Additional description:

  Release-candidate bump from the beta line. master already carries the merged aa-ffi pin for v0.0.1-rc.1 (🤖 (aa-ffi-node): Bump agent-assembly git pins to v0.0.1-rc.1 #196), so the native binding source is aligned with this target.

Description

• Bump root package.json version 0.0.1-beta.5 → 0.0.1-rc.1.
• Update user-facing SDK version references from 0.0.1-beta.5 → 0.0.1-rc.1 in the quick-start install command and the eight example pages (docs/02-quick-start/, docs/09-examples/*).

---

Release-intent — publish after merge + owner go. Do not merge this PR before the owner approves the release. After merge, the operator publishes via release-node.yml workflow_dispatch with npm_version=0.0.1-rc.1. This PR itself does not tag, publish, or trigger any workflow. Sub-packages and the lockfile are intentionally untouched — the release workflow rewrites them at publish time.

Closes AAASM-3762

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[Chisanan232]

🔍 Code Review — Claude Code

Release-intent (prep-only) bump → v0.0.1-rc.1 · ticket AAASM-3762

• CI: ✅ 18 pass, 0 fails.
• Scope: ✅ package.json 0.0.1-beta.5 → 0.0.1-rc.1 + 8 doc version refs — mirrors [AAASM-3707] 🔖 (release): node-sdk v0.0.1-beta.5 #191 exactly. The 4 @agent-assembly/runtime-* sub-packages, root optionalDependencies, and pnpm-lock.yaml are intentionally untouched (release-node.yml rewrites them at publish).
• Side-effects: ✅ none — version metadata + docs only; the published npm version comes from the release-node.yml npm_version=0.0.1-rc.1 dispatch. Frozen beta.5 doc snapshot + version registries correctly left as historical.
• Verdict: ✅ Ready (prep-only; no tag/publish).
  Automated review by Claude Code.