🚀 (release): Bump to 0.0.1rc5

agent_assembly/__init__.py

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

docs/compatibility/release-notes.md

@@ -5,6 +5,28 @@ 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.5
+
+Fifth **release candidate** on the `0.0.1` line. This release tracks the published
+`agent-assembly` core **`v0.0.1-rc.5`**: the bundled `aasm` runtime binary and the
+compiled `aa-ffi-python` extension are pinned to that core tag.
+
+Headline is the **agent-registration fix**: the SDK now registers against the
+gateway's derived gRPC endpoint (`:50051`) instead of the REST base URL, and fails
+loud — warning and exposing an unregistered state — when that register call cannot
+reach the gateway, so a silent registration gap can no longer look healthy.
+
+- Register against the derived gRPC endpoint (`:50051`) rather than the REST base,
+  and warn loudly / expose the unregistered state when the register call fails
+  (AAASM-4547).
+- Relax the `pydantic` / `protobuf` / `grpcio` dependency floors and add a CI
+  dependency-resolution guard so an over-tight floor can no longer wedge resolution
+  (AAASM-4518).
+- Docs: per-framework quick-start tabs across the SDK docs (AAASM-4558 / AAASM-4559 /
+  AAASM-4560).
+- Bump the `aa-core` / `aa-proto` / `aa-sdk-client` pins in `aa-ffi-python` to the
+  core `v0.0.1-rc.5` tag.
+
 ## 0.0.1-rc.4
 
 Fourth **release candidate** on the `0.0.1` line. This release tracks the published

docs/examples/agno.md

@@ -19,7 +19,7 @@ Version pins (from `pyproject.toml`):
 | Dependency | Version |
 |---|---|
 | `agno` | `>=2.0.0` |
-| `agent-assembly` | `>=0.0.1rc4` (the release that ships the Agno adapter) |
+| `agent-assembly` | `>=0.0.1rc5` (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.1rc4` (the release that ships the Haystack adapter) |
+| `agent-assembly` | `>=0.0.1rc5` (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.1rc4` (the release that ships the LlamaIndex adapter) |
+| `agent-assembly` | `>=0.0.1rc5` (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.1rc4` (the release that ships the Microsoft Agent Framework adapter) |
+| `agent-assembly` | `>=0.0.1rc5` (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.1rc4` (the release that ships the Smolagents adapter) |
+| `agent-assembly` | `>=0.0.1rc5` (the release that ships the Smolagents adapter) |
 | Python | `>=3.12` |
 
 ## How it works

docs/guides/container-base-image.md

@@ -33,13 +33,13 @@ There are two families of tags: **immutable** (pinned, reproducible) and **movin
 
 | Tag | Example | Mutable? | Use it for |
 | --- | --- | --- | --- |
-| `python:<runtime>-<core-version>` | `python:3.14-slim-v0.0.1-rc.4` | **No** — immutable | **CI and production.** Reproducible, byte-for-byte stable. |
+| `python:<runtime>-<core-version>` | `python:3.14-slim-v0.0.1-rc.5` | **No** — immutable | **CI and production.** Reproducible, byte-for-byte stable. |
 | `python:<runtime>` | `python:3.14-slim` | Yes — moves per release | Local experiments on a fixed Python runtime. |
 | `python:latest` | `python:latest` | Yes — moves per release | Quick one-off tries only. |
 
 `<core-version>` is the **Agent Assembly core / `aa-runtime` release** baked into the
 image — it is also the version of the `aasm` CLI inside the image. Pinning
-`python:3.14-slim-v0.0.1-rc.4` therefore pins *both* the Python runtime and the exact
+`python:3.14-slim-v0.0.1-rc.5` therefore pins *both* the Python runtime and the exact
 governance core/CLI version, which is what makes the build reproducible.
 
 !!! warning "Pin the immutable tag in CI and production"
@@ -53,7 +53,7 @@ A minimal agent image that inherits governance from the base image:
 
 ```dockerfile
 # Pin the immutable tag — Python 3.14 runtime + a fixed governance core/CLI version.
-FROM ghcr.io/ai-agent-assembly/python:3.14-slim-v0.0.1-rc.4
+FROM ghcr.io/ai-agent-assembly/python:3.14-slim-v0.0.1-rc.5
 
 WORKDIR /app
 
@@ -123,7 +123,7 @@ which `agent-assembly` SDK release gets baked in.
 ## Best practices
 
 - **Pin the immutable tag in CI and production.** Use
-  `python:<runtime>-<core-version>` (e.g. `python:3.14-slim-v0.0.1-rc.4`); never `:latest`.
+  `python:<runtime>-<core-version>` (e.g. `python:3.14-slim-v0.0.1-rc.5`); never `:latest`.
 - **Pair the image with the `aa-runtime` sidecar.** The image makes your agent
   *governance-ready*, but the in-process SDK layer is **not a security boundary on its
   own** — point `init_assembly()` at an `aa-runtime` instance (sidecar or service) so policy

docs/javascripts/source-facts-guard.js

@@ -7,7 +7,7 @@
   It issues TWO unauthenticated calls to api.github.com per page load:
 
     1. GET https://api.github.com/repos/<owner>/<repo>/releases/latest
-       → 404, because this repo publishes only pre-releases (0.0.1a4..0.0.1rc3,
+       → 404, because this repo publishes only pre-releases (0.0.1a4..0.0.1rc5,
          0.0.2); GitHub's /releases/latest endpoint excludes pre-releases and
          returns 404 when no non-prerelease exists. AAASM-4318 rewrites this
          request to /releases?per_page=1 and picks the newest so the badge can

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "agent-assembly"
-version = "0.0.1rc4"
+version = "0.0.1rc5"
 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"

sonar-project.properties

@@ -12,7 +12,7 @@ sonar.projectName=python-sdk
 # `-Dsonar.projectVersion=...` (see .github/workflows/rw_run_all_test_and_record.yaml),
 # so it always tracks the current release; this static value is the local-scan
 # fallback only.
-sonar.projectVersion=0.0.1rc4
+sonar.projectVersion=0.0.1rc5
 
 # Path is relative to the sonar-project.properties file. Replace "\" by "/" on Windows.
 sonar.projectBaseDir=./