[AAASM-2313] 🔧 (release): Bump python-sdk to 0.0.1a3 + refresh release intent

[Chisanan232]

Description

Bump pyproject.toml + __init__.py + uv.lock to 0.0.1a3 (PEP 440 form of v0.0.1-alpha.3 tag). Also refresh release-title.md + release-notes.md for alpha-3 content.

Note on master state pre-bump: pyproject.toml was at 0.0.2 (auto-bumped by alpha-2 release workflow's level: patch logic), while agent_assembly/__init__.py was still at 0.0.1a2 (only pyproject was auto-bumped). Both now consistent at 0.0.1a3.

Related Issues

• Jira: AAASM-2313
• Parent: AAASM-1234

— Claude Code (Opus 4.7, 1M context)

[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]

Claude Code review — AAASM-2313

CI state

30 SUCCESS + 10 SKIPPED, 0 failures — mergeable=MERGEABLE, mergeStateStatus=CLEAN. The 10 SKIPPED checks are all by-design for PR context (same pattern as alpha-2's PR #67):

• docs-build skipped because intent.yaml sets artifacts.docs: skip (PR [AAASM-2053] 🐛 (ci): Fix python-sdk workflow triggers + slack_mcp template leakage #66's MkDocs fix)
• Docker validate jobs skipped because no Dockerfile present
• Security supply-chain scan + e2e jobs only fire on tag-push, not on PR
• Two Load Package Configuration jobs skipped because the Parse Release Intent variant handles PR context

All 30 actually-applicable checks pass: full pytest matrix (3.13 × 4 OS combinations × unit + integration), Test Type Imports (AAASM-2053 work), python-build-check / Python Package test, Validation Summary, SonarCloud, Codecov.

Scope vs. AC

AC	Verified	Status
pyproject.toml version 0.0.2 → 0.0.1a3	yes — note the deliberate backwards-step from 0.0.2 (auto-bumped artifact from alpha-2 release workflow) to align with the v0.0.1-alpha.3 tag intent	✅
agent_assembly/__init__.py __version__ → 0.0.1a3	yes — and importantly, this was at 0.0.1a2 on master (drift since alpha-2's auto-bump only touched pyproject). Both now consistent.	✅
uv.lock regenerated	yes — Updated agent-assembly v0.0.2 -> v0.0.1a3 per local run	✅
release-title.md refreshed	yes — v0.0.1-alpha.3 — release-infra fixes verification	✅
release-notes.md refreshed	yes — covers the 3 release-infra fixes (AAASM-2188/2189/2190)	✅
intent.yaml correct (no edit needed)	yes — artifacts.docs: skip from PR #66 still in place	✅

Caveat about the centralized release workflow

intent.yaml has release: true; level: patch. On tag push, the centralized release workflow's Bump Version and Commit step will auto-bump 0.0.1a3 to something else (likely 0.0.4 — patch-bump of 0.0.3, ignoring the pre-release identifier per its bump logic) and publish that to PyPI. The MANUAL bump to 0.0.1a3 here is for the Release Python SDK workflow which reads pyproject.toml directly when building wheels — those wheels will be 0.0.1a3. The version-coordination weirdness is a pre-existing concern (see AAASM-2313 description) and not something this PR is trying to fix.

Verdict

Ready for human approval and merge. All by-design skips, no actionable failures.

— Claude Code (Opus 4.7, 1M context)