refactor(scheduler): migrate story fix loop off RootTaskID re-pointing onto CurrentAttempt resolution

1 files changed, 0 insertions, 6 deletions

diff --git a/internal/scheduler/story_orchestrator_test.go b/internal/scheduler/story_orchestrator_test.go
index aa7fff1..08bd155 100644
--- a/internal/scheduler/story_orchestrator_test.go
+++ b/internal/scheduler/story_orchestrator_test.go
@@ -954,12 +954,6 @@ func TestStoryOrchestrator_ArbitrationRejects_LeavesRootReadyNotCompleted(t *tes
 	}
 }
 
-// TestStoryOrchestrator_NeedsFix_SpawnsFixAttemptAndRepointsRoot proves the
-// core mechanism: a story at NEEDS_FIX gets a new builder-role fix-attempt
-// task spawned (depending on the rejected root), and the story is re-pointed
-// at it (RootTaskID updated, Status reset to IN_PROGRESS) so the very next
-// tick re-enters the normal Builder->Evaluators->Arbitration flow against
-// the new attempt.
 // TestStoryOrchestrator_NeedsFix_SpawnsFixAttempt proves the core mechanism:
 // a story at NEEDS_FIX gets a new builder-role fix-attempt task spawned
 // (depending on the rejected root), and the story's Status resets to