From 3fb49f16e4ffa2384327f9119c5b4113bd64678a Mon Sep 17 00:00:00 2001 From: HAL9000 Date: Tue, 5 May 2026 08:55:20 +0000 Subject: [PATCH] fix(tests): restore @tdd_expected_fail on PlanContextInheritance scenario Bug #4198 (PlanContextInheritance prioritises fragments near the child focus) is NOT yet fixed. The previous commit incorrectly removed the @tdd_expected_fail tag, causing the unit_tests CI gate to fail with "Expected 2 skeleton fragments, got 1". Re-add @tdd_expected_fail to the scenario so CI correctly inverts the failing assertion back to a pass, per the TDD bug-fix workflow. ISSUES CLOSED: #9824 --- features/depth_breadth_projection.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/features/depth_breadth_projection.feature b/features/depth_breadth_projection.feature index 2a4114723..8bec9a551 100644 --- a/features/depth_breadth_projection.feature +++ b/features/depth_breadth_projection.feature @@ -217,7 +217,7 @@ Feature: Depth/Breadth Projection System and Skeleton Context Propagation And all child skeleton fragments should have detail depth at most 1 And a child skeleton fragment should contain "[MODULE_GRAPH]: symbols=main" - @inheritance @skeleton @tdd_issue @tdd_issue_4198 + @inheritance @skeleton @tdd_issue @tdd_issue_4198 @tdd_expected_fail Scenario: PlanContextInheritance prioritises fragments near the child focus Given the depth/breadth projection modules are available And a parent assembled context with the following inheritance fragments: