The previous refactor routed list_invariants through _resolve_scope,
which silently changed the no-flags behavior: _resolve_scope returns
(GLOBAL, "system") when no flag is given (the `add` default), so
`agents invariant list` filtered to only global+system invariants
instead of returning every active invariant.
InvariantService.list_invariants documents scope=None / source_name=None
as "all scopes" / "all sources"; the listing CLI must preserve that
contract. Inline the mutual-exclusion check in list_invariants and
restore the if/elif chain that leaves scope/source_name=None when no
flag is set, while keeping `agents invariant add` defaulting to global.
Tests added:
- "List invariants with no flags passes no scope filter" verifies the
service is called with scope=None, source_name=None.
- "List invariants with conflicting scope flags rejected" covers the
new BadParameter raise path.
ISSUES CLOSED: #11049
Fix `_resolve_scope()` to properly check the `is_global` parameter
instead of silently ignoring it. Replace the standalone if/elif chain
in `list_invariants` with a call to `_resolve_scope()` so that scope
flag conflicts are consistently rejected on both `add` and `list`
commands via mutual-exclusion validation.
- Explicit global check in _resolve_scope() for correctness
- list_invariants uses shared _resolve_scope for consistent validation
- BDD coverage: add scenario for list with conflicting scope flags
- Robot coverage: add list-scope-conflict smoke test
- CHANGELOG.md and CONTRIBUTORS.md updated
ISSUES CLOSED: #11049