[AAASM-3460] 🔖 (release): python-sdk 0.0.1-beta.4 (prep)

[Chisanan232]

Description

Version-prep PR for the next python-sdk beta on its published PyPI line. PyPI latest is 0.0.1b3, so the next beta is 0.0.1b4 (PEP 440) = 0.0.1-beta.4 (SemVer).

Version model — pyproject is NOT the source of truth. release-python.yml's sync-version composite action rewrites the version in pyproject.toml + agent_assembly/__init__.py to the resolve job's pypi_version at dispatch time (before maturin reads it). The published version comes from the pypi_version workflow input, not the checked-in literal. The checked-in value on master was stale at 0.0.2a1 (wrong vs the 0.0.1 beta line).

What this PR changes:

• Bump the checked-in version 0.0.2a1 → 0.0.1b4 in pyproject.toml and agent_assembly/__init__.py (de-stale + align with the line being shipped), and sync uv.lock.
• Add a 0.0.1-beta.4 entry to docs/compatibility/release-notes.md.
• Does not touch the native/aa-ffi-python/Cargo.toml git-SHA FFI pins — those are bumped by the separate post-publish bot/aa-ffi-pin-<tag> auto-bump PR.

Type of Change

• 🚀 Release

Breaking Changes

• No

Publish gating (do NOT publish from this PR)

The actual PyPI publish is dispatch-gated and must follow the Case A coordination SOP (AAASM-3007). agent-assembly is cutting v0.0.1-beta.3 in parallel. Required order:

1. Cut the agent-assembly v0.0.1-beta.3 core tag and wait for its Release workflow to complete.
2. Wait for + merge the bot/aa-ffi-pin-<tag> auto-bump PR on this repo (brings master's FFI pins in line with the new core tag).
3. Only then dispatch release-python.yml with pypi_version=0.0.1b4 + binary_source_tag=v0.0.1-beta.3.

This PR does not dispatch any publish workflow.

Related Issues

• Related JIRA ticket: AAASM-3460

Testing

• No tests required (metadata/docs change; pre-commit ruff/black/isort/mypy/uv-lock passed locally on the version bump)

Checklist

• Code follows project style guidelines
• Self-review completed
• Documentation updated if needed

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[Chisanan232]

Claude Code — PR review (AAASM-3460, python-sdk beta.4 prep)

✅ Looks good — release-prep only, no publish. Correct version: PyPI 0.0.1b3 → next 0.0.1b4 (= 0.0.1-beta.4). De-stales pyproject.toml + agent_assembly/__init__.py from the stray 0.0.2a1 to 0.0.1b4, syncs uv.lock, adds the release-notes entry.

• Correctly identified the published version is workflow-set (sync-version rewrites it from pypi_version at dispatch) — so this is metadata/docs hygiene; the real version comes from the dispatch input.
• Correctly did NOT touch the native/aa-ffi-python git-SHA pin — that's the post-core-tag bot/aa-ffi-pin auto-bump PR's job.
• Publish gating respected (no dispatch): core v0.0.1-beta.3 tag → merge FFI-pin PR → then dispatch release-python.yml pypi_version=0.0.1b4 binary_source_tag=v0.0.1-beta.3.

Good to merge as prep. Actual publish stays gated on the core release.

[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