# Changelog

## Score

- CAI 53 → 56 (+2.9)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 65 → 65 (+0.0)
- Architecture 85 → 83 (-1.4)
- Maturity 40 → 49 (+9.1)
- Readiness 60 → 60 (+0.0)
- Security 71 → 59 (-11.7)

## Resolved (10)

- Both `length` and `size` are defined on `AssociationProxy`. In Ruby/ActiveRecord conventions, these often have different performance characteristics (count vs size), but without documentation, they appear as redundant aliases.
- Constraint management APIs are inconsistent. Element methods use `create_constraint`/`drop_constraint` with minimal args. Migration Helpers use `add_constraint`/`drop_constraint` with many more args including `name` and `relationship`. `drop_uniqueness_constraint` is a specific variant on Element that doesn't have a clear counterpart in Helpers (which use a generic `drop_constraint`).
- Documentation: no installation or build instructions (docs/index.rst)
- Documentation: no project overview (docs/README.md)
- Documentation: no usage examples (docs/index.rst)
- Duplicate definition of `pretty_cypher` as both a Property and a Method in `ActiveGraph.Core.Query`. This is redundant and potentially confusing for consumers expecting one or the other.
- Inconsistent indexing API across Element, Migration Helpers, and ModelSchema. Element uses `create_index`/`drop_index` with `properties` (plural) or `property` (singular). Migration Helpers use `add_index`/`drop_index` with explicit `label` and `property`. ModelSchema uses `add_defined_index`. The parameter names and object contexts differ significantly for the same underlying Neo4j operation.
- Inconsistent pluralization in helper methods. `add_label` vs `add_labels`, `remove_label` vs `remove_labels`. While this allows for single vs multiple operations, it creates a fragmented API surface where the user must choose the correct verb based on arity, which is error-prone.
- Multiple distinct entry points for executing Cypher queries with inconsistent naming and likely inconsistent argument handling. 'query' is used in Base, Helpers, and Migration, while 'magic_query' exists in Base. QueryBuilder also exposes 'query'. This creates confusion about which method to use for ad-hoc queries versus model-bound queries.
- Two methods with nearly identical names and likely identical intent (`has_association?` vs `association?`) on the same class. This is a direct duplication.

## New (1)

- Off-boarding risk: anonymized user #1

## Changes since last survey

- 6 commits — 4 feature/other, 2 fixes

## By area

- (root) — 6 commits

## Notable commits

- fix: fix(type_converters): make JSON properties work with json >= 3.0 (#1748)
- fix: fix: update 'neo4j-ruby-driver' version to 6.3.0 (#1747)
- change: chore(release): ignore untracked files in the dirty-tree check (#1751)
- change: chore(release): one-command rake release (#1750)
- change: chore(release): v12.0.1
- change: chore: gitignore stray .mvn/ directory (#1746)

## Architecture

- Unchanged — 0 containers · 1 contexts · 0 edges
