# Changelog

## Score

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

## Lenses

- Code Health 61 → 61 (+0.0)
- Architecture 87 → 85 (-2.0)
- Maturity 40 → 44 (+4.1)
- Readiness 50 → 50 (+0.0)
- Security 81 → 71 (-9.6)

## Resolved (5)

- Ambiguous initialization entry points. `Awspec.configure` suggests configuration setup, while `CLI.init` suggests command-line interface initialization. It is unclear if these are distinct concerns or if one is a wrapper for the other, leading to confusion about the correct entry point for library vs CLI usage.
- Helper methods for ID/Name conversion duplicate intent of standard finders. `get_id_by_name_tag` and `get_name_by_id` are utility methods that essentially perform lookups. If `find_efs` is the standard way to get a resource, these helper methods create a parallel, confusing path for users who might want to resolve an ID from a name.
- Inconsistent naming for 'find by ID' vs 'select by criteria'. Some finders use `find_<resource>(id)` (e.g., `Alb.find_alb(id)`), while others use `select_<resource>_by_<criteria>` (e.g., `Alb.select_alb_by_vpc_id`). However, `Sqs` uses `find_queue(queue_name)` which is ambiguous (is it an ID or name?). More critically, `Ebs.select_ebs_by_instance_id` and `Eip.select_eip_by_instance_id` use 'select' for a specific lookup, whereas `Ebs.find_ebs(volume_id)` uses 'find'. The distinction between 'find' (usually by ID/ARN) and 'select' (usually by filter/criteria) is violated or inconsistently applied across services.
- Inconsistent pluralization and 'all' selection. While `find` vs `select_all` is a common pattern, some services like `CloudwatchEvent` use `find_cloudwatch_event` and `select_all_cloudwatch_events`, while others like `Codebuild` use `find_codebuild_project` and `select_all_codebuild_projects`. The inconsistency is minor but present in the naming of the 'all' method (e.g., `select_all_*` vs potentially `find_all_*` in other parts of the codebase not shown, but here the main issue is the mix of `find` and `select` verbs for similar operations across different services). Specifically, `Alb` uses `select_all_alb_tags` which is a different operation (tags vs resources), but `Cloudwatch` uses `select_all_cloudwatch_alarms`. The verb 'select' is used for 'get all', while 'find' is used for 'get one'. This is consistent within services but the API surface as a whole should ensure 'find' is always singular and 'select_all' is always plural.
- Redundant 'get' vs 'find' methods in WAFv2. `Wafv2.get_ip_set` and `Wafv2.find_ip_set` appear to do the same thing (retrieve a resource), but with different signatures (one takes ID, one takes Name). This duplicates intent and forces users to choose between two methods for the same logical operation.

## Changes since last survey

- 2 commits — 2 feature/other, 0 fixes

## By area

- doc/resource_types.md — 2 commits

## Notable commits

- change: Commit from GitHub Actions (Doc)
- change: Commit from GitHub Actions (Doc)
