[mm9942]

Summary

Supersedes #24: contains its commits (M0-min/M0-ext building blocks and the reviewed pq_cascade state a29b8b6 from the comnet workflow) plus the fixes needed to build, the RustSec dependency updates, and the plan documents for the next crates. GitHub Actions in this repository currently fails every job after about one second without reaching a runner (runner_id 0, see the comment below), so verification was done locally.

Build fixes

• tests/ml_dsa_seed_context.rs: gated on ml-dsa-backend (the legacy-pqclean lane builds without it).
• crates/core/src/lib.rs: rustfmt module order.
• .gitignore: track docs/**/*.md.
• The intermediate revert of pq_multi (993f714) is superseded by the merge of a29b8b6, which ships pq_cascade.rs together with the cascade functions of pq_multi.

Dependency updates (cargo deny, RustSec)

• p256/p384 =0.13 → =0.14.0 (ecdh feature, ToSec1Point): the hybrid PQ KEMs leave crypto-bigint 0.5 (RUSTSEC-2026-0387). Wire bytes and pinned vectors unchanged.
• zip 2 → 9 (feature zip): RUSTSEC-2026-0367/0368/0369; via it zstd 0.14.3/zstd-safe 8.2.0 (RUSTSEC-2026-0391/0398/0403). ZipFile::name now returns a Result; archive tests adapted.
• Lockfile: tokio 1.54.1 (RUSTSEC-2026-0386), ctutils 0.4.7 (RUSTSEC-2026-0385), zstd-sys 2.1.2 (RUSTSEC-2026-0410).
• deny.toml: bzip2-1.0.6 licence allowed (libbz2-rs-sys behind zip); RUSTSEC-2026-0387 accepted only for the remaining path hpke 0.13 → p256/p384 0.13 (classical DHKEM suites), reason recorded. Clearing it needs the hpke 0.15 migration (rand_core 0.10, aead 0.6, sha2 0.11, x25519-dalek 3), documented as open in CHANGELOG and SECURITY.md.

Plans (docs only, nothing implemented)

• docs/plans/crypt-guard-pyo3-contract.md: Python bindings crate.
• docs/plans/crypt-guard-kms-contract.md: crypt_guard_keystore (handle-based Kek/KekProvider, OS backends for Linux/macOS/Windows) and crypt_guard_kms (CGKS container with rollback guard, SealedProvider, HTTP API, streamable-HTTP MCP, mTLS, UNIX-socket identity via SO_PEERCRED+SO_PEERPIDFD+cgroup v2, public-key directory, optional arti). Aligned with the comnet and Harwness sessions.
• docs/decisions/DEC-101: layout and lint contract for the new crates.

Open decision for the maintainer

• polyval = { features = ["zeroize"] } for the AES-256-GCM-SIV layer of pq_cascade (helps only the portable backend, see SECURITY.md). Not set in this PR.

Verification (local, Rust 1.97, head a67a570 code / 6a3b3c4 docs)

All 19 lanes pass: cargo fmt --check; clippy -D warnings with --all-features and with default features; the 10 cargo test lanes of rust.yml (including tests/pq_cascade_kats.rs, the module's unit tests and doctests); per-feature cargo check matrix; examples; fuzz-target check; scripts/check_dep_gates.sh; vector provenance; cargo deny check (advisories, bans, licences, sources all ok).

🤖 Generated with Claude Code

https://claude.ai/code/session_01Uh7jkDG5sDvfZRz5J21a2N

[mm9942]

CI status on 8b97e77: red, but not because of this PR.

All 14 jobs of run 41313938409 were created and marked failed within one second (started_at 13:59:55, completed_at 13:59:56, runner_id 0, no log available). The same pattern hit every run on #24 since 2026-11-01 02:04 (runs 109 to 112), while the last main run (108, 2026-09-27) was green with the same workflow file. The workflow never reached a runner, so this is a GitHub Actions account/billing or runner-availability problem of the repository, not a build failure. It cannot be fixed from a PR, and I have no way to re-run jobs from this session.

What was verified instead, locally on this head with Rust 1.97: every lane of rust.yml passes: cargo fmt --check, clippy -D warnings with --all-features and with default features, the ten cargo test lanes, the per-feature cargo check matrix, examples, fuzz-target check, scripts/check_dep_gates.sh, and the vector provenance script. cargo deny check result follows in the PR description once it finishes.

Action needed from the repository owner: check Settings → Billing → Actions (spending limit / payment) or Settings → Actions → General (runners enabled). As soon as runs start reaching a runner, the next push or a re-run will show the real status.

---

Generated by Claude Code