# Changelog

## Score

- CAI 79 → 76 (-3.1)
- Rubric changed (rubric-2026.10.1 → rubric-2026.10.5) — scores are not directly comparable.

## Lenses

- Code Health 99 → 75 (-24.0)
- Architecture 100 → 100 (+0.0)
- Maturity 71 → 71 (+0.0)
- Readiness 74 → 74 (+0.0)
- Security 94 → 94 (+0.0)

## Resolved (3)

- Inconsistent method naming across Psych versions. Both Psych3 and Psych4 patches expose `load_file` and `unsafe_load_file`. However, in the context of a 'Patch' class, these methods likely override or wrap standard Ruby YAML methods. The presence of both `load_file` and `unsafe_load_file` suggests a duplication of intent if one is a wrapper for the other, or a confusing API where the user must choose between 'safe' and 'unsafe' variants that might behave identically in the patched context.
- Members sharing a duplicated core (4 members, 50+ identical tokens) (lib/bootsnap/compile_cache/yaml.rb)
- Off-boarding risk: anonymized user #1

## New (3)

- Duplicate implementation across version-specific patches. While technically necessary for compatibility, the API surface exposes two identical method signatures on parallel types (`Psych4.Patch` and `Psych3.Patch`). This forces consumers to know which patch to use or implies that `YAML.patch()` should handle the dispatch, making the individual patch methods redundant if they are only ever called via the main `YAML` interface.
- Members sharing a duplicated core (4 members, 50+ identical tokens) (lib/bootsnap/compile_cache/yaml.rb)
- Off-boarding risk: anonymized user #1