# Changelog

## Score

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

## Lenses

- Code Health 70 → 70 (+0.0)
- Architecture 95 → 92 (-2.6)
- Maturity 64 → 69 (+4.5)
- Readiness 60 → 60 (+0.0)
- Security 55 → 54 (-1.9)
- Performance 87 → 87 (+0.0)

## Resolved (16)

- Ambiguous 'force' semantics. 'force_delete' implies a different behavior than 'delete', but the API does not expose what that difference is (e.g., bypassing checks, immediate removal). This creates a cognitive load to determine when to use which.
- Ambiguous loading behavior. 'load_default_or_new' suggests a specific fallback logic, while 'load' takes an optional path. It is unclear if 'load' with no path behaves the same as 'load_default_or_new'.
- Conflicting delete semantics. 'delete_cluster' returns the deleted config object, while 'delete_cluster_check' returns a Result. It is unclear if 'check' implies validation before deletion or if they are alternative implementations.
- Critical CVE: [GHSA redacted] (Cargo.lock)
- Documentation: no project overview (crates/fluvio/README.md)
- Inconsistent connection entry points. FluvioAdmin and Fluvio both offer connect() and connect_with_config(), but Fluvio adds a third connect_with_profile() variant while FluvioAdmin does not. This forces users to remember which client supports profile-based connection directly.
- Inconsistent return types for watch operations. 'watch()' returns a generic Result (likely blocking or returning a generic stream), while specific watchers return typed streams. This breaks the principle of least surprise for stream-based APIs.
- Medium vulnerability: RUSTSEC-2026-0346 (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0367 (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0367 (Cargo.lock)
- Off-boarding risk: anonymized user #1
- Proliferation of listing methods. 'all()', 'list()', 'list_with_params()', and 'list_with_config()' offer overlapping functionality. 'all()' is likely a no-filter 'list()', and 'list_with_params' vs 'list_with_config' is confusingly similar.
- Redundant creation methods with unclear distinction. 'create' takes individual parameters (name, dry_run, spec) while 'create_with_config' takes a request object. It is unclear if 'create' is a convenience wrapper or if they handle different validation/execution paths.
- Split crates/fluvio-cli
- Split crates/fluvio-sc
- Split crates/fluvio-spu

## New (29)

- Classify ADR enforcement: Add partition (rfc/add-partition.md)
- Classify ADR enforcement: Enhancing Fluvio Message Sizes (rfc/produce-message-size.md)
- Classify ADR enforcement: materialize_view (rfc/materialize_view.md)
- Classify ADR enforcement: offset-management (rfc/offset-management.md)
- Critical CVE: [GHSA redacted] (Cargo.lock)
- Critical CVE: [GHSA redacted] (Cargo.lock)
- Critical CVE: [GHSA redacted] (Cargo.lock)
- Medium CVE: [GHSA redacted] (Cargo.lock)
- Medium advisory (unmaintained): RUSTSEC-2026-0441 (Cargo.lock)
- 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)
- …and 9 more
