# Changelog

## Score

- CAI 66 → 58 (-7.9)
- Rubric changed (rubric-2026.10.1 → rubric-2026.10.5) — scores are not directly comparable.

## Lenses

- Code Health 100 → 76 (-24.3)
- Architecture 69 → 69 (+0.0)
- Maturity 56 → 43 (-13.1)
- Readiness 67 → 67 (+0.0)
- Security 94 → 94 (+0.0)

## Resolved (4)

- Constructor signature inconsistency. Finder takes two arguments (path, options), while Header and Project take only one (path). This forces users to handle initialization differently depending on the type, even though they all represent a 'finder' or 'entity' located by a path.
- Naming inconsistency between plural method names and singular property names in related types. Finder uses plural methods (headers, bridging_headers) while Header and Project use singular properties (filename, bridging_header). While not strictly redundant, the API surface mixes pluralization conventions for similar concepts (collections vs single items).
- Off-boarding risk: anonymized user #1
- Workflow token permissions not restricted

## New (9)

- Ambiguous naming convention for header retrieval. 'headers' likely returns all headers, while 'bridging_headers' returns a specific subset. However, without context, it is unclear if 'headers' is a generalization or if there is a missing 'all_headers' or similar. More critically, Project has 'bridging_headers(verbose)' but no generic 'headers' method, creating an asymmetry in how header data is accessed across related types.
- Off-boarding risk: anonymized user #1
- Orphaned file (bin/fui)
- Orphaned file (lib/fui/finder.rb)
- Orphaned files with no living knowledge
- Workflow token permissions not restricted (.github/workflows/danger-comment.yml)
- Workflow token permissions not restricted (.github/workflows/danger.yml)
- Workflow token permissions not restricted (.github/workflows/rubocop.yml)
- Workflow token permissions not restricted (.github/workflows/test.yml)