fix(plan): wrap plan tree JSON/YAML output in spec-required command envelope #11041

Closed
HAL9000 wants to merge 1 commits from pr-fix-9313-plan-tree-envelope into master

1 Commits

Author SHA1 Message Date
HAL9000 7d87f1f345 fix(plan): wrap plan tree JSON/YAML output in spec-required command envelope
CI / benchmark-publish (pull_request) Has been skipped
CI / lint (pull_request) Failing after 1m3s
CI / push-validation (pull_request) Successful in 24s
CI / quality (pull_request) Successful in 1m10s
CI / helm (pull_request) Successful in 30s
CI / build (pull_request) Successful in 33s
CI / typecheck (pull_request) Successful in 1m21s
CI / security (pull_request) Successful in 1m38s
CI / integration_tests (pull_request) Successful in 3m29s
CI / benchmark-regression (pull_request) Failing after 1m33s
CI / e2e_tests (pull_request) Failing after 4m28s
CI / unit_tests (pull_request) Failing after 4m39s
CI / coverage (pull_request) Has been skipped
CI / docker (pull_request) Has been skipped
CI / status-check (pull_request) Failing after 3s
The agents plan tree CLI command's JSON and YAML output paths now include
the standardised envelope fields (command, status, exit_code, data, timing)
as required by the specification. Previously the envelope had an empty
command field which broke programmatic consumers that parse the command key
to identify the source command.

Updated BDD test assertions to validate against the envelope structure and
removed @tdd_expected_fail tag from the JSON format scenario.

ISSUES CLOSED: #9313
2026-05-08 11:12:57 +00:00