# Changelog

## Score

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

## Lenses

- Code Health 56 → 56 (+0.0)
- Architecture 80 → 80 (+0.0)
- Maturity 50 → 77 (+27.3)
- Readiness 38 → 38 (+0.0)
- Security 52 → 56 (+4.6)
- Performance 100 → 100 (+0.0)

## Resolved (9)

- Confusing overlap in lifecycle management verbs. `spawn` implies creation, `start` implies activation, but `background` and `foreground` also imply activation modes. It is unclear if `spawn` creates and starts, or just creates. `start` vs `background`/`foreground` suggests `start` might be a default mode, but the existence of explicit mode methods makes `start` redundant or confusingly named.
- Documentation: no installation or build instructions (docs/cli/reference.md)
- Documentation: no usage examples (docs/core/utilities.module.md)
- Duplicate method name with different semantic intent. `ModelBase.setBaseProperties` appears to configure internal state/defaults for a model, while `Property.setBaseProperties` likely configures a specific property instance. The name 'setBaseProperties' is ambiguous in both contexts and suggests a shared implementation or intent that doesn't exist.
- Inconsistent retrieval patterns. There are separate methods for getting by alias, by pid, and by name+alias. This suggests a lack of a unified lookup mechanism. `getByNameAndAlias` is particularly confusing as it requires both, whereas others require only one.
- Medium CVE: [GHSA redacted] (package-lock.json)
- Redundant operation signatures. Similar to `call`, `status` and `statusByPid` duplicate the intent of retrieving worker status based on different identifier types.
- Redundant operation signatures. `call` and `callByPid` perform the same action (invoking a method on a worker) but accept different identifiers (name/alias vs pid). This forces users to know which identifier they have and choose the correct method, rather than having a single `call` method that accepts a flexible identifier or a worker reference.
- Redundant operation signatures. `stop` and `stopByPid` duplicate the intent of stopping a worker based on different identifier types.

## New (4)

- High CVE: [GHSA redacted] (package-lock.json)
- doc comments repeat the names (src/adapters/workers/worker.state-machine.js)
- redundant comment (src/adapters/http/api.module.js)
- redundant comment (src/utils/validator.util.js)
