[AAASM-3763] 🔖 (release): python-sdk v0.0.1rc1

.claude/skills/release-runbook/SKILL.md

@@ -149,10 +149,21 @@ fires (or in a follow-up PR on the same cycle), bring the repo in sync:
    The b5 wave found four wrong: `agno` was pinned `>=…b4` and
    `haystack` / `microsoft-agent-framework` / `smolagents` were pinned `>=…b2`,
    yet all four adapters only ship in b5, so every one had to move to `>=…b5`.
-4. **Leave the history alone.** Do **not** rewrite `CHANGELOG` /
+4. **Add the new release-notes section.** Prepend a new `## <version>` heading at
+   the **top** of the version list in `docs/compatibility/release-notes.md`
+   (immediately above the most recent existing entry), summarizing this release —
+   the channel promotion and the headline changes since the last published tag.
+   Use the hyphenated tag form of the version (e.g. `## 0.0.1-rc.1`) to match the
+   existing headers. Derive the highlights from the delta
+   (`git log --oneline <last-tag>..HEAD` / the merged PRs since the last tag); do
+   not invent changes. This is the one *additive* edit to the file — it is
+   distinct from, and must not be conflated with, the don't-rewrite-history rule
+   below.
+5. **Leave the history alone.** Do **not** rewrite `CHANGELOG` /
    `docs/compatibility/release-notes.md` past entries, and do **not** touch the
    auto-managed Docusaurus docs snapshot (`publish-release-tag` labels it — see
-   above). You are syncing *current* pins, not editing the historical record.
+   above). You are syncing *current* pins and adding the one new section above —
+   not editing the historical record.
 
 (The `agent-assembly` core `release-docs-sync` skill is the canonical, full
 version-sweep procedure across every channel; this section is the python slice.)

agent_assembly/__init__.py

@@ -8,7 +8,7 @@
 import sys
 from typing import TYPE_CHECKING, Any
 
-__version__ = "0.0.1b5"
+__version__ = "0.0.1rc1"
 
 _MODULE_CORE = "agent_assembly.core"
 _MODULE_ADAPTERS = "agent_assembly.adapters"

docs/compatibility/release-notes.md

@@ -5,6 +5,22 @@ Release notes for the Agent Assembly Python SDK. Versions follow [SemVer](https:
 !!! info "0.x development"
     The SDK is in active 0.x development; per-release notes are minimal. Track full changes via [the commits to `master`](https://github.com/ai-agent-assembly/python-sdk/commits/master) and the [GitHub releases](https://github.com/ai-agent-assembly/python-sdk/releases) feed.
 
+## 0.0.1-rc.1
+
+First **release candidate** on the `0.0.1` line — promotes the Python SDK from
+the `beta` channel to `rc`. This release tracks the published `agent-assembly`
+core **`v0.0.1-rc.1`**: the bundled `aasm` runtime binary and the compiled
+`aa-ffi-python` extension are pinned to that core tag (AAASM-3763).
+
+Changes since beta.5 are limited to the core-pin promotion plus security and
+release housekeeping — there is no new SDK surface:
+
+- Require TLS for non-loopback gateway / op-control connections — refuse a Bearer
+  API key over plaintext `http` and refuse a plaintext gRPC channel to a
+  non-loopback host (AAASM-3685).
+- Pin third-party reusable CI workflows to commit SHAs (AAASM-3686).
+- Fix and pin the CycloneDX SBOM flag in `release-python.yml` (AAASM-3722).
+
 ## 0.0.1-beta.5
 
 Beta iteration of the Python SDK on the `0.0.1` line. Headline of this release is

docs/examples/agno.md

@@ -19,7 +19,7 @@ Version pins (from `pyproject.toml`):
 | Dependency | Version |
 |---|---|
 | `agno` | `>=2.0.0` |
-| `agent-assembly` | `>=0.0.1b5` (the release that ships the Agno adapter) |
+| `agent-assembly` | `>=0.0.1rc1` (the release that ships the Agno adapter) |
 | Python | `>=3.12` |
 
 ## How it works

docs/examples/haystack.md

@@ -20,7 +20,7 @@ Version pins (from `pyproject.toml`):
 | Dependency | Version |
 |---|---|
 | `haystack-ai` | `>=2.0.0,<3.0` |
-| `agent-assembly` | `>=0.0.1b5` (the release that ships the Haystack adapter) |
+| `agent-assembly` | `>=0.0.1rc1` (the release that ships the Haystack adapter) |
 | Python | `>=3.12` |
 
 ## How it works

docs/examples/llamaindex-tool-policy.md

@@ -19,7 +19,7 @@ Version pins (from `pyproject.toml`):
 | Dependency | Version |
 |---|---|
 | `llama-index-core` | `>=0.14.22` |
-| `agent-assembly` | `>=0.0.1b5` (the release that ships the LlamaIndex adapter) |
+| `agent-assembly` | `>=0.0.1rc1` (the release that ships the LlamaIndex adapter) |
 | Python | `>=3.12` |
 
 ## How it works

docs/examples/microsoft-agent-framework.md

@@ -19,7 +19,7 @@ Version pins (from `pyproject.toml`):
 | Dependency | Version |
 |---|---|
 | `agent-framework` (the `live` extra) | `>=1.9,<2` |
-| `agent-assembly` | `>=0.0.1b5` (the release that ships the Microsoft Agent Framework adapter) |
+| `agent-assembly` | `>=0.0.1rc1` (the release that ships the Microsoft Agent Framework adapter) |
 | Python | `>=3.12` |
 
 The adapter's `get_supported_versions()` reports `>=1.0.0,<2.0` — governance attaches across the 1.x line.

docs/examples/smolagents.md

@@ -19,7 +19,7 @@ Version pins (from `pyproject.toml`):
 | Dependency | Version |
 |---|---|
 | `smolagents` | `>=1.0.0,<2.0.0` |
-| `agent-assembly` | `>=0.0.1b5` (the release that ships the Smolagents adapter) |
+| `agent-assembly` | `>=0.0.1rc1` (the release that ships the Smolagents adapter) |
 | Python | `>=3.12` |
 
 ## How it works

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "agent-assembly"
-version = "0.0.1b5"
+version = "0.0.1rc1"
 description = "Python SDK for AI Agent Assembly - A governance-native runtime for AI agents"
 authors = [{ name = "Agent Assembly Team", email = "team@agent-assembly.dev" }]
 requires-python = ">=3.12,<4.0"