cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.0k Pull Requests 115 Actions Packages Projects Releases Wiki Activity

docs(changelog): add CHANGELOG entry for invariant add scope requirement
CI / lint (pull_request) Successful in 36s
Details
CI / quality (pull_request) Successful in 43s
Details
CI / typecheck (pull_request) Successful in 52s
Details
CI / security (pull_request) Successful in 58s
Details
CI / build (pull_request) Successful in 25s
Details
CI / helm (pull_request) Successful in 26s
Details
CI / push-validation (pull_request) Successful in 21s
Details
CI / e2e_tests (pull_request) Failing after 3m11s
Details
CI / unit_tests (pull_request) Successful in 7m21s
Details
CI / integration_tests (pull_request) Successful in 7m22s
Details
CI / docker (pull_request) Successful in 55s
Details
CI / coverage (pull_request) Successful in 10m52s
Details
CI / status-check (pull_request) Failing after 1s
Details

Browse Source 
Document the bug fix for agents invariant add requiring at least one scope flag per spec §17900 (#9002).

ISSUES CLOSED: #9002
This commit is contained in:
HAL 9000
2026-04-16 20:00:20 +00:00
parent 1a0590405b
commit 5bf59132a5
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+7
View File
@@ -26,6 +26,13 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
crash (unhandled exception) is detected via an all-zero summary and the
captured traceback is always surfaced.
- **Invariant Add Scope Requirement** (#9002): `agents invariant add` now requires at
least one scope flag (`--global`, `--project`, `--plan`, or `--action`) per spec §17900.
Previously, omitting all scope flags silently defaulted to global scope. The
`_resolve_scope()` function now raises `typer.BadParameter` with a clear error message
when no scope flag is provided, failing fast instead of silently applying an unintended
default.
- **Automation Profile Silent Fallback** (#8232): `_resolve_profile_for_plan` in
`PlanLifecycleService` now raises a clear `ValidationError` when a plan's
automation profile name is not a known built-in profile, instead of silently