-
run_fix_loop() chains U-015 (3-perspective root-cause judgment) + U-016 (routing) + real Coder/Planner/Validator calls into architecture doc §11's 4th MVP acceptance criterion: judge -> create bug_record -> route (fast_lane for category=coder, full_replan for category=planning -- a fixed mapping this Unit defines, since bug_record.suggested_route is technically an independent Validator judgment but REQ-05/architecture §11's scenarios always correlate the two, so no extra Agent call was added just to re-decide it) -> trigger the fixer -> re-trigger Validator -> close_task_ done on confirmed PASS. 3 new mocked stdlib unittest cases (route branching, verification-fails leaves the task out of 'done'). 160 total mocked tests across U-001-017, all passing. Real coverage reuses U-015's wall-collision scenario but this time drives an actual fix: a real Coder call edits collision.py in the repo, a real Validator call reads the fixed file and confirms it, running as a detached background process (survives this session's own restarts, unlike two earlier real runs this session that got silently orphaned by a session teardown with no completion record -- lesson learned, not repeated). This closes PH2-S1 (U-015/016/017): REQ-04/05/09 and architecture doc §11 criterion 4 are now real, verified code, not just planned intent. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
