The step "I build the decision tree with default options" was already
defined in features/steps/plan_explain_steps.py:268. This caused
behave.step_registry.AmbiguousStep during step loading, which crashed
all 31 parallel workers before any scenario could run (0 scenarios,
31 errored at feature level).
Rename the When step in the TDD feature and its step definition to
"I build the correction TDD test decision tree" — unique across the
entire features/steps/ directory.
ISSUES CLOSED: #8576
This TDD scenario documents the gap in Spec Requirement #7: the current
implementation of 'agents plan tree' does not visually distinguish corrected
nodes (decisions with is_correction=True).
The scenario creates a plan with a corrected decision and asserts that the
tree output contains a visual marker such as [corrected] or ✎. The scenario
is tagged @tdd_expected_fail to allow CI to pass while the bug exists.
The Rich tree renderer in tree_decisions_cmd builds node labels without
checking decision.is_correction, proving the gap exists.
- Revert production code change: remove label key and [corrected] marker
from _node_dict in build_decision_tree (the TDD scenario must prove the
bug exists, not fix it; the fix belongs in a separate PR)
- Update CONTRIBUTORS.md with TDD scenario contribution entry
- Add CHANGELOG.md entry for TDD scenario (#8576)
- Remove dead _make_decision() helper (was already removed by prior attempt)
- Remove # type: ignore[import-untyped] (was already removed by prior attempt)
ISSUES CLOSED: #8576
HAL9000