# Changelog

## Score

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

## Lenses

- Code Health 75 → 75 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 54 → 54 (+0.0)
- Readiness 67 → 67 (+0.0)
- Security 99 → 98 (-0.7)

## Resolved (4)

- CLI offers a combined 'create_and_start' operation, while the Client API requires two separate calls (create_workflow then start_workflow). This inconsistency forces CLI users to have a simpler workflow than programmatic users.
- Four different methods for listing/retrieving workflows with inconsistent parameter names and return types. CLI.list returns display data, Client.workflow_ids returns IDs, Client.workflows returns objects, and Workflow.page is a class method. The parameter 'start/stop' vs 'order' vs 'kwargs' is inconsistent.
- Three distinct entry points for creating a workflow exist with different signatures and responsibilities. CLI.create is a high-level CLI command, Client.create_workflow is a client-side API call, and Workflow.create is a model-level factory. This forces users to choose the correct layer without a clear unified entry point.
- Three methods for retrieving a workflow by ID. CLI.show is for display, Client.find_workflow is for client retrieval, and Workflow.find is a model lookup. This duplication creates confusion about which method to use for programmatic access.
