# Changelog

## Score

- CAI 51 → 59 (+7.5)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 80 → 80 (+0.0)
- Architecture 87 → 85 (-1.3)
- Maturity 40 → 65 (+25.1)
- Readiness 50 → 50 (+0.0)
- Security 90 → 95 (+4.9)
- Accessibility 55 → 55 (+0.7)
- Performance 100 → 100 (+0.0)

## Resolved (3)

- Facade method delegates to ConfigTreeRunner but exposes a different signature. The Facade takes a `storageFile` string, while the underlying runner takes the `EffectiveConfigNode` root. This hides the necessary context object from the user and forces the Facade to perform internal resolution, creating a disconnect between the public API contract and the actual implementation logic.
- Similar to `allowCurrentState`, the Facade's `check` method omits the `rootNode` (EffectiveConfigNode) and `recordHistory` parameters present in the underlying `ConfigTreeRunner`. This inconsistency makes it unclear if the Facade always records history or uses a default root node, reducing API transparency.
- The Facade's `generateReport` method takes a `reportPath` string, whereas the runner's `generateReports` (plural) takes `allowedPaths` and `recordHistory`. The Facade signature implies a single report generation at a specific path, while the runner suggests a broader operation on a tree structure. The parameter mismatch (`reportPath` vs `rootNode`/`allowedPaths`) indicates a lack of consistency in how the report generation scope is defined.
