# Changelog

## Score

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

## Lenses

- Code Health 59 → 59 (+0.0)
- Architecture 97 → 97 (+0.0)
- Maturity 43 → 51 (+8.1)
- Readiness 67 → 67 (+0.0)
- Security 83 → 78 (-4.6)

## Resolved (6)

- Duplicate method signatures between the global `DEBUGGER__` object and the `Session` object. This creates confusion about whether the user should interact with the global singleton or the session instance.
- Inconsistent naming convention for colorization methods. While they are distinct colors, the pattern `colorize_<color>` is verbose compared to typical DSLs which might use `cyan(str)`, `blue(str)`, or a single `colorize(str, :cyan)`. This is a minor stylistic inconsistency but notable in a public API.
- Off-boarding risk: anonymized user #1
- Redundant entry points for adding catch breakpoints. `DEBUGGER__` and `Session` both expose `add_catch_breakpoint`. The signatures differ slightly (`pat` vs `pat, cond`), suggesting inconsistent default handling or argument parsing between the global interface and the session interface.
- Redundant entry points for adding line breakpoints. `DEBUGGER__` (global singleton) and `Session` both expose `add_line_breakpoint` with identical signatures. Additionally, `Session.repl_add_breakpoint` appears to be a wrapper or alternative for the same operation, likely handling argument parsing differently.
- Scattered skip logic. `DEBUGGER__.skip_all` is a global action, while `skip?` is a query. `Breakpoint` has `skip_src` (property) and `skip_path?` (method). It is unclear if `skip_all` respects `skip_src` or `skip_path?` configurations, leading to potential confusion about how skipping is controlled globally vs per-breakpoint.

## New (1)

- Off-boarding risk: anonymized user #1
