[AAASM-3834] 🔖 (release): node-sdk v0.0.1-rc.2

[Chisanan232]

Target

• Task summary:

  Release-intent (prep-only) version bump of the node-sdk from 0.0.1-rc.1 to 0.0.1-rc.2, coordinated with the just-released core v0.0.1-rc.2. This PR only prepares the version metadata and docs; it does not publish, tag, or trigger a release.

• Task tickets:

  • Task ID: AAASM-3834.
  • Relative task IDs:
    • AAASM-3834.
  • Relative PRs:
    • 🤖 (aa-ffi-node): Bump agent-assembly git pins to v0.0.1-rc.2 #204 (FFI-pin to core v0.0.1-rc.2, already merged).
    • [AAASM-3707] 🔖 (release): node-sdk v0.0.1-beta.5 #191 (prior rc/beta prep PR — footprint mirrored here).

• Key point change (optional):

  • package.json version: 0.0.1-rc.1 → 0.0.1-rc.2 (only package.json declaring the SDK version; the @agent-assembly/runtime-* sub-packages use workspace:* and are version-decoupled, so they are untouched).
  • Docs SDK version pins bumped to 0.0.1-rc.2 in docs/02-quick-start/index.md and docs/09-examples/*.md — mirrors exactly what PR [AAASM-3707] 🔖 (release): node-sdk v0.0.1-beta.5 #191 touched.
  • pnpm-lock.yaml not regenerated: the lockfile does not pin the project's own version (verified no 0.0.1-rc.1 reference, and pnpm install --frozen-lockfile succeeds with no drift).

Effecting Scope

• Action Types:
  • 🚀 Release
• Scopes:
  • 🚀 Building
    • 📦 Project configurations
  • 📚 Documentation
• Additional description:
  Prep-only. No source/runtime behavior changes.

Description

• What changed: version bump 0.0.1-rc.1 → 0.0.1-rc.2 in root package.json, plus the matching SDK version pins in quick-start and example docs (9 files total).
• Why: coordinate the node-sdk release line with the just-released core v0.0.1-rc.2; the FFI-pin PR 🤖 (aa-ffi-node): Bump agent-assembly git pins to v0.0.1-rc.2 #204 (core v0.0.1-rc.2) is already merged, so the SDK metadata now needs to advance to rc.2.
• How to verify:
  • pnpm install --frozen-lockfile — succeeds with no lockfile drift.
  • pnpm typecheck — passes.
  • grep -rn '0\.0\.1-rc\.1' docs/02-quick-start docs/09-examples package.json — returns nothing.
  • node -p "require('./package.json').version" — prints 0.0.1-rc.2.
• PREP-ONLY: this PR does not publish to npm and does not create a git tag. Publishing happens later via the release workflow_dispatch.

Closes AAASM-3834

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[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

[Chisanan232]

✅ Review — node-sdk v0.0.1-rc.2 release-intent prep (Claude Code)

1. CI — green. 18/18 pass · 0 fail (test Node 18/20/22/24, build, napi-build, module-smoke, quality, audit, coverage, CodeQL, SonarCloud).

2. Scope vs AAASM-3834 — complete. Release-intent (prep-only) bump 0.0.1-rc.1 → 0.0.1-rc.2, coordinated with core v0.0.1-rc.2 (FFI-pin PR #204 already merged). Footprint mirrors rc.1 prep #191 + the sonar source-of-truth: root package.json (the only package declaring the SDK version — runtime sub-packages are workspace:*/version-decoupled, correctly untouched), docs version pins (docs/02-quick-start, docs/09-examples/*), and sonar-project.properties. pnpm-lock.yaml correctly not regenerated (no own-version pin; --frozen-lockfile clean). PREP-ONLY. Ready to merge.

3. Side effects — none. Diff is exclusively version strings, docs, and the sonar project version. tsc --noEmit passes. No behaviour change.

Verdict: approve & merge. After merge + your go, publish via release-node.yml workflow_dispatch (npm_version=0.0.1-rc.2, binary_source_tag=v0.0.1-rc.2, publish_mode=all; dry-run first).

🤖 Generated with Claude Code