# Changelog

## Score

- CAI 62 → 70 (+7.9)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 75 → 75 (-0.0)
- Architecture 71 → 78 (+7.2)
- Maturity 52 → 81 (+28.5)
- Readiness 70 → 64 (-6.1)
- Security 64 → 68 (+4.2)
- Domain Modelling 100 → 100 (+0.0)
- Performance 100 → 100 (+0.0)

## Resolved (9)

- Documentation: no project overview (examples/hybrid-kem-settlement/README.md)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- Inconsistent naming and scope of verification methods. `validateSpendProofStructure` and `verifySpendProofStructure` appear to do similar structural checks but have different names and potentially different inputs (one takes just proof, the other takes proof + output). `verifyMerkleProof` is a specific subset. The distinction between 'validate' and 'verify' is unclear and inconsistent with other parts of the API (e.g., `MerkleTree.verify` vs `MerkleTree.verifyHash`).
- Multiple entry points for SHA-256 hashing with inconsistent naming and signatures. `crypto.sha256hex` and `HashingPort.sha256hex` are identical. `CommitmentProvider` also exposes `sha256hex`. This creates confusion about which utility to use and duplicates functionality across different modules (shared, p2mr, mpc).
- Redundant verification methods with overlapping intent. `verify` computes the hash of the leaf internally, while `verifyHash` expects the hash. This forces callers to either duplicate hashing logic or choose between two nearly identical methods based on an implementation detail.
- Split packages/enterprise-blockchain

## New (81)

- Banned license: @img/sharp-libvips-darwin-arm64 (demo/package-lock.json)
- Banned license: @img/sharp-libvips-darwin-x64 (demo/package-lock.json)
- Banned license: @img/sharp-libvips-linux-arm (demo/package-lock.json)
- Banned license: @img/sharp-libvips-linux-arm64 (demo/package-lock.json)
- Banned license: @img/sharp-libvips-linux-ppc64 (demo/package-lock.json)
- Banned license: @img/sharp-libvips-linux-riscv64 (demo/package-lock.json)
- Banned license: @img/sharp-libvips-linux-s390x (demo/package-lock.json)
- Banned license: @img/sharp-libvips-linux-x64 (demo/package-lock.json)
- Banned license: @img/sharp-libvips-linuxmusl-arm64 (demo/package-lock.json)
- Banned license: @img/sharp-libvips-linuxmusl-x64 (demo/package-lock.json)
- Banned license: @img/sharp-wasm32 (demo/package-lock.json)
- Banned license: @img/sharp-win32-arm64 (demo/package-lock.json)
- Banned license: @img/sharp-win32-ia32 (demo/package-lock.json)
- Banned license: @img/sharp-win32-x64 (demo/package-lock.json)
- Classify ADR enforcement: ADR-0001: Hexagonal Architecture with Domain-Driven Design (docs/adr/ADR-0001-hexagonal-architecture.md)
- Classify ADR enforcement: ADR-0002: Protocol Adapter Pattern for Multi-Blockchain Support (docs/adr/ADR-0002-protocol-adapter-pattern.md)
- Classify ADR enforcement: ADR-0003: Hybrid KEM for Post-Quantum Transition (docs/adr/ADR-0003-hybrid-kem-design.md)
- Classify ADR enforcement: ADR-0004: Field Arithmetic Parameters for MPC (docs/adr/ADR-0004-field-arithmetic-for-mpc.md)
- Classify ADR enforcement: ADR-0005: P2MR (Pay-to-Merkle-Root) Quantum-Safe Outputs (docs/adr/ADR-0005-p2mr-merkle-root-outputs.md)
- Critical CVE: [GHSA redacted] (package-lock.json)
- …and 61 more

## Architecture

- Unchanged — 0 containers · 1 contexts · 0 edges
