HAL9000
ec6987a014
CI / lint (pull_request) Successful in 28s
CI / quality (pull_request) Successful in 28s
CI / typecheck (pull_request) Successful in 55s
CI / security (pull_request) Successful in 51s
CI / push-validation (pull_request) Successful in 18s
CI / helm (pull_request) Successful in 24s
CI / build (pull_request) Successful in 25s
CI / e2e_tests (pull_request) Successful in 3m28s
CI / unit_tests (pull_request) Successful in 6m12s
CI / integration_tests (pull_request) Successful in 6m18s
CI / docker (pull_request) Successful in 1m23s
CI / coverage (pull_request) Successful in 13m53s
CI / status-check (pull_request) Successful in 1s
CI / benchmark-publish (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Successful in 58m16s
Closes #5328 The spec synopsis showed [<ARGS>...] which was ambiguous. The implementation (PR #3837) enforces --key value named option format and explicitly rejects positional key=value tokens. This commit aligns the synopsis, argument description, and all inline references throughout the spec to match the implementation and the existing examples which already showed --coverage-threshold 90. Changes: - Command synopsis (line ~270): [<ARGS>...] -> [--<KEY> <VALUE>]... - agents validation attach section synopsis: same fix - Argument description: clarify named option format, hyphen-to-underscore conversion - Inline references at lines 9271-9273: updated all three attachment scope examples - Attachment model section (lines 22536, 22546, 22556): updated all three entries - Management table (line 22986): updated synopsis and added note about named options