You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix the three red binding/pages CI workflows (all pre-existing)
python-binding, wasm-binding, and pages had been red since the bindings
landed (2026-05-20) — none related to the 0.5 crypto work. Root causes:
Code drift vs the current pqf-reader API (the real CI compile errors):
- Both bindings referenced a removed `Header.alg` field. The reader
validates then discards the alg identifiers, so a parsed header is
guaranteed conformant. Expose them as canonical pub consts
(ALG_AEAD/COMBINER/KDF/KEM/SIG) from pqf-reader and have both bindings
report those — single source of truth, no re-drift.
- wasm: chunk_size is u64 (cast to u32 for the JS view).
- python: SignerEntry fields are ed25519_pub/mldsa87_pub, not
classical_pub/pqc_pub (kept the spec-named dict keys).
Build-config fixes:
- wasm: aes-gcm pulls getrandom 0.2, which needs the "js" feature on
wasm32-unknown-unknown.
- python: pyo3 0.22 gates the &PyDict/&PyBytes GIL-ref API this binding
uses behind the "gil-refs" feature.
- python: pyproject license pointed at ../../LICENSE (outside the project);
newer maturin rejects it — use the SPDX `license = "MIT"` string.
- python-binding.yml: `maturin develop` needs an active virtualenv; create
and activate one (cross-platform). Also update the smoke-test combiner
assertion to pqf1-bind-extract-v1.
Verified locally: reader conformance still 47/47; wasm builds for
wasm32-unknown-unknown; python `maturin develop` + smoke parses and
decrypts TV-001 (4291 bytes) under the new bind-extract crypto.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments