[saurabhjain1592]

Scope

Prepare a reviewed Python SDK 9.5.1 release candidate from merged main 7018d75921657fed672ba18fced0a1b9b3f8da6f (#276). Align pyproject.toml, axonflow/_version.py, and the first released CHANGELOG.md section. This PR changes no runtime code, tags, registry artifacts, or production state. PyPI and the GitHub tag/release still have no 9.5.1 entry as checked on 2026-11-03.

Exact-head local board

Candidate commit: cf54af7a0ee9a7069fd48db0e8ad2be4e31cd5a6 (signed off). In a fully isolated Python 3.11.14 venv with declared .[dev,all] dependencies:

• Full pytest: 1,645 passed, 30 skipped, 86.17% coverage (75% gate).
• Ruff check and format, mypy (39 source files), falsey-clobber baseline, generated AuthZEN types, no-mocks runtime E2E lint, version alignment, pip check, and git diff --check: passed.
• Wire-shape marker run: 12 passed, 8 designed skips without external OpenAPI specs.
• Fresh exact-commit wheel and sdist built with python -m build --no-isolation; both passed twine check and contain 9.5.1 metadata/runtime source.
• Wheel SHA-256: 6ab0a3b85d3b28314f9940e31deff1ea4f46f71348b312f6569256c136b3b4ee.
• Sdist SHA-256: 5a1096724b9a57a697bb6356fabef206cb852be6176bdf9081613e8afa3456bb.
• A second clean Python 3.11 venv cold-installed that exact wheel with dependencies. Metadata and runtime version both read 9.5.1 from site-packages; pip check passed. Nine canonical/trailing-dot/IDNA Hosted origins were refused before any HTTP attempt with verified Portal guidance, while explicit self-hosted Community registration still reached its local stub.

Local evidence, artifacts, and logs are under /private/tmp/oc4487-python-951-evidence for the release operator. These are candidate artifacts only. The GitHub Actions billing lock still needs resolution or a reviewed CI-down exception; local results do not turn remote checks green.

Skip-runtime-e2e justification

This PR only changes release version declarations and the changelog. It adds no user-facing runtime or wire behavior. The guarded runtime-e2e/hosted_first_run/test.py landed in #276; that merge's installed-wheel staging proof covered the first-run guard, paid test Checkout, usage, terminal 402, and revocation. The exact candidate wheel also passed the fresh-consumer smoke above. No new runtime E2E file is needed for this metadata-only release-prep diff.

Release hold

Independent review and release-owner approval are required before merge or tag. After merge, rebuild from the reviewed merge SHA, recheck 9.5.1 registry availability, choose one publisher path (prefer the tagged trusted workflow when Actions returns), compare exact artifacts, and cold-install the published package. Do not upload this PR's locally built wheel or sdist as an already released version; do not tag or publish from this branch.

[saurabhjain1592]

Release-preparation CI-down exception for #277

The reviewed head is cf54af7a0ee9a7069fd48db0e8ad2be4e31cd5a6, based on 7018d75921657fed672ba18fced0a1b9b3f8da6f. The only changed files are CHANGELOG.md, pyproject.toml, and axonflow/_version.py; the diff is version/changelog metadata and passes git diff --check. Independent exact-head review found no code issue. DCO passed.

GitHub Actions is under the organization billing lock. The ruleset-required lint, Lint — no mocks in runtime-e2e/, Runtime E2E required for user-facing changes, and Test Summary jobs failed before running steps. The sampled lint and Test Summary jobs in run 41679471409 have empty steps arrays. These are unavailable checks, not passing CI. No runtime E2E skip is inferred from a green job; the PR body documents why this metadata-only change does not add a new runtime E2E file.

The exact-head Python 3.11.14 local board passed 1,645 tests (30 skipped) with 86.17% coverage, Ruff check/format, mypy, version alignment, falsey-clobber and AuthZEN checks, no-mocks lint, wire-shape marker, pip check, Twine, and an isolated installed-wheel consumer smoke. The wheel SHA-256 is 6ab0a3b85d3b28314f9940e31deff1ea4f46f71348b312f6569256c136b3b4ee; the sdist SHA-256 is 5a1096724b9a57a697bb6356fabef206cb852be6176bdf9081613e8afa3456bb. The local 20-file evidence manifest SHA-256 is a919288e53a006fda2785da04eb0e330dba213def843f289071a3d3ec1cdfb88. PyPI 9.5.1 and tag v9.5.1 are absent as checked on 2026-11-03.

For this preparation merge only, temporarily remove the required_status_checks rule from repository ruleset 11269575 while retaining pull-request, deletion, non-fast-forward, and linear-history rules. Save the exact original rule, merge this one reviewed head by squash, then restore the rule immediately and verify equality to the saved configuration. This exception does not approve a tag, PyPI upload, production deployment, or public client promotion. Rebuild and cold-install from the merge SHA; the publication gate remains held until a separate release decision and published-artifact proof.

[saurabhjain1592]

Preparation merge completed at 7f841b2e3d9cc26caf3d4495b51bb32606ba6c09 (squash of reviewed head cf54af7a). Ruleset 11269575 was restored and independently re-read equal to the saved pre-merge configuration, including all four required checks. No tag or PyPI upload was made; both v9.5.1 and PyPI 9.5.1 remained absent after merge.

From the merge SHA, the unpublished wheel (sha256:407027ae4769d59aeafc647a0bd0fdd1042c1576f8ec86b319c65aab5fe7ba00) and sdist (sha256:199f2d082b50146bfc175f67b084141fcf1b6f2149426eca1a1fe2137affb6c5) passed Twine. Their archive bytes differ from the pre-merge build, but the 45 wheel files and 112 sdist files have identical names and contents. A fresh wheel install passed pip check, 9.5.1 site-packages/version checks, nine Hosted-origin zero-HTTP refusals, and explicit Community registration. The local merge-evidence manifest is sha256:afa7815c0f4855bd5651fe84464080decf14e056e805befecb0620ec36c22ec4 under /private/tmp/oc4487-python-951-merge-gate. Registry publication and published-artifact cold install remain held for a separate release decision.