# Changelog

## Score

- CAI 49 → 50 (+0.8)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 68 → 68 (+0.0)
- Architecture 84 → 83 (-1.4)
- Maturity 46 → 53 (+7.3)
- Readiness 59 → 56 (-2.8)
- Security 42 → 41 (-1.4)
- Domain Modelling 66 → 66 (+0.0)
- Accessibility 60 → 60 (+0.0)

## Resolved (6)

- Both controllers expose 'lookup', which is consistent. However, Shipit.TasksController also exposes 'tail', which is not present in the API controller. 'tail' is likely a streaming operation for logs, which might not fit the RESTful API pattern, but if the API is meant to be feature-complete, this is a gap.
- Both controllers expose 'refresh', which is good. However, Shipit.StacksController also exposes 'lookup' and 'all_tasks', while Shipit.Api.StacksController does not. This suggests the API controller is a subset of the web controller's functionality, which is acceptable but should be intentional. The inconsistency lies in the fact that 'lookup' is a common pattern for finding resources, yet it's missing from the API.
- Duplicate intent across API and Web controllers. Shipit.Api.DeploysController and Shipit.DeploysController both expose 'create'. Furthermore, Shipit.DeploysController exposes 'rollback' and 'revert' as distinct actions, while Shipit.Api.DeploysController only exposes 'create'. This suggests the API controller is either incomplete or the domain model for 'rollback' vs 'revert' is not consistently exposed via the API.
- Inconsistent naming for starting a task. The API controller uses 'trigger' to start a task, while the web controller uses 'create'. This forces consumers of the API to use a different verb than the internal web application logic, creating cognitive load.
- Off-boarding risk: anonymized user #1
- While both use 'abort', the context differs. The API controller likely handles programmatic cancellation, while the web controller handles UI-initiated cancellation. However, without clear documentation, this is a minor inconsistency. A more significant issue is the lack of 'abort' in Shipit.Api.DeploysController despite its presence in Shipit.DeploysController (implied by the need to cancel deployments).

## New (3)

- Leaked secret: private-key (docs/setup.md)
- Off-boarding risk: anonymized user #1
- Secret: private-key (docs/setup.md)

## Changes since last survey

- 1 commits — 1 feature/other, 0 fixes

## By area

- (root) — 1 commit

## Notable commits

- change: 0.45.5 (#1509)

## Architecture

- Unchanged — 0 containers · 1 contexts · 0 edges
