# Changelog

## Score

- CAI 57 → 59 (+1.9)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.3) — scores are not directly comparable.

## Lenses

- Code Health 73 → 73 (+0.0)
- Architecture 98 → 98 (-0.5)
- Maturity 44 → 44 (+0.0)
- Readiness 62 → 67 (+4.4)
- Security 73 → 73 (+0.0)
- Performance 71 → 85 (+14.3)

## Resolved (10)

- Ambiguous relationship between `then` and `and`. `then` implies sequential execution (handler B runs after A), while `and` implies parallel/concurrent execution (handlers A and B run concurrently). While the names are distinct, they are often confused by users. The API is consistent in its own logic, but the naming could be more explicit (e.g., `thenConcurrently` vs `thenSequentially`). However, given the DSL nature, `then` and `and` are standard and distinct enough.
- Naming inconsistency between lifecycle management and component control. `Disruptor` uses `halt()` to stop the entire system, while the underlying `EventProcessor` implementations also use `halt()`. However, `Disruptor` also exposes `shutdown()` which performs a graceful stop with optional timeout. The distinction between `halt()` (immediate/forceful) and `shutdown()` (graceful) is clear on `Disruptor`, but `EventProcessor` only has `halt()`. This is not a direct duplication, but the API surface for stopping processors is less rich than the orchestrator. More critically, `Disruptor.start()` returns `RingBuffer`, while `Disruptor.shutdown()` returns `void`. This is a minor asymmetry but acceptable.
- No assertions: shouldHandleImmediateSequenceChange (src/test/java/com/lmax/disruptor/PhasedBackoffWaitStrategyTest.java)
- No assertions: shouldHandleSequenceChangeWithOneMillisecondDelay (src/test/java/com/lmax/disruptor/PhasedBackoffWaitStrategyTest.java)
- No assertions: shouldHandleSequenceChangeWithTenMillisecondDelay (src/test/java/com/lmax/disruptor/PhasedBackoffWaitStrategyTest.java)
- No assertions: shouldHandleSequenceChangeWithTwoMillisecondDelay (src/test/java/com/lmax/disruptor/PhasedBackoffWaitStrategyTest.java)
- No assertions: shouldWaitForValue (src/test/java/com/lmax/disruptor/BusySpinWaitStrategyTest.java)
- No assertions: shouldWaitForValue (src/test/java/com/lmax/disruptor/SleepingWaitStrategyTest.java)
- No assertions: shouldWaitForValue (src/test/java/com/lmax/disruptor/YieldingWaitStrategyTest.java)
- Redundant factory methods. `RingBuffer.createSingleProducer` and `RingBuffer.createMultiProducer` are essentially wrappers around `RingBuffer.create` with a specific `ProducerType`. This creates three ways to create a RingBuffer with a single producer, which is redundant.

## New (6)

- Edited copy of a member (11 corresponding lines) (src/main/java/com/lmax/disruptor/SleepingWaitStrategy.java)
- Edited copy of a member (22 corresponding lines) (src/main/java/com/lmax/disruptor/BlockingWaitStrategy.java)
- Edited copy of a member (25 corresponding lines) (src/main/java/com/lmax/disruptor/MultiProducerSequencer.java)
- Edited copy of a member (26 corresponding lines) (src/main/java/com/lmax/disruptor/dsl/Disruptor.java)
- Edited copy of a member (27 corresponding lines) (src/main/java/com/lmax/disruptor/LiteTimeoutBlockingWaitStrategy.java)
- Edited copy of a member (9 corresponding lines) (src/main/java/com/lmax/disruptor/dsl/Disruptor.java)
