# Changelog

## Score

- CAI 43 → 40 (-2.9)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 53 → 39 (-14.4)
- Architecture 92 → 92 (-0.8)
- Maturity 68 → 69 (+1.3)
- Readiness 67 → 67 (-0.1)
- Security 37 → 34 (-3.6)
- Domain Modelling 100 → 100 (+0.0)
- Accessibility 31 → 31 (+0.0)
- Performance 95 → 95 (+0.0)

## Resolved (5)

- Ambiguous duplication: It is unclear if `now_f` and `now` serve distinct purposes (e.g., float vs integer timestamp, or different time sources) or if one is a legacy alias for the other. Without documentation, these appear to be redundant operations for retrieving the current time.
- Ambiguous duplication: `locked` likely returns a boolean indicating if the lock is held, while `locked_jids` returns the IDs of jobs currently holding the lock. However, the naming `locked` is a predicate, while `locked_jids` is a data retrieval method. This is not strictly an inconsistency, but if `locked` returns a list of JIDs in some contexts, it would be a major issue. Assuming standard usage, this is likely consistent, but the naming `locked` vs `locked_jids` could be clearer (e.g., `is_locked?` vs `holding_job_ids`).
- Ambiguous duplication: `reflections` (plural) suggests retrieving a collection or registry of reflections, while `reflect` (singular) suggests performing an action or retrieving a single item. However, without seeing the return types, it is unclear if `reflect` is a method on a specific object or a class method that does something entirely different. If `reflect` is a class method that triggers a reflection process, it's distinct. If it's meant to be a getter for a single reflection, the naming is inconsistent with `reflections`.
- Standard Ruby convention violation: Similar to `validate_worker`, the `!` suffix on `delete` implies a destructive operation or raising an exception. If `delete` returns a boolean and `delete!` raises, this is consistent. However, in many Ruby libraries, `delete` is the primary method and `delete!` is not used, or vice versa. Having both requires strict adherence to the convention to avoid confusion.
- Standard Ruby convention violation: The `!` suffix typically implies a destructive operation or raising an exception on failure, while the non-`!` version returns a boolean or nil. However, in validation contexts, this distinction is often confusing if both raise or both return booleans. If `validate_worker` returns a boolean and `validate_worker!` raises, this is consistent with Ruby, but if they behave similarly, it's redundant.

## New (8)

- High secret: WD-SECRET-0005 (my_app/dev.env)
- High secret: WD-SECRET-0005 (myapp/db/seeds.rb)
- High secret: WD-SECRET-0005 (myapp/db/seeds.rb)
- High secret: WD-SECRET-0005 (myapp/dev.env)
- High secret: WD-SECRET-0005 (rails_example/dev.env)
- High secret: WD-SECRET-0005 (rails_example/docker-compose.yml)
- Medium CVE: [GHSA redacted] (myapp/Gemfile.lock)
- Outdated: bootsnap

## Architecture

- Unchanged — 0 containers · 1 contexts · 0 edges
