[AAASM-3833] 🔖 (release): python-sdk 0.0.1rc2

[Chisanan232]

Description

Release-intent (prep-only) version bump for the Python SDK: 0.0.1rc1 → 0.0.1rc2,
coordinated with the just-released core v0.0.1-rc.2. The aa-ffi-python core
pin (aa-core/aa-proto/aa-sdk-client) was already bumped to v0.0.1-rc.2 in
the merged FFI-pin PR #189; this PR aligns the published SDK package metadata and docs.

Changes:

• pyproject.toml: version = "0.0.1rc2".
• agent_assembly/__init__.py: __version__ = "0.0.1rc2" (kept in lockstep with pyproject).
• uv.lock: regenerated so the project's own pinned version matches (uv sync would
  otherwise fail in CI).
• docs/compatibility/release-notes.md: new 0.0.1-rc.2 section (mirrors the rc.1 entry).
• docs/examples/{agno,haystack,llamaindex-tool-policy,microsoft-agent-framework,smolagents}.md:
  bump the agent-assembly install pin >=0.0.1rc1 → >=0.0.1rc2.
• docs/guides/container-base-image.md: bump the governed base-image tag examples
  v0.0.1-rc.1 → v0.0.1-rc.2 to track the coordinated core release.

This PR is PREP-ONLY — it does not publish or tag. Publishing happens later via
the operator-dispatch release-python.yml (workflow_dispatch).

Type of Change

• ✨ New feature
• 🔧 Bug fix
• ♻️ Refactoring
• 🍀 Performance improvement
• 📚 Documentation update
• 🚀 Release

Breaking Changes

• No
• Yes (please describe below)

Related Issues

• Related JIRA ticket: AAASM-3833
• Related GitHub issues: 🤖 (aa-ffi-python): Bump aa-core/aa-proto/aa-sdk-client pin to v0.0.1-rc.2 #189 (core FFI pin to v0.0.1-rc.2, already merged)

Testing

Describe the testing performed for this PR:

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed
• No tests required (explain why)

Verification performed locally:

• uv lock succeeded — agent-assembly v0.0.1rc1 -> v0.0.1rc2.
• uv sync succeeded against the regenerated lockfile.
• pytest test/unit/test_runtime_import_isolation.py → 4 passed (confirms the
  in-tree __version__ resolves consistently across a subprocess import).

No code paths change — this is a metadata/docs/lockfile-only bump, so no new tests
are required.

Checklist

• Code follows project style guidelines
• Self-review completed
• Comments added for complex logic
• Documentation updated if needed
• All tests passing

Closes AAASM-3833

🤖 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
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Chisanan232]

✅ Review — python-sdk 0.0.1rc2 release-intent prep (Claude Code)

1. CI — green. 22 pass · 6 skipping · 0 fail. Skips are tag/acceptance-only (sonarcloud_finish quality gate + coverage). No hard failures.

2. Scope vs AAASM-3833 — complete. Release-intent (prep-only) bump 0.0.1rc1 → 0.0.1rc2, coordinated with core v0.0.1-rc.2 (FFI-pin PR #189 already merged). Footprint mirrors the rc.1 prep #177 + the sonar source-of-truth: pyproject.toml, agent_assembly/__init__.py (__version__ in lockstep), uv.lock (regenerated — the project's own version is pinned there), docs/compatibility/release-notes.md, docs/examples/*, docs/guides/container-base-image.md, and sonar-project.properties. PREP-ONLY: no tag, no publish. Ready to merge.

3. Side effects — none. Diff is exclusively version strings, docs, the regenerated lockfile, and the sonar project version. No runtime/library code touched; uv sync consistent. Nothing can alter SDK behaviour.

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

🤖 Generated with Claude Code