HAL9000
be11d3c269
CI / build (pull_request) Successful in 23s
CI / lint (pull_request) Successful in 38s
CI / helm (pull_request) Successful in 28s
CI / push-validation (pull_request) Successful in 28s
CI / quality (pull_request) Successful in 40s
CI / typecheck (pull_request) Successful in 50s
CI / security (pull_request) Successful in 59s
CI / e2e_tests (pull_request) Successful in 3m21s
CI / integration_tests (pull_request) Successful in 4m16s
CI / unit_tests (pull_request) Successful in 5m11s
CI / docker (pull_request) Successful in 1m23s
CI / coverage (pull_request) Successful in 11m57s
CI / status-check (pull_request) Successful in 3s
CI / benchmark-publish (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Successful in 57m51s
The implementation (plan.py correct_decision function) accepts either a plan ID or a decision ID as the positional identifier argument. When a plan ID is given, the root decision of that plan is auto-selected as the correction target. Updated documentation to reflect both identifier forms across the synopsis, argument description, recovery hints, correction guidance, and decision tree sections. ISSUES CLOSED: #5558