# Changelog

## Score

- CAI 67 → 60 (-7.2)
- Rubric changed (rubric-2026.10.1 → rubric-2026.10.5) — scores are not directly comparable.

## Lenses

- Code Health 100 → 76 (-24.2)
- Architecture 69 → 69 (+0.0)
- Maturity 61 → 49 (-11.9)
- Readiness 66 → 66 (+0.0)
- Security 90 → 90 (+0.0)

## Resolved (2)

- Fork-triggerable workflow runs with an unscoped write token
- Inconsistent parameter naming for the batch execution method. While all loaders use `perform` as the method name, the argument names vary significantly (`record_ids`, `records`, `operations`, `keys`, `foreign_ids`). This creates cognitive load when reading code or documentation, as the semantic meaning of the input is similar (a collection of keys/records to load) but the API surface differs.

## New (4)

- Fork-triggerable workflow runs with an unscoped write token (.github/workflows/cla.yml)
- Inconsistent parameter naming for the batch execution method. While all loaders use `perform` as the method name, the argument names vary significantly (`record_ids`, `records`, `operations`, `keys`, `foreign_ids`). This forces consumers to remember specific argument names or rely on positional arguments, reducing readability and IDE support.
- Off-boarding risk: anonymized user #1
- Workflow token permissions not restricted (.github/workflows/ci.yml)