🚀 (release): Bump to 0.0.1rc6

[Chisanan232]

Description

Version-bump prep for the 0.0.1rc6 python-sdk release (mirrors the rc.5 bump, +1). Reversible prep only — this does not publish. The published wheel version comes from CI's sync-version; these edits keep the checked-in repo, docs, and badges honest.

Version files (🔖 commit):

• pyproject.toml version = "0.0.1rc6"
• agent_assembly/__init__.py __version__ = "0.0.1rc6"
• sonar-project.properties sonar.projectVersion=0.0.1rc6
• uv.lock regenerated via uv lock

Docs version refs (📝 commit):

• New ## 0.0.1-rc.6 section in docs/compatibility/release-notes.md summarizing what merged since rc.5 (register-endpoint TLS guard AAASM-4655, LangChain deny enforcement AAASM-4658, allow_insecure opt-in AAASM-4664, aasm --version AAASM-4656/4710, OS-classifier fix AAASM-4648, dead-callback/test-hygiene cleanup AAASM-4710/4691)
• 5 framework example install pins >=0.0.1rc5 → >=0.0.1rc6 (agno, haystack, llamaindex-tool-policy, microsoft-agent-framework, smolagents)
• docs/guides/container-base-image.md governed base-image tags → v0.0.1-rc.6
• README.md aasm --version sample output → 0.0.1rc6
• docs/javascripts/source-facts-guard.js published pre-release range advanced to rc6 (tracks the release being cut, per the rc.5 AAASM-4634 precedent + release-docs-sync classification)
• docs/development/docs-macros.md historical example left untouched; native/aa-ffi-python/Cargo.lock FFI pins left to the separate bot/aa-ffi-pin PR (same as the rc.5 cycle)

Type of Change

• 🚀 Release

Breaking Changes

• No

Related Issues

• Related JIRA ticket: AAASM-4679 (3-part release-branch convention)

Testing

• Manual testing performed

Local gates (authoritative): uv sync OK · pytest 798 passed / 15 skipped (1 rerun = pre-existing environmental latency-bench flake, reran and passed) · mypy --ignore-missing-imports agent_assembly clean. ruff check . / ruff format --check . report pre-existing violations that are identical on pristine remote/master and unrelated to this bump (the only changed .py file, __init__.py, passes ruff cleanly).

Checklist

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

---

⚠️ Release publishes via release-python.yml workflow_dispatch AFTER the core rc.6 tag is cut. DO NOT dispatch yet. This PR is reversible version/doc prep only.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[Chisanan232]

Claude Code review — PR #266 🚀 (release): Bump to 0.0.1rc6

Review only (no merge, no approval). Verdict per the 4-point rubric:

1. CI — green (Sonar-only RED, ignorable). Every real gate passes: build-and-test unit/integration/contract jobs, pip-audit, LangChain __getattr__ contract test, CodeQL, PEP 561, wheel-matrix, dependency-floors, docs build. The two RED checks are a single Sonar chain: SonarCloud Scan (step) → build-and-test_all / sonarcloud_finish → build-and-test_all (reports failure) → CI Success (aggregator, exit 1 because build-and-test_all=failure). Confirmed via job steps: the only failing step is SonarCloud Scan; all sibling test/coverage steps succeed. Per release-review policy, Sonar/coverage/Codecov are excluded — no non-acceptance RED to fix.

2. Scope — clean, pure version bump. ✅ 13 files, no stragglers:

• Version files, PEP440 0.0.1rc6 (no dot): pyproject.toml, agent_assembly/__init__.py, sonar-project.properties; uv.lock regenerated (version line only).
• docs/compatibility/release-notes.md: new ## 0.0.1-rc.6 section (dotted heading, consistent with rc.5).
• 5 example install pins >=0.0.1rc5 → >=0.0.1rc6 (agno, haystack, llamaindex-tool-policy, microsoft-agent-framework, smolagents).
• docs/guides/container-base-image.md: governed base-image tags → v0.0.1-rc.6 (dotted tag style, correct for GHCR tags).
• README.md: aasm --version sample → 0.0.1rc6.
• docs/javascripts/source-facts-guard.js: published pre-release range advanced to rc6 (tracks the release being cut — per the rc.5 AAASM-4634 precedent).
• docs/development/docs-macros.md historical example correctly left untouched; FFI Cargo.lock left to the separate bot/aa-ffi-pin PR. Matches the rc.5 cycle.

3. Side effects — version/docs only, no runtime behavior change. ✅ The only .py change is __init__.py __version__. Local gates (this checkout):

• uv sync — OK.
• pytest test/ — 798 passed, 15 skipped, 1 rerun (the environmental latency-bench flake reran and passed).
• mypy --ignore-missing-imports agent_assembly — clean, no issues in 70 files.
• ruff check . — 52 errors, byte-identical to pristine remote/master (verified by ruff-comparing a temp remote/master worktree; diff empty). __init__.py itself passes ruff clean. Pre-existing, not from this bump — noted, not a blocker.

4. FE — N/A.

Verdict: ✅ APPROVE (recommendation only — not merging/approving)

Reversible version/doc prep; CI is effectively green (Sonar-only RED excluded by policy); scope is a pure rc.5→rc.6 bump with no runtime change. Release publishes via release-python.yml workflow_dispatch after the core rc.6 tag is cut — do not dispatch from this PR.

_{🤖 Generated with Claude Code}

[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