# Changelog

## Score

- CAI 68 → 69 (+1.7)

## Lenses

- Code Health 92 → 92 (+0.0)
- Architecture 97 → 97 (+0.0)
- Maturity 55 → 59 (+3.7)
- Readiness 59 → 59 (+0.0)
- Security 100 → 100 (+0.0)
- Performance 100 → 100 (+0.0)

## Resolved (6)

- Documentation: no installation or build instructions (README.md)
- Documentation: no usage examples (README.md)
- Duplicate functionality with different access paths. `FloatingPanelProxy` exposes the exact same `move` signature as the underlying `FloatingPanelController`. This creates confusion about whether the user should interact with the Controller directly or via the Proxy.
- Duplicate functionality with different access paths. `FloatingPanelProxy` exposes the exact same `track` signature as the underlying `FloatingPanelController`.
- Inconsistent naming convention for paired operations. `track` is used for setting up the scroll view tracking, but `untrack` is used for removing it. Standard iOS/Swift conventions typically use `untrack` or `stopTracking`, but `removeTracking` or `detach` might be more consistent with `addPanel`/`removePanel`. However, the primary issue is that `track` is a verb implying an action, while `untrack` is a negation. A more consistent pair would be `track(scrollView:)` and `untrack(scrollView:)` (current) OR `startTracking(scrollView:)` and `stopTracking(scrollView:)`. Given `addPanel`/`removePanel` exists, `track`/`untrack` is acceptable but slightly less idiomatic than `startTracking`/`stopTracking`.
- Workflow token permissions not restricted

## New (1)

- Workflow token permissions not restricted (.github/workflows/ci.yml)