# Changelog

## Score

- CAI 51 → 50 (-0.2)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 65 → 65 (+0.0)
- Architecture 80 → 80 (+0.0)
- Maturity 43 → 43 (+0.0)
- Readiness 42 → 42 (+0.0)
- Security 92 → 87 (-5.3)

## Resolved (5)

- Documentation: no installation or build instructions (README.md)
- Documentation: no usage examples (README.md)
- Inconsistent parameter naming between Resource classes and Client methods. Resource classes (Project, Release, Stack) use `params` for query/filter options, while the underlying Client methods use `data`. This creates a disconnect in the API surface where the caller might expect `params` to map directly to the client's `data` argument, but the naming convention differs between the high-level resource API and the low-level client API.
- Inconsistent parameter naming for HTTP methods. While 'path' and 'data' are used, 'data' is ambiguous for GET requests (where query params are usually expected) and POST/PUT/PATCH (where body is expected). Other APIs often distinguish between 'query_params' and 'body' or 'payload'.
- Inconsistent spelling of 'standardize'. The methods in Jets.Cfn.Base and Jets.Cfn.Resource.Standardizer are misspelled as 'standarize', while IAM policy classes use the correct spelling 'standardize'.
