[easel]

Weft's Python binding previously had only local builds. This prepares weft-sql 0.4.2 wheels with the owner-selected MIT OR Apache-2.0 license, both packaged licenses and dependency notices, and explicit 0.4.1/0.4.2 candidate APIs alongside the existing generic compiler composition.

The workflow builds macOS ARM64/Intel, manylinux2014 ARM64/x86_64 and Windows x64 wheels, then installs each on conventional GIL CPython 3.9–3.14. Installed-wheel checks verify RECORD/native payload/license custody and replay 2,181 ordinary plus 174 candidate/control response objects with deterministic repeats and subprocess calls disabled during compilation. Separate manual jobs prepare PyPI Trusted Publishing and a regular GitHub release with checksums and validation reports.

Validation: all five wheel builds and all 30 hosted interpreter checks passed in run 38191803413 at 0e2d76d94f0c1accb449bf9dc703618ceaaa0906. Local checks also passed 637 workspace tests, 51 tests for the exact runtime feature composition, and all 16 module-boundary negative controls. The release scripts are declared in the governed host-tool inventory. Full compiler conformance also passed in run 38191803398. Regular GitHub release v0.4.2 is published at that exact source commit with all five wheels, SHA256SUMS, the validation summary and 30 installed-wheel reports.

Current source retains 53 changed ordinary outputs requiring native requalification. Candidate APIs stay experimental, protected-read activation stays blocked, and no broader production storage/engine support is claimed. The owner authorized a regular v0.4.2 GitHub release with validated wheel assets. PyPI account/pending publisher setup remains outstanding. The unrelated older local checkout and unfinished security work are untouched.

Recovery disposition — 2026-10-16

Current release integration is merged in #15 (685691d3f7e2b9cd98285c74a56a6707a7b01cfd). Compatible project/package licensing, metadata, dependency notices and exact installed-wheel RECORD/ABI checks were ported into the current five-platform release workflow. Its newer native, Date, Decimal and refinement gates remain intact.

The original 0e2d76d94f0c1accb449bf9dc703618ceaaa0906 branch is retained unchanged. The recovery packet preserves original packaging bytes and explicitly records the historical 0.4.2/30-interpreter-check workflow. Those historical version defaults and corpus expectations are archived rather than restored over the current compiler, and their results are not promoted to 0.4.40. This older release-preparation PR is superseded; current public publication still requires its recorded full CI and five-platform gates.