Generated from the executable scenarios in tests/acceptance/catalog.py. Run python3 scripts/scenarios.py to verify the scenarios and regenerate this page.
Repair remains possible during failure
repair warnings View test
Protected actions stay protected on every attempt
protected-actions View test
Inspection never starts a check
repair check-execution View test
Inherited debt does not absorb new failures
baseline regressions View test
Editing a function activates its inherited findings
changed-code View proposal
- Given A function has three inherited warnings and another function has twelve.
- When The agent changes the first function.
- Then Its three warnings require cleanup while the other twelve remain backlog.
- And Repair tools remain available while completion is guarded.
Changed code activates the cross-file findings it participates in
changed-code cross-file View proposal
- Given An inherited finding involves functions in two files.
- When The agent changes one of those participating functions.
- Then That cross-file finding requires cleanup while unrelated findings remain backlog.
Disabling a rule is not a resolution
rules resolution View proposal
- Given A finding requires cleanup in changed code.
- When Its rule is disabled or its source path is excluded.
- Then The finding is not recorded as fixed.
Moving a finding preserves its identity and age
identity age View proposal
- Given An inherited finding has a recorded identity and first-seen date.
- When Unrelated lines are inserted above it or the agent session restarts.
- Then Its identity and age remain unchanged and movement alone does not activate it.
Untouched debt escalates at its configured deadline
age deadlines View proposal
- Given An inherited finding has a project-configured deadline.
- When A check runs after that deadline.
- Then The finding escalates according to project policy without resetting its first-seen date.