# Changelog

## Score

- CAI 58 → 58 (-0.6)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 76 → 76 (+0.0)
- Architecture 93 → 93 (+0.0)
- Maturity 63 → 63 (-0.1)
- Readiness 43 → 43 (+0.0)
- Security 83 → 77 (-6.6)

## Resolved (4)

- Ambiguous distinction between `exec_program` and `exec_subprocess`. The names suggest a technical implementation detail (process type) rather than a user-facing operation. It is unclear if this is a public API or internal helper. If public, the distinction is confusing; if internal, it should not be exposed at the top-level `Dip.Command` type.
- Inconsistent argument handling for CLI entry points. Most methods accept `argv`, but `provision()` and `validate()` do not. This suggests an inconsistency in how the CLI layer handles argument parsing or delegation, or implies these commands are stateless/single-argument while others are not.
- Inconsistent argument naming in sub-CLI modules. `DNS.up()` and `SSH.up()` take no arguments, while `DNS.restart(args)` and `SSH.restart(args)` take `args`. Meanwhile, `Dip.CLI.up(argv)` takes `argv`. It is unclear if `args` in the sub-modules is a subset of `argv` or a different structure, creating confusion for implementers of these sub-commands.
- Inconsistent constructor parameter naming compared to other command constructors. Most commands use `initialize(argv, ...)` or `initialize(...)`, but Infra commands explicitly name the first argument `compose_argv`. This breaks the pattern established by `Dip.Commands.Compose` and others.
