# Changelog

## Score

- CAI 47 → 47 (+0.3)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 81 → 81 (+0.0)
- Architecture 94 → 94 (+0.0)
- Maturity 70 → 78 (+8.6)
- Readiness 68 → 68 (+0.0)
- Security 46 → 44 (-2.5)
- Accessibility 29 → 30 (+0.7)
- Performance 100 → 100 (+0.0)

## Resolved (3)

- Inconsistent constructor patterns for encrypted vs unencrypted storage. WalEventStore, WalWriter, and WalScanner all use distinct method names (open vs open_encrypted) for the same logical operation with different security levels. While this is a common pattern, it is inconsistent with the rest of the API which tends to use constructors or single methods with optional parameters. More importantly, WalEventStore and WalScanner do not take a 'start_seq' in their open methods, whereas WalWriter does, leading to inconsistent state initialization requirements across similar components.
- Inconsistent parameterization for compaction. WalEventStore requires an explicit 'frontier' argument to define the compaction boundary, while ZamEngine.compact() takes no arguments, implying it either uses a default or manages the frontier internally. This creates confusion about whether the engine's compact method delegates to the store with a specific frontier or a different logic.
- Inconsistent peer acceptance strategy. TcpTransport has both accept_peer (specific) and accept_any (generic) methods, while TlsTcpTransport only has accept_any. This suggests a missing feature in the TLS transport or an inconsistency in how peer identity is verified during the connection acceptance phase.

## New (14)

- Medium advisory (unsound): RUSTSEC-2026-0386 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0395 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0396 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0397 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0399 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0400 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0401 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0402 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0404 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0405 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0406 (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0391 (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0398 (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0410 (Cargo.lock)
