# Changelog

## Score

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

## Lenses

- Code Health 48 → 48 (+0.0)
- Architecture 85 → 85 (+0.0)
- Maturity 73 → 74 (+1.0)
- Readiness 62 → 62 (+0.0)
- Security 81 → 74 (-7.6)
- Performance 94 → 94 (+0.0)

## Resolved (5)

- Ambiguous preposition usage. `fromStart` and `toStart` likely represent opposite operations (starting iteration from the beginning vs. moving the cursor to the beginning), but the naming is not immediately intuitive. Similarly for `fromEnd`/`toEnd`. This forces users to memorize which preposition implies 'start iteration' vs 'move cursor'.
- Confusing directional naming conventions. `forwards`/`backwards` use adverbial forms, while `previous`/`following` use participial forms. Furthermore, `previous` and `backwards` likely perform the same operation (moving to earlier events), as do `following` and `forwards`. This creates ambiguity about which pair to use.
- Documentation: no project overview (README.md)
- Duplicate intent for filtering. `where` and `filter` are semantically identical in most fluent APIs (LINQ style). Having both allows users to achieve the same result with different method names, leading to confusion about whether `options` in `filter` provides unique functionality or if `where` is just a simpler alias.
- Redundant iteration interfaces. The class exposes both a standard callback-based iteration method and the ES6 Symbol.iterator, allowing for both `forEach` loops and `for...of` loops. While not strictly an error, it creates API surface bloat where one canonical iteration strategy (typically Symbol.iterator for modern JS) should suffice, with `forEach` being a convenience wrapper or vice versa.

## New (3)

- Medium CVE: [GHSA redacted] (package-lock.json)
- Medium CVE: [GHSA redacted] (package-lock.json)
- doc comments repeat the names (src/JoinEventStream.js)
