# Changelog

## Score

- CAI 57 → 58 (+0.4)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 99 → 99 (+0.0)
- Architecture 99 → 99 (+0.0)
- Maturity 66 → 70 (+4.1)
- Readiness 34 → 34 (-0.1)
- Security 75 → 71 (-4.1)
- Performance 100 → 100 (+0.0)

## Resolved (7)

- Ambiguous naming for similar operations. `matches` takes a full event object, while `matches_event` takes a string (likely an event name/type). The naming convention is inconsistent (`matches` vs `matches_event`) and the parameter types are distinct but the intent (checking if an event matches the query) is the same.
- Concentrated knowledge decay
- Documentation: contradicts the code (docs/docs/postgres.md)
- Documentation: written for insiders (docs/docs/intro.md)
- Off-boarding risk: anonymized user #1
- The naming `unsafe_new` suggests a Rust `unsafe` block or a dangerous operation, but it returns `Self` directly without a `Result`. If it performs validation, it should return a `Result`. If it bypasses validation, the name is misleading because `new` is the safe constructor. In Rust, `unsafe` usually refers to the block, not the method name. If it's a 'fast path' for already-validated strings, it should be named `from_str_unchecked` or similar to follow standard library conventions.
- While both methods exist on different types, the naming `exclude_events` is potentially confusing because it likely filters by event *names* (strings), not event *instances*. Given that `StreamQuery` also has `matches_event(event: str)`, the term 'events' in `exclude_events` is ambiguous. It should probably be `exclude_event_names` for consistency with the likely intent.

## New (24)

- Dormant codebase
- 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)
- Medium vulnerability: [GHSA redacted] (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0391 (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0398 (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0410 (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0414 (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0447 (Cargo.lock)
- Off-boarding risk: anonymized user #1
- …and 4 more
