diff --git a/CHANGELOG.md b/CHANGELOG.md index d2c30c1..b3e1f1c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -26,6 +26,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 source files, and test files, and skips symlinked entries even when local search is configured to follow symlinks. +### Python distribution + +- The native Python package was separately published to PyPI as + `eggsearch==0.4.4` on 2026-10-28, with CPython 3.11–3.15 ABI3 wheels for + Linux x86_64/aarch64, macOS x86_64/arm64, Windows x86_64, and experimental + ARMv7 hard-float Linux. + ## [0.4.3] - 2026-10-13 ### Fixed diff --git a/README.md b/README.md index b201ee0..f03b96d 100644 --- a/README.md +++ b/README.md @@ -27,6 +27,19 @@ Pin a version, or install from source with `cargo install eggsearch --locked`. T installer verifies a SHA-256 checksum and the version, and never elevates — see [Installation](docs/installation.md) for targets and fallback rules. +Install the native asyncio Python package separately: + +```bash +python -m pip install eggsearch +``` + +On ARMv7 SBCs, require a prebuilt wheel so unsupported targets fail without +attempting a source build: + +```bash +python -m pip install --only-binary=:all: eggsearch +``` + ## Quickstart ```bash @@ -147,9 +160,9 @@ See [Safety](docs/safety.md) and [Threat model](docs/threat-model.md). [CodeGG harness integration](docs/codegg-integration.md) · [Test inventory](docs/test-inventory.md) -The in-process asyncio Python package is under `bindings/python` and is not -published yet. See the [Python library guide](docs/python-library.md) for -local build instructions and current support limits. +The in-process asyncio Python package is published separately on PyPI. See the +[Python library guide](docs/python-library.md) for its API, platform limits, +and experimental ARMv7 SBC support. ## Build diff --git a/architecture/python-library.md b/architecture/python-library.md index e0a8550..68f7529 100644 --- a/architecture/python-library.md +++ b/architecture/python-library.md @@ -19,13 +19,13 @@ superseded as the qualification basis by M008 advisory remediation and symlink containment at `plans/closure/python-native-library/008-status.md` (candidate `067468a`, fully-green run `38641009246`). -A separate **active PyPI distribution workstream** (not a reopening of M001–M008) -is registered at `plans/subsystems/python-pypi-distribution-roadmap.md`. -It prepares CPython 3.11–3.15 ABI3 support, hosted prebuilt ARMv7/SBC wheels, -first controlled PyPI publication, and **post-publication** physical-SBC -benchmarking. No device-local source build or native SBC benchmark is a -first-release prerequisite; compatible SBC installs must use the published -prebuilt wheel and are labeled experimental pending hardware evidence. +A separate PyPI distribution workstream (not a reopening of M001–M008) is +registered at `plans/subsystems/python-pypi-distribution-roadmap.md`. M003 +published `eggsearch==0.4.4` with CPython 3.11–3.15 ABI3 support and hosted +prebuilt ARMv7 wheels. M004 covers **post-publication** physical-SBC +benchmarking. No device-local source build or native SBC benchmark was a +first-release prerequisite; ARMv7 installs use the published prebuilt wheel +and remain experimental pending hardware evidence. ## Rust operation facade @@ -70,19 +70,21 @@ out with `debug_assertions` off and never ships in release wheels. Milestone status and exact-candidate evidence live in `plans/registry.md` and `plans/closure/python-native-library/`. A compiled extension alone is not evidence of a supported Python consumer. Wheel support -is limited to targets with native install and runtime qualification, and -publication requires separate authorization. +is limited to targets with native install and runtime qualification. Python +publication is separate from Rust crate and Eggpack binary releases and uses +the manually dispatched OIDC workflow. -The active PyPI distribution candidate uses PyO3's `abi3-py311` stable ABI. -Its release matrix builds a manylinux2014 Linux x86_64/aarch64 wheel, macOS -x86_64/arm64 wheels, and a Windows x86_64 wheel, then installs each exact -artifact on CPython 3.11–3.15 in separate consumer jobs. These platform claims -remain conditional on the matching exact-candidate matrix jobs passing. An sdist +The published PyPI distribution uses PyO3's `abi3-py311` stable ABI. Its +release matrix built a manylinux2014 Linux x86_64/aarch64 wheel, macOS +x86_64/arm64 wheels, a Windows x86_64 wheel, and an experimental ARMv7 +hard-float wheel; all six passed exact-candidate qualification and public +binary-only consumer installs. An sdist rebuild uses the binding and root Cargo manifests from clean extraction; it can build offline with locked crates already cached, otherwise Cargo registry access is required. PyPy, free-threaded CPython, and Windows ARM64 are outside -the support matrix. ARMv7 requires its separate experimental wheel and -emulated installed-wheel qualification before it may be listed as supported. +the support matrix. ARMv7 has an experimental `manylinux_2_28_armv7l` +hard-float wheel with emulated public installation; physical hardware evidence +is pending through M004. The public Python `AsyncEggsearch` wrapper adds `async with`, `aclose()`, and the ten named keyword methods over the generic native `execute` call. Request diff --git a/bindings/python/PYTHON_README.md b/bindings/python/PYTHON_README.md index dc9ac81..1f0c9ec 100644 --- a/bindings/python/PYTHON_README.md +++ b/bindings/python/PYTHON_README.md @@ -4,8 +4,21 @@ The native package exposes an asyncio client for Eggsearch's ten search, fetch, repository, security, research, diagnostic, and evidence operations. It calls the shared Rust SDK in-process and does not start the MCP server. -This package is not published to PyPI. To build and install it locally, use -Rust 1.89, CPython 3.11–3.15, and an active virtual environment: +Install the published package with pip: + +```bash +python -m pip install eggsearch +``` + +ARMv7 SBC support is experimental; require a prebuilt wheel and do not build +the source distribution on-device: + +```bash +python -m pip install --only-binary=:all: eggsearch +``` + +To build and install from this checkout for development, use Rust 1.89, +CPython 3.11–3.15, and an active virtual environment: ```bash python -m venv .venv diff --git a/bindings/python/benchmarks/sbc_runtime.py b/bindings/python/benchmarks/sbc_runtime.py index 3ef21a0..d03dae5 100644 --- a/bindings/python/benchmarks/sbc_runtime.py +++ b/bindings/python/benchmarks/sbc_runtime.py @@ -20,6 +20,9 @@ from eggsearch import AsyncEggsearch, EggsearchError, tool_names +QUALIFIED_VERSION = "0.4.4" +QUALIFIED_SOURCE_SHA = "1135608af5d625cd72db6704adf3bcabd1a58ab1" + def percentile(values, fraction): ordered = sorted(values) @@ -311,11 +314,14 @@ def run_sequential_event_loop_benchmark(config, repeats): def main(): parser = argparse.ArgumentParser() parser.add_argument("--version", required=True) + parser.add_argument("--source-sha", required=True) parser.add_argument("--repeats", type=int, default=40) parser.add_argument("--wheel", type=Path, required=True) parser.add_argument("--pip-report", type=Path, required=True) parser.add_argument("--output", type=Path, default=Path("sbc-runtime.json")) args = parser.parse_args() + if args.version != QUALIFIED_VERSION or args.source_sha != QUALIFIED_SOURCE_SHA: + raise SystemExit("version or source SHA does not match the M003-qualified PyPI candidate") installed = distribution("eggsearch") if installed.version != args.version: raise SystemExit(f"installed eggsearch {installed.version} does not match {args.version}") @@ -374,6 +380,7 @@ def main(): raise SystemExit("installed package did not expose ten unique tool names") result = { "package_version": installed.version, + "qualified_source_sha": args.source_sha, "wheel": str(args.wheel), "wheel_sha256": wheel_sha256, "pypi_wheel_url": download["url"], diff --git a/docs/installation.md b/docs/installation.md index cb86a09..8f1a74b 100644 --- a/docs/installation.md +++ b/docs/installation.md @@ -1,12 +1,31 @@ # Installation +## Python package + +The in-process native Python package is published separately from the Rust +crate and executable assets. Install it on a supported host with: + +```bash +python -m pip install eggsearch +``` + +On ARMv7 or another SBC, require a prebuilt compatible wheel so an unsupported +host fails without compiling the source distribution: + +```bash +python -m pip install --only-binary=:all: eggsearch +``` + +The published package supports CPython 3.11–3.15. Linux x86-64 and aarch64 +wheels use manylinux2014 (glibc 2.17); the experimental ARMv7 hard-float wheel +requires glibc 2.28 or newer. macOS x86-64/arm64 and Windows x86-64 wheels are +also available. See the [Python library guide](python-library.md) for API and +platform details. ARMv7 remains experimental pending physical SBC measurements. + ## Install from the published binary release -The `v0.4.3` release candidate is prepared to carry the Mode-Off local -repository dispatch fix. Until it is published, `v0.4.2` remains the latest -published release. `v0.3.9` was the first binary-enabled release and `v0.4.0` -is crate + tag only, with no published binaries. Once published, install the -host-matched executable with the reviewed release installer: +The Rust executable release is separate from the Python package. Install the +host-matched executable with the release installer: ```bash curl -fsSL https://github.com/eggstack/eggsearch/releases/latest/download/install.sh | bash @@ -18,7 +37,7 @@ PowerShell: irm https://github.com/eggstack/eggsearch/releases/latest/download/install.ps1 | iex ``` -Pin a published binary version when reproducibility matters: +Pin a published executable version when reproducibility matters: ```bash curl -fsSL https://github.com/eggstack/eggsearch/releases/latest/download/install.sh | bash -s -- --version 0.4.3 diff --git a/docs/python-library.md b/docs/python-library.md index 779f32a..70941aa 100644 --- a/docs/python-library.md +++ b/docs/python-library.md @@ -3,7 +3,19 @@ The native Python package wraps the same Rust SDK operations used by Eggsearch's MCP tools. It runs in-process and does not launch an Eggsearch executable, MCP server, or listener. The package is an independent PyO3 extension under -`bindings/python`; it is not published to PyPI yet. +`bindings/python` and is published separately from the Rust crate and binaries. + +Install it from PyPI: + +```bash +python -m pip install eggsearch +``` + +On ARMv7 SBCs, require a compatible prebuilt wheel: + +```bash +python -m pip install --only-binary=:all: eggsearch +``` ## Build and use locally @@ -19,12 +31,10 @@ python -m pytest -q bindings/python/tests pyright bindings/python/python/eggsearch bindings/python/examples ``` -No Python runtime dependencies are required. The candidate distribution and -import name are both `eggsearch`, and the Python package version tracks the root -Eggsearch version as a starting point for synchronized candidate artifacts. -PyPI's project JSON endpoint returned 404 for `eggsearch` on 2026-10-14. The -package remains unpublished, and name availability must be rechecked -immediately before any separately authorized publication. +No Python runtime dependencies are required. The distribution and import name +are both `eggsearch`. The first public Python distribution is version 0.4.4; +Python package publication is a separate release from the Rust crate and +Eggpack binary assets. ## Client API @@ -122,24 +132,21 @@ remote source text uses `external_untrusted`. Preserve the `trust` and ## Compatibility and features The binding enables PyO3's `abi3-py311` stable ABI, targeting GIL-enabled -CPython 3.11 and newer. The active PyPI distribution qualification targets -CPython 3.11 through 3.15 on each supported platform; only candidates that pass -the exact 25-cell workflow matrix qualify. Linux wheels use the manylinux2014 -baseline; native targets are Linux x86_64 and aarch64, macOS x86_64 and arm64, -and Windows x86_64. CI builds on each target and installs each exact wheel on -all five interpreters without installing Rust in the consumer job. These -claims remain conditional on the corresponding exact-candidate jobs passing. - -PyPy, free-threaded CPython, and Windows ARM64 are not claimed. ARMv7 is -planned as experimental SBC support only after its separate build and emulated -installed-wheel qualification passes. The release candidate uses a pinned -manylinux cross toolchain and targets the `manylinux_2_28_armv7l` compatibility -tag; its glibc floor and hard-float ABI must pass artifact audit and emulated -installation before publication. That support is limited to ARMv7 hard-float -Linux with glibc 2.28 or newer. ARMv6, soft-float, Windows ARM64, and Alpine or -other musl systems are not included. After the first release appears on PyPI, -SBC users must require a wheel so pip fails on an unsupported target instead -of trying to compile from source: +CPython 3.11 and newer. Version 0.4.4 passed the exact 25-cell CPython +3.11–3.15 workflow matrix and public binary-only consumer installs. Linux wheels +use the manylinux2014 baseline; native targets are Linux x86_64 and aarch64, +macOS x86_64 and arm64, and Windows x86_64. CI builds on each target and +installs each exact wheel on all five interpreters without source builds in the +consumer job. The exact candidate and public-consumer evidence is recorded in +the M003 closure. + +PyPy, free-threaded CPython, and Windows ARM64 are not claimed. ARMv7 support is +experimental SBC support, qualified by a `manylinux_2_28_armv7l` hard-float +wheel, an ELF audit, and emulated public installation. It supports ARMv7 +hard-float Linux with glibc 2.28 or newer; physical board compatibility and +performance remain unmeasured. ARMv6, soft-float, Windows ARM64, and Alpine or +other musl systems are not included. SBC users must require a wheel so pip fails +on an unsupported target instead of trying to compile from source: ```bash python -m pip install --only-binary=:all: eggsearch @@ -157,9 +164,8 @@ An sdist build requires Rust 1.89, a C toolchain, and the Cargo dependencies in `bindings/python/Cargo.lock`. It can build offline when those locked crate sources are already in Cargo's local cache; a fresh build must be able to fetch them from Cargo registries. Native wheels avoid those build requirements at -install and runtime. After the M003 first publication is verified, upgrade -with `python -m pip install --upgrade eggsearch` and remove with -`python -m pip uninstall eggsearch`. +install and runtime. Upgrade with `python -m pip install --upgrade eggsearch` +and remove with `python -m pip uninstall eggsearch`. ## Post-publication SBC benchmark @@ -168,12 +174,13 @@ the exact public wheel with `--only-binary=:all:`, then run the standard-library harness outside the repository checkout: ```bash -python -m pip install --only-binary=:all: --report install-report.json eggsearch==VERSION -python -m pip download --only-binary=:all: --no-deps --dest wheelhouse eggsearch==VERSION +python -m pip download --only-binary=:all: --no-deps --dest wheelhouse eggsearch==0.4.4 +python -m pip install --only-binary=:all: --no-deps --report install-report.json eggsearch==0.4.4 python /path/to/eggsearch/bindings/python/scripts/smoke_installed_wheel.py python /path/to/eggsearch/bindings/python/benchmarks/sbc_runtime.py \ - --version VERSION --wheel /path/to/wheelhouse/eggsearch-*.whl \ - --pip-report install-report.json + --version 0.4.4 --source-sha 1135608af5d625cd72db6704adf3bcabd1a58ab1 \ + --wheel /path/to/wheelhouse/eggsearch-0.4.4-*.whl \ + --pip-report install-report.json --output sbc-runtime.json ``` The harness verifies that the wheel matches the public PyPI URL and SHA-256 in diff --git a/docs/release-checklist.md b/docs/release-checklist.md index df8e723..011c51c 100644 --- a/docs/release-checklist.md +++ b/docs/release-checklist.md @@ -28,11 +28,18 @@ Short operational checklist. The authoritative release process lives in - [ ] Review binary checksums and publish the draft release manually - [ ] Verify the published release has exactly 19 assets (7 executables, 7 `.sha256` sidecars, `install.sh`, `install.ps1`, `release-manifest.json`, `install-exact.sh`, `install-exact.ps1`) and run external Unix/Windows installer smoke -## Separate Python package publication - -- [ ] Confirm M001 and M002 exact-SHA qualification and root CI are green -- [ ] Configure PyPI Trusted Publishing for `eggstack/eggsearch`, workflow `release-python-pypi.yml`, environment `pypi` -- [ ] Create GitHub environment `pypi` before dispatching -- [ ] Dispatch the Python publication workflow with the qualified SHA, Python qualification run ID, and synchronized version -- [ ] Confirm public binary-only installs and the M003 closure record before announcing availability -- [ ] Schedule M004 benchmarks on native SBC devices after publication +## Initial Python package publication — completed 2026-10-28 + +- [x] Confirm M001 and M002 exact-SHA qualification and root CI are green for `1135608af5d625cd72db6704adf3bcabd1a58ab1` +- [x] Configure PyPI Trusted Publishing for `eggstack/eggsearch`, workflow `release-python-pypi.yml`, environment `pypi` +- [x] Create GitHub environment `pypi` before dispatching; no required reviewer was configured per maintainer direction +- [x] Dispatch run `40742653291` with the qualified SHA, Python qualification run `40729011504`, and version `0.4.4` +- [x] Confirm public binary-only installs on five native platforms and emulated ARMv7; see `plans/closure/python-pypi-distribution/003-status.md` +- [ ] Run M004 benchmarks on native aarch64 and ARMv7 SBC devices after publication + +## Future Python package publications + +- [ ] Qualify the exact candidate source and verify a synchronized, unused Python version +- [ ] Confirm PyPI Trusted Publishing and the pre-created GitHub `pypi` environment remain configured +- [ ] Dispatch `.github/workflows/release-python-pypi.yml` with the exact SHA, successful qualification run ID, and version +- [ ] Confirm public binary-only installs and record the release evidence before announcing availability diff --git a/docs/release.md b/docs/release.md index 1137099..d058116 100644 --- a/docs/release.md +++ b/docs/release.md @@ -62,24 +62,26 @@ producer contract. The native Python distribution has its own release path and does not use root Rust tags, crates.io publication, Eggpack, or the 19-asset binary inventory. The controlling workstream is `plans/subsystems/python-pypi-distribution-roadmap.md`. -Its first publication must use the exact candidate SHA whose five-platform, -25-cell interpreter matrix, ARMv7 emulated install, source rebuild, audits, and -root CI all passed. - -Before dispatching `.github/workflows/release-python-pypi.yml`, configure the -PyPI Trusted Publisher for owner `eggstack`, repository `eggsearch`, workflow -`release-python-pypi.yml`, and pre-create the GitHub environment `pypi`. The -publisher workflow requires the exact candidate SHA, successful Python -qualification run ID, and synchronized package version. Its preflight verifies -the environment exists, then verifies the source and six-wheel plus sdist -inventory before the OIDC publish job. Dispatching the workflow is the explicit -publication action. The publication is complete only after independent public -binary-only installs pass on Linux x86_64/aarch64, macOS x86_64/arm64, Windows -x86_64, and emulated ARMv7. - -Do not announce PyPI availability or update the public installation claim -until that post-publication verification and M003 closure record are complete. -Physical SBC measurements belong to M004 and happen after the initial release. +The first publication completed on 2026-10-28 as `eggsearch==0.4.4` from +qualified source `1135608af5d625cd72db6704adf3bcabd1a58ab1`. Publication run +`40742653291` verified the exact source and wheelhouse, published through +Trusted Publishing, and passed public binary-only installs on five native +platform families plus emulated ARMv7. See +`plans/closure/python-pypi-distribution/003-status.md` for the inventory and +evidence. + +For future Python releases, configure the PyPI Trusted Publisher for owner +`eggstack`, repository `eggsearch`, workflow `release-python-pypi.yml`, and +pre-create the GitHub environment `pypi`. The workflow takes the exact candidate +SHA, successful Python qualification run ID, and synchronized package version. +It verifies the environment exists, checks the qualified source and artifact +inventory, then publishes with OIDC. Explicit workflow dispatch is the release +action; a required environment reviewer is not configured. + +Public install instructions are in `README.md` and `docs/python-library.md`. +ARMv7 support remains experimental until M004 provides physical-board evidence. +Physical SBC measurements happen after publication and do not block a future +Python release unless they reveal a compatibility defect. ## Publication and binary release diff --git a/plans/closure/python-pypi-distribution/003-status.md b/plans/closure/python-pypi-distribution/003-status.md new file mode 100644 index 0000000..5832589 --- /dev/null +++ b/plans/closure/python-pypi-distribution/003-status.md @@ -0,0 +1,61 @@ +# M003 — First PyPI Publication and Public Wheel Provenance Closure + +Status: closed +Candidate source: `1135608af5d625cd72db6704adf3bcabd1a58ab1` +Package: `eggsearch==0.4.4` +Implementation plan: `plans/implementation/python-pypi-distribution/003-first-pypi-release-and-provenance.md` +Roadmap: `plans/subsystems/python-pypi-distribution-roadmap.md` M003 +Publication workflow run: `40742653291` +Merged workflow commit: `2ac49f6e945f3d940218587f75c18a9c573abe9d` (PR #10) + +## Result + +The first Python distribution was published to [PyPI](https://pypi.org/project/eggsearch/0.4.4/) on 2026-10-28. The public project metadata reports name `eggsearch`, version `0.4.4`, and `Requires-Python >=3.11,<3.16`. PyPI serves exactly six ABI3 wheels and one source distribution. The PyPI SHA-256 digests match qualification run `40729011504` and the verified release manifest. + +The maintainer confirmed the PyPI Trusted Publisher and GitHub `pypi` environment were configured and directed that no required reviewer be used. The explicitly dispatched workflow verified that the environment existed, checked the exact qualified source and artifact inventory, and published with PyPI Trusted Publishing. The verification job, publication job, and every post-publication consumer job in run `40742653291` succeeded. No PyPI token or secret was used. + +## Requirement-to-evidence matrix + +| Requirement | Evidence | Result | +|---|---|---| +| Exact qualified source and synchronized version | Candidate `1135608af5d625cd72db6704adf3bcabd1a58ab1`; root, binding, and project manifests all report 0.4.4; workflow run `40742653291` checked candidate CI and Python qualification run `40729011504`. | Passed | +| M001/M002 exact-SHA qualification | Python native run `40729011504` passed all 34 jobs; root CI `40729011529`, release drift `40729011257`, and egress qualification `40729042102` passed. Closure records `001-status.md` and `002-status.md` hold the qualification matrix, audits, sdist rebuild, and ARMv7 ELF evidence. | Passed | +| Immutable release inventory | Workflow run `40742653291`, `Verify qualified source and artifact inventory` job; `verify_release_artifacts.py` accepted the six wheels, sdist, manifest, source SHA, qualification ID, and ARMv7 audit before publication. | Passed | +| Trusted publication and environment | Workflow run `40742653291`, `Manually dispatched PyPI publication` job succeeded using the configured OIDC publisher and pre-created `pypi` environment. No environment reviewer was configured, as explicitly directed by the maintainer; the manual workflow dispatch was the publication action. | Passed | +| Public package metadata and inventory | [PyPI 0.4.4 JSON](https://pypi.org/pypi/eggsearch/0.4.4/json), fetched after upload: expected name/version, Python range, six wheels, and one sdist. Public file digests and sizes are listed below. | Passed | +| Public binary-only consumer installation | Workflow run `40742653291` passed fresh installs with `--only-binary=:all: --no-deps` and `smoke_installed_wheel.py` on Linux x86_64, Linux aarch64, macOS x86_64, macOS arm64, and Windows x86_64 using CPython 3.15, plus emulated ARMv7 manylinux 2.31 using CPython 3.11. The smoke checks ten tools, malformed-input error handling, trusted local Mode-Off evidence, and closed-client behavior. Job logs record each public wheel URL and SHA-256; each matches the public PyPI JSON. | Passed | +| Consumer installation requirements | Consumers installed wheels directly from `files.pythonhosted.org`; no source build step ran, and pip was constrained to binary distributions. PyPI `Requires-Python` excludes unsupported interpreter versions. | Passed | +| Documentation and governance | README, Python library guide, binding README, architecture, release guide/checklist, roadmap, registry, and this closure record describe the published package and separate PyPI release path. | Passed | + +The consumer workflow also writes `pip debug --verbose` supported tags to each job summary. Native ARMv7 hardware has not been tested; ARMv7 remains explicitly experimental, with evidence limited to the published hard-float wheel and emulated installed-wheel smoke. + +## Published artifact inventory + +All sizes are bytes; SHA-256 values are from the public PyPI JSON response and were checked against the qualification manifest. + +| PyPI artifact | Size | SHA-256 | +|---|---:|---| +| `eggsearch-0.4.4-cp311-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl` | 9,461,830 | `96247b088c2ae924e49c459c5a29b7b9ac348c776a9c928e1eaafc09f032a4e0` | +| `eggsearch-0.4.4-cp311-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl` | 9,252,055 | `840e8689a9ec52d26e480f3946e8a389ad0bdab816940681a1431b2faea52ccb` | +| `eggsearch-0.4.4-cp311-abi3-macosx_10_12_x86_64.whl` | 8,727,305 | `cb5dd563ee71f1aa8844c4c454effad17c1838ce315c01f14776dbf2733db7ad` | +| `eggsearch-0.4.4-cp311-abi3-macosx_11_0_arm64.whl` | 8,498,057 | `adaadee8bd530f302b642a48886ca723f19c245c5249e107aa885a0cfe78349e` | +| `eggsearch-0.4.4-cp311-abi3-win_amd64.whl` | 8,327,031 | `62bedfea95581d906e5f4749310c2013a277754e05f177d93d4f08a271bc8340` | +| `eggsearch-0.4.4-cp311-abi3-manylinux_2_28_armv7l.whl` | 8,938,271 | `530c31f51018886caaa70659e037ed6ceff5a4d053f762ebef46f92c8ec82eb0` | +| `eggsearch-0.4.4.tar.gz` | 1,299,743 | `42e57e1c9a4ec02b97d715cc28f522e7effde2e1cb9d0ca43ee0fecaac7ae436` | + +Public native-consumer jobs reported these wheel identities: + +| Consumer | Public wheel SHA-256 | Result | +|---|---|---| +| Linux x86_64, CPython 3.15 | `96247b088c2ae924e49c459c5a29b7b9ac348c776a9c928e1eaafc09f032a4e0` | Passed | +| Linux aarch64, CPython 3.15 | `840e8689a9ec52d26e480f3946e8a389ad0bdab816940681a1431b2faea52ccb` | Passed | +| macOS x86_64, CPython 3.15 | `cb5dd563ee71f1aa8844c4c454effad17c1838ce315c01f14776dbf2733db7ad` | Passed | +| macOS arm64, CPython 3.15 | `adaadee8bd530f302b642a48886ca723f19c245c5249e107aa885a0cfe78349e` | Passed | +| Windows x86_64, CPython 3.15 | `62bedfea95581d906e5f4749310c2013a277754e05f177d93d4f08a271bc8340` | Passed | +| Emulated ARMv7 manylinux 2.31, CPython 3.11 | `530c31f51018886caaa70659e037ed6ceff5a4d053f762ebef46f92c8ec82eb0` | Passed; emulated | + +## Residuals and handoff + +The sdist is published for developer environments outside the wheel matrix; SBC instructions require `--only-binary=:all:` and do not permit on-device compilation. ARMv7 remains experimental because no physical board has been measured. M004 owns native aarch64/ARMv7 runtime benchmarking and is blocked only on access to physical SBC devices. No benchmark or optimization was performed before publication. + +M003 is closed. M004 is recorded separately in `004-status.md` once device evidence or an explicit hardware-access blocker is available. diff --git a/plans/implementation/python-pypi-distribution/003-first-pypi-release-and-provenance.md b/plans/implementation/python-pypi-distribution/003-first-pypi-release-and-provenance.md index 4d287e8..ede5533 100644 --- a/plans/implementation/python-pypi-distribution/003-first-pypi-release-and-provenance.md +++ b/plans/implementation/python-pypi-distribution/003-first-pypi-release-and-provenance.md @@ -1,6 +1,6 @@ # M003 — First Controlled PyPI Publication and Installed-Wheel Provenance -Status: active (workflow implemented; exact-SHA M001/M002 qualification passed; maintainer setup confirmed; awaiting default-branch workflow availability and publication) +Status: closed Primary class: capability Source: `plans/subsystems/python-pypi-distribution-roadmap.md` M003. Qualified release candidate: `1135608af5d625cd72db6704adf3bcabd1a58ab1`, Eggsearch 0.4.4. Closure-only plan/registry updates followed at `65fba70705b2657bb40063283ccd51f28d2e993d`; they do not change the package source. Keep the candidate SHA explicit if merge strategy rewrites the commit. @@ -12,11 +12,11 @@ User direction: the `eggsearch` PyPI name has been manually checked as available Publish the first `eggsearch` Python wheel+sdist inventory to PyPI, allowing `pip`/`uv` consumers to install **prebuilt** artifacts for the stated supported platforms including experimental ARMv7 SBC. Protect immutability, exact-source provenance, architectural tag honesty, and dependency integrity. The user explicitly directs that a required reviewer not be configured; explicit workflow dispatch is the publication action. A published wheel and independently successful binary-only PyPI install, not a passing build, establish the user-visible capability. -Current `bindings/python` is unpublished, `pyproject.toml` / Cargo manifests use version 0.4.4, and `.github/workflows/python-native-qualification.yml` is nonpublishing. Historical M008 candidate `067468a` qualified 0.4.3 with five wheels, 20 interpreter smokes, sdist rebuild and audit; new release bytes must be requalified. The root Rust publication sequence is controlled by Eggpack and remains unchanged. +`bindings/python` is published on PyPI as version 0.4.4; the qualification workflow remains nonpublishing. Historical M008 candidate `067468a` qualified 0.4.3 with five wheels, 20 interpreter smokes, sdist rebuild and audit; the 0.4.4 release bytes were independently requalified. The root Rust publication sequence is controlled by Eggpack and remains unchanged. Execution added `.github/workflows/release-python-pypi.yml`. It accepts an exact candidate SHA, successful qualification run ID, and synchronized version; checks exact-SHA root CI and Python qualification; requires the pre-created `pypi` environment to exist; downloads only that run's artifacts; verifies the six-wheel-plus-sdist inventory and hashes; and publishes only through the `pypi` environment with OIDC permission scoped to the publish job. Post-publication binary-only consumer jobs cover five native platforms and emulated ARMv7. -The selected candidate's M001/M002 acceptance is green: Python native qualification run `40729011504` passed all 34 jobs, root CI `40729011529` passed, egress qualification `40729042102` passed, and release drift run `40729011257` passed. The exact hosted artifact set was downloaded and accepted by `verify_release_artifacts.py`; hashes and the ARMv7 audit are recorded in `plans/closure/python-pypi-distribution/001-status.md` and `002-status.md`. No M003 release-workflow run or PyPI publication has been initiated. The maintainer confirmed that the PyPI Trusted Publisher and GitHub `pypi` environment are configured and directed that no required reviewer be used. The workflow verifies the environment exists before publication; manual workflow dispatch remains the explicit release action. +The selected candidate's M001/M002 acceptance is green: Python native qualification run `40729011504` passed all 34 jobs, root CI `40729011529` passed, egress qualification `40729042102` passed, and release drift run `40729011257` passed. The exact hosted artifact set was accepted by `verify_release_artifacts.py`; hashes and the ARMv7 audit are recorded in `plans/closure/python-pypi-distribution/001-status.md` and `002-status.md`. M003 publication run `40742653291` passed exact-source and inventory verification, PyPI Trusted Publishing, and all six public binary-only consumer jobs. The public package is `eggsearch==0.4.4`; full evidence is in `plans/closure/python-pypi-distribution/003-status.md`. The maintainer explicitly directed that no required reviewer be used; the manual workflow dispatch was the publication action. ## Non-goals and invariant boundaries @@ -40,4 +40,4 @@ A successful wheel upload with missing mandatory target, a wheel whose platform ## Verification and closure requirements -Run all M001/M002 checks at the chosen commit and complete an independently verified `pip install --only-binary=:all: eggsearch==` from **public PyPI**, with no compiler on consumers. Collect: exact source SHA/tag/ref; chosen version and name-ownership proof; final release inventory/hashes; M001/M002 qualification IDs and jobs; sdist extraction/audits; GitHub publish run and dispatch inputs, OIDC publisher/environment details without secrets; PyPI project/version URL; raw public wheel download/installed smoke evidence; wheel sizes; unsupported/experimental coverage statement; no SBC build or benchmark performed before release. Record in `plans/closure/python-pypi-distribution/003-status.md` with requirement-to-evidence matrix, classified residuals and recommendation. Update roadmap and registry in the same closure commit. **Only M003 publication closure** may declare Python package publicly available. +M003 acceptance is recorded in `plans/closure/python-pypi-distribution/003-status.md`: exact source and version; M001/M002 and root verification IDs; the complete public wheel/sdist inventory and hashes; OIDC publication run; public PyPI URLs and consumer wheel digests; five native and emulated ARMv7 installation results; experimental and unsupported coverage; and the fact that no SBC build or benchmark occurred before release. The roadmap and registry are updated in the closure commit. **Only M003 publication closure** may declare Python package publicly available. diff --git a/plans/implementation/python-pypi-distribution/004-post-publication-sbc-benchmarking.md b/plans/implementation/python-pypi-distribution/004-post-publication-sbc-benchmarking.md index 272bc16..79e8a58 100644 --- a/plans/implementation/python-pypi-distribution/004-post-publication-sbc-benchmarking.md +++ b/plans/implementation/python-pypi-distribution/004-post-publication-sbc-benchmarking.md @@ -1,9 +1,9 @@ # M004 — Post-Publication SBC Runtime Benchmarking and Resource Policy -Status: blocked (operational: M003 first PyPI publication must succeed) +Status: blocked (operational: native aarch64 and ARMv7 SBC device access is unavailable) Primary class: polish Source: `plans/subsystems/python-pypi-distribution-roadmap.md` M004. -Planning baseline: `main@13fcac0b7ac0125d38e4e9775ebe1d62028fda72`. A standard-library benchmark harness is prepared at `bindings/python/benchmarks/sbc_runtime.py`; it verifies the installed native extension against the public PyPI pip-report and wheel digest, requires ten unique tool names, validates trusted local Mode-Off search results and malformed-input rejection, uses a loopback-only fetch fixture, and records repeated sequential asyncio event loops. Actual execution must pin the **published** `eggsearch` Python version and its installed wheel hashes. +Planning baseline: `main@13fcac0b7ac0125d38e4e9775ebe1d62028fda72`. M003 published `eggsearch==0.4.4`; its M003 closure records exact wheel identities and emulated ARMv7 installation. A standard-library benchmark harness is prepared at `bindings/python/benchmarks/sbc_runtime.py`; it verifies the installed native extension against the public PyPI pip-report and wheel digest, requires ten unique tool names, validates trusted local Mode-Off search results and malformed-input rejection, uses a loopback-only fetch fixture, and records repeated sequential asyncio event loops. Actual execution must pin the published version and installed wheel hashes. Physical device access is the sole remaining operational blocker. Authority: ADR-0005, `architecture/python-library.md`, historical Python M002/M005 lifecycle guarantees and M003 release closure. Primary rule: **publish first; measure on SBCs later; never compile Eggsearch or its wheel on the device.** @@ -20,7 +20,7 @@ No device-local Rust build, `maturin develop`, Cargo source compilation, compile ## Ordered work packages 1. Select at least one native aarch64 Linux SBC and one ARMv7 32-bit Linux environment as hardware access allows (e.g., Pi 5-class aarch64, Le Potato/Raspberry Pi OS ARMv7 hard-float), recording `uname -m`, `/etc/os-release`, glibc or musl version, Python version, physical RAM, core count, storage, swap and thermal/power mode. Devices are consumer/benchmark hosts only. If ARMv7 hardware is temporarily unavailable, classify that evidence as **blocked post-release**, without retroactively blocking M003. -2. Install **only the exact published wheel**, `python -m pip install --only-binary=:all: eggsearch==`, confirm download URL/digest and `importlib.metadata`; instrument package import and each benchmark from a fresh process. Refuse a source distribution, ensure no Cargo/compiler invocation. Use a lightweight Python standard-library measurement harness (e.g., `time.perf_counter_ns`, `resource.getrusage`, `tracemalloc` for Python allocations, Linux `/proc/self/status`, `/proc//smaps_rollup` for native RSS/PSS); optional `psutil` is not required. +2. Install **only the exact published wheel** and retain both the wheel and pip install report. For the current M003 release, use `python -m pip download --only-binary=:all: --no-deps --dest wheelhouse eggsearch==0.4.4`, then `python -m pip install --only-binary=:all: --no-deps --report pip-report.json eggsearch==0.4.4`. Confirm the public URL/digest and `importlib.metadata`; the harness checks the installed extension against the local wheel, the pip report, version `0.4.4`, and qualified source `1135608af5d625cd72db6704adf3bcabd1a58ab1`. Run `python bindings/python/benchmarks/sbc_runtime.py --version 0.4.4 --source-sha 1135608af5d625cd72db6704adf3bcabd1a58ab1 --wheel wheelhouse/.whl --pip-report pip-report.json --output sbc-runtime.json` from a fresh process. Refuse a source distribution and ensure no Cargo/compiler invocation. The standard-library harness measures `time.perf_counter_ns`, `resource.getrusage`, `tracemalloc` for Python allocations, Linux `/proc/self/status`, and `/proc/self/smaps_rollup` for native RSS/PSS; optional `psutil` is not required. 3. Measure cold import and first Tokio initialization separately, initialization with default vs explicit Mode-Off config, idle RSS/PSS, memory after sequential search/fetch fixtures, 1/2/4/8/16/32 concurrent bounded calls, cancellation/drain latency, per-client close, sequential `asyncio.run` loops, and heavy-output JSON conversion near defined budget caps. Prefer deterministic local/recorded fixtures; external live-provider performance is a separate optional observation with provider failure context. 4. Capture CPU time, wall-time distributions (median, p95 and spread across repeated runs), peak RSS/PSS, thread counts, process FD count, total memory headroom, disk wheel footprint and observable thermal throttling. Vary default process-concurrency realistically, keep tests short and bounded, and use the same scenario configuration when comparing ARMv7/aarch64. Report exact command and metadata, not just averaged headline numbers. 5. Analyze whether fixed four Tokio workers/eight blocking threads or 32-admission budget is unnecessarily expensive on 1–2-core/low-memory hardware. If evidence supports adaptation, propose the narrowest backwards-compatible config/runtime setting, explicit default behavior, bounded lower/upper values and tests proving continued operation on larger hosts. Treat tuning as a **separate corrective/optimization plan and patch release**, not an unreviewed change to the published baseline. diff --git a/plans/registry.md b/plans/registry.md index 9bde7c5..b5d6113 100644 --- a/plans/registry.md +++ b/plans/registry.md @@ -43,7 +43,7 @@ Historical `phase-*.md` plans and pre-migration roadmaps are archived under | Dependency evidence hardening | closed | `plans/subsystems/dependency-evidence-hardening-roadmap.md` | M010 corrective closed | M001-M010 closed. Current control point `plans/closure/dependency-evidence-hardening/010-status.md`; implementation `23676cc`, CI `36253474005`. | | Repository security, supply-chain, and maintenance hardening | active | `plans/subsystems/repository-hardening-roadmap.md` | M001/M002/M007/M008/M009/M010 closed; M006 blocked | Scheduled dependency-security run `38290328560` succeeded; M010 records M001/M007 closure. M002 closed by M009; M006 remains externally blocked on chromiumoxide. | | Python native library for agents | closed (M001-M008 closed; unpublished by design) | `plans/subsystems/python-native-library-roadmap.md` | M008 closed at `067468a`, qualifying run `38641009246` (27/27 incl. audit) | ADR-0005 accepted. Runs `38522548258`, `38608502185`/`38611932990`/`38614592873`, `38637266178`, and `38638066765` are historical/deficiency/supporting evidence only. Publication separately authorized. | -| Python PyPI distribution and prebuilt SBC wheels | active (M001/M002 closed; M003 active; M004 blocked) | `plans/subsystems/python-pypi-distribution-roadmap.md` | M001/M002 closed at `1135608af5d625cd72db6704adf3bcabd1a58ab1`; qualification run `40729011504` and exact artifact verifier passed. M003 gated release workflow is implemented; M004 benchmark harness is prepared | Historical Python M001-M008 stay closed. Maintainer must configure the PyPI Trusted Publisher and GitHub `pypi` approval environment before M003 publication. Do not compile on SBCs; physical SBC benchmarking starts after publication. | +| Python PyPI distribution and prebuilt SBC wheels | active (M001–M003 closed; M004 blocked on devices) | `plans/subsystems/python-pypi-distribution-roadmap.md` | M001/M002 closed at `1135608af5d625cd72db6704adf3bcabd1a58ab1`; M003 published 0.4.4 and passed all public consumers in run `40742653291`; closure `plans/closure/python-pypi-distribution/003-status.md` | Historical Python M001–M008 stay closed. Do not compile on SBCs; M004 needs native aarch64/ARMv7 device access. | ## Dependency-ready implementation plans @@ -51,8 +51,8 @@ Historical `phase-*.md` plans and pre-migration roadmaps are archived under |---|---|---|---|---| | Python PyPI distribution | M001 Python 3.15 / PyO3 ABI3 requalification | closed | `plans/implementation/python-pypi-distribution/001-python315-toolchain-and-abi3.md` | Closed at `1135608af5d625cd72db6704adf3bcabd1a58ab1`; closure `plans/closure/python-pypi-distribution/001-status.md`; exact-SHA run `40729011504` passed 25/25 smoke cells. No publication. | | Python PyPI distribution | M002 hosted ARMv7 and Linux wheel expansion | closed | `plans/implementation/python-pypi-distribution/002-hosted-armv7-and-linux-wheel-expansion.md` | Closed at `1135608af5d625cd72db6704adf3bcabd1a58ab1`; closure `plans/closure/python-pypi-distribution/002-status.md`; hosted ELF/tag audit and CPython 3.11/3.15 QEMU installed-wheel tests passed. Optional musllinux deferred. **No SBC compilation**. | -| Python PyPI distribution | M003 controlled first PyPI release | **active** (publish gated) | `plans/implementation/python-pypi-distribution/003-first-pypi-release-and-provenance.md` | Candidate `1135608af5d625cd72db6704adf3bcabd1a58ab1` qualified (Python run `40729011504`, root CI `40729011529`, egress `40729042102`); exact six-wheel/sdist verifier passed. Requires PyPI Trusted Publisher and reviewed GitHub `pypi` environment setup before dispatch. | -| Python PyPI distribution | M004 physical SBC benchmarking after publication | **blocked** | `plans/implementation/python-pypi-distribution/004-post-publication-sbc-benchmarking.md` | Operational blocker: M003 public PyPI release. No pre-publication SBC build/benchmark. | +| Python PyPI distribution | M003 controlled first PyPI release | closed | `plans/implementation/python-pypi-distribution/003-first-pypi-release-and-provenance.md` | Candidate `1135608af5d625cd72db6704adf3bcabd1a58ab1`; publication run `40742653291`; closure `plans/closure/python-pypi-distribution/003-status.md`; six public binary-only consumer jobs passed. | +| Python PyPI distribution | M004 physical SBC benchmarking after publication | **blocked** | `plans/implementation/python-pypi-distribution/004-post-publication-sbc-benchmarking.md` | Operational blocker is access to native aarch64 and ARMv7 SBCs. M003 publication succeeded; no pre-publication SBC build/benchmark. | | Eggpack release adoption | M001 seven-target Eggpack producer cutover | closed | `plans/implementation/eggpack-release-adoption/001-seven-target-eggpack-producer-cutover.md` | Paired producer plan `eggstack/eggpack: plans/implementation/ecosystem-adoption/003b-eggsearch-seven-target-eggpack-producer-cutover.md` (`325d44e`). Implementation `eabbf80`; run `37531104901`; draft `405157598`; provenance `37561960304`; published 2026-10-07. Eggpack production code was not edited | | CodeGG legacy search parity corrective | M001 keyless/source-specific provider parity | closed | `plans/implementation/codegg-legacy-search-parity/001-keyless-source-provider-parity.md` | Closed at `e9103b4`; closure `plans/closure/codegg-legacy-search-parity/001-status.md`. Added Wikipedia, arXiv, PubMed, HN Algolia, and GitHub repository discovery plus the additive `structured_api` provider kind; inventory 37 -> 42. | | CodeGG legacy search parity corrective | M002 credentialed provider parity | closed | `plans/implementation/codegg-legacy-search-parity/002-credentialed-provider-parity.md` | Closed at `5233315`; closure `plans/closure/codegg-legacy-search-parity/002-status.md`. Added opt-in `serpapi` and `kagi` (current v1, terms gate passed); inventory 42 -> 44. | @@ -109,7 +109,7 @@ Corrective closure sequence: `plans/implementation/dependency-evidence-hardening ## Current execution order and dependency gates -**Python native library gate:** ADR-0005 authorizes a narrow direct Rust SDK facade and Python PyO3 native package without broad Rust module stability. M001-M008 are closed at `067468a` with fully-green qualifying run `38641009246` (5/5 builds, 20/20 smokes, offline sdist rebuild, green audit, digests in `008-status.md`). Earlier runs are historical/deficiency/supporting evidence only. Initial Python qualification was nonpublishing; first PyPI publication is now separately planned under `python-pypi-distribution` M003 with explicit human release approval. Eggpack binary assets remain unchanged. +**Python native library gate:** ADR-0005 authorizes a narrow direct Rust SDK facade and Python PyO3 native package without broad Rust module stability. M001–M008 are closed at `067468a` with fully-green qualifying run `38641009246` (5/5 builds, 20/20 smokes, offline sdist rebuild, green audit, digests in `008-status.md`). Earlier runs are historical/deficiency/supporting evidence only. First PyPI publication is separately closed under `python-pypi-distribution` M003 at 0.4.4; Eggpack binary assets remain unchanged. **Tool-surface gate:** M001-M007 closed. Do not run evaluation against pre-consolidation bytes and present it as consolidation @@ -183,7 +183,7 @@ release that makes HTTP discovery / reqwest optional without regressing | CodeGG legacy search parity | closed; M001 through M005 closed | `plans/closure/codegg-legacy-search-parity/005-status.md`; prior control points `plans/closure/codegg-legacy-search-parity/004-status.md` and `003-status.md`; implementations `e9103b4` (M001), `5233315` (M002), `8e5ec75` (M003), `81a2e49` (M004 release-prep), `32769d6` (M005 fix-prep); historical provider-parity closure retained, new Mode-Off locality issue separately registered | | Mode-Off local repository dispatch corrective | closed; M001-M003 closed | M001 closure `001-status.md`; M003 hosted qualification `38476463235`; M002 immutable crate/tag/release `v0.4.3`, producer run `38480449328`, provenance run `38483437078`, and closure `002-status.md`. CodeGG paired requalification remains consumer-owned. | | Python native library | closed; M001-M008 closed | `plans/subsystems/python-native-library-roadmap.md`; closure records `001-status.md`–`008-status.md`; M008 closed at `067468a`, run `38641009246`; unpublished by design | -| Python PyPI distribution | active; M001/M002 closed, M003 active, M004 blocked | `plans/subsystems/python-pypi-distribution-roadmap.md`; M001/M002 closed at `1135608af5d625cd72db6704adf3bcabd1a58ab1` with exact-SHA hosted qualification; M003 publication waits on PyPI/GitHub setup; M004 benchmark harness is prepared and hardware evidence follows publication | +| Python PyPI distribution | active; M001–M003 closed, M004 blocked | `plans/subsystems/python-pypi-distribution-roadmap.md`; M001/M002 exact-SHA qualification at `1135608af5d625cd72db6704adf3bcabd1a58ab1`; M003 public release and consumer run `40742653291`; M004 harness prepared, pending native aarch64/ARMv7 devices | ## Closure rule diff --git a/plans/subsystems/python-pypi-distribution-roadmap.md b/plans/subsystems/python-pypi-distribution-roadmap.md index 68ae52f..7589a1d 100644 --- a/plans/subsystems/python-pypi-distribution-roadmap.md +++ b/plans/subsystems/python-pypi-distribution-roadmap.md @@ -1,6 +1,6 @@ # Python PyPI Distribution and Prebuilt SBC Wheels Roadmap -Status: active (M001/M002 closed; M003 active; M004 blocked on first PyPI publication and native-device access) +Status: active (M001–M003 closed; M004 blocked on native-device access) Primary outcome: publish the existing in-process `eggsearch` Python package promptly, with CPython 3.11–3.15 and broad precompiled platform wheels, explicitly experimental SBC support, then perform hardware benchmarking **after publication**. Planning baseline: `main` `13fcac0b7ac0125d38e4e9775ebe1d62028fda72` (2026-10-28; root/binding/pyproject 0.4.4). Refresh the baseline at execution. Authority: user confirmed the `eggsearch` PyPI project name is available by manual check and requested a release-first sequence without compiling on SBCs. @@ -39,10 +39,10 @@ The term *experimental SBC support* covers hardware-model/runtime/footprint unce |---|---|---|---|---| | M001 Python 3.15 and binding toolchain qualification | closed | hard: historical Python M008 closed | Closed at `1135608af5d625cd72db6704adf3bcabd1a58ab1`; exact-SHA qualification run `40729011504` passed all 25 CPython 3.11–3.15 cells across the five existing platform families. Closure: `plans/closure/python-pypi-distribution/001-status.md`. | | M002 hosted ARMv7 and Linux wheel expansion | closed | interface: M001 keeps `abi3-py311` stable; operational integration before M003 | Closed at `1135608af5d625cd72db6704adf3bcabd1a58ab1`; hosted ARMv7 hard-float build, ELF audit and CPython 3.11/3.15 QEMU installs passed in run `40729011504`. No SBC compilation; optional musllinux remains deferred. Closure: `plans/closure/python-pypi-distribution/002-status.md`. | -| M003 controlled PyPI first publication | active (publication gated) | interface: established M001/M002 artifact contracts; operational: M001/M002 qualification and exact candidate | Trusted Publisher configured; exact-SHA wheel/sdist set passes audits and clean consumers; operator publishes `eggsearch` to PyPI and independently verifies public binary-only installs. Workflow and exact-SHA artifacts are ready; PyPI Trusted Publisher and GitHub `pypi` approval environment setup remain. | -| M004 post-publication SBC benchmarking and tuning decision | blocked | operational: successful M003 publication and native ARMv7/aarch64 device access | Native SBC installed-wheel benchmarks for memory, latency and concurrency; no source compilation; evidence-based recommendations/patch release only if needed. The standard-library harness is prepared. | +| M003 controlled PyPI first publication | closed | interface: established M001/M002 artifact contracts; operational: M001/M002 qualification and exact candidate | Published `eggsearch==0.4.4` from candidate `1135608af5d625cd72db6704adf3bcabd1a58ab1`; workflow `40742653291` passed source/artifact verification, OIDC upload, and public binary-only installs on five native families plus emulated ARMv7. Closure: `plans/closure/python-pypi-distribution/003-status.md`. | +| M004 post-publication SBC benchmarking and tuning decision | blocked | operational: native ARMv7/aarch64 device access | Benchmark the public 0.4.4 wheels on native SBCs; no source compilation; evidence-based recommendations/patch release only if needed. The standard-library harness is prepared. | -M001 and M002 are closed against the exact release candidate; the M003 workflow implementation is ready. The **M003 publish action** is gated on maintainer configuration of the PyPI Trusted Publisher and the GitHub `pypi` approval environment. M004 benchmarking is deliberately scheduled **after** publication; a device not immediately available is not a retroactive blocker for M003. +M001–M003 are closed. The first public release was manually dispatched through the configured PyPI Trusted Publisher and pre-created GitHub `pypi` environment; the maintainer directed that no required reviewer be used. M004 benchmarking is deliberately scheduled **after** publication; lack of native hardware access blocks only M004 and does not affect M003 closure. Implementation handoffs: `plans/implementation/python-pypi-distribution/001-python315-toolchain-and-abi3.md` through `004-post-publication-sbc-benchmarking.md`. Closure records go to `plans/closure/python-pypi-distribution/NNN-status.md`. Keep the registry aligned. @@ -50,4 +50,4 @@ Implementation handoffs: `plans/implementation/python-pypi-distribution/001-pyth Record exact full commit SHA, frozen version, wheel names/tags, hashes, host/emulator architecture, build/audit tools and CI run IDs. Run `make check`, `make packaging-check`, `cargo publish --dry-run --locked` when tree cleanliness permits, binding `pytest`/type checks, sdist extraction/rebuild, and actual installation from the *selected final* wheelhouse with `--only-binary=:all: --no-deps --no-index`. Runtime tests must cover all ten operations, configuration policy, no-network Mode-Off, lifecycle/cancellation and import without side effects. An experimental ARMv7 wheel must at least pass a release-installed smoke under emulation; full physical-SBC performance and long-duration soak are M004. -Risks: cross-ABI interpreter discovery, glibc floor/correct `armv7l` tagging, host runner/emulator availability, PyO3 ABI compatibility with 3.15, and upstream audit findings. Any incompatibility must be visible as a blocked requirement with the exact failing evidence. Publication requires human-controlled approval (GitHub environment) and immutable PyPI version handling; a failed upload cannot be overwritten. +Risks: cross-ABI interpreter discovery, glibc floor/correct `armv7l` tagging, host runner/emulator availability, PyO3 ABI compatibility with 3.15, and upstream audit findings. Any incompatibility must be visible as a blocked requirement with the exact failing evidence. Python publication uses explicit manual workflow dispatch, OIDC Trusted Publishing, and immutable PyPI version handling; a failed upload cannot be overwritten.