Release v1.5.0
What changed
- Added provider capability contracts in the registry using tri-state support:
supportedunsupportedunknown- Added execution safety/diagnostic CLI flags:
--strict-capabilities--dry-run--print-effective-config- Added capability validation before execution:
- default permissive mode: warning + continue
- strict mode: fail-fast on unsupported/unknown requested capabilities
- Added dry-run preflight behavior:
- validates resolved provider/runtime config
- validates capability compatibility
- exits without provider generation and without writing artifacts
- Added effective-config diagnostics with masked API key handling.
- Updated documentation (README + technical docs) to reflect v1.5 safety and preflight behavior.
Why it matters
- Reduces runtime surprises by checking feature compatibility before execution.
- Improves operational safety for CI/automation workflows.
- Adds reproducible preflight diagnostics for debugging configuration issues.
- Preserves the existing stateless execution architecture while improving reliability.
Stability Statement
v1.5.0is a stable feature release.- No CLI breaking changes were introduced.
- No output JSON schema/contract breaking changes were introduced.
- Stateless single-execution design remains unchanged.
Scope Clarification
- This release does not introduce agents, memory, orchestration, tool-calling runtime, or multi-
turn workflows. - The
toolscapability is currently a reserved contract field for future compatibility checks and
remains unsupported at runtime.
GitHub Pull Requests Included
- feat(v1.5): introduce provider capability contract registry by @damienSavoldelli in #21
- feat(v1.5): add strict and permissive provider capability safety checks by @damienSavoldelli in #22
- feat(v1.5): add dry-run and effective runtime config diagnostics by @damienSavoldelli in #23
- docs(v1.5): document capability safety and diagnostic modes by @damienSavoldelli in #24
- release: prepare v1.5.0 by @damienSavoldelli in #25
Full Changelog: v1.4.0...v1.5.0