qector-release-engineeringlisted

# QECTOR Release Engineering Source of authority: v1.0.0 reference manual, chapter 25; the plugin-side release gates in `RELEASE_VALIDATION.md` driven by `scripts/build_release.py` and `scripts/release_validate.py`. The manual also cites `docs/RELEASING.md` (decoder tree) and `docs/API_STABILITY.md` — those live in the upstream decoder source tree, not in this plugin repository. ## Wheels only (manual 25.1) - The package publishes **deterministic binary wheels only**. - **No source distribution is published**, by design: the proprietary Rust core is not tracked as source, and an sdist cannot be rebuilt. - `pip install` must resolve to a wheel on every supported platform. - The plugin-side release procedure lives in `RELEASE_VALIDATION.md`; upstream wheel-release steps remain in the decoder tree's own `docs/RELEASING.md`. ## The core delivery path (manual 25.2) The Rust core is delivered to the build pipeline through a **chunked, hash-anchored packaging mechanism**: - 12 base64 chunks - a tracked manifest digest - the pipeline verifies the manifest against the packed core before building, so a stale or corrupted core fails the build explicitly rather than silently shipping older source This mechanism is build infrastructure; the chunks and digest are not reproduced in the manual. ## Feature flags in published wheels (manual 25.3) - Published wheels are built with the **CUDA feature only**. - CUDA support ships; OpenCL does not. - Both backends load their