Make mixed Homeworld HTTP fixture deterministic

docs/CURRENT_STATUS.md

@@ -64,7 +64,13 @@ job and test-container loopback addresses are in separate nested Docker
 network namespaces. With user approval the dedicated runner now shares its
 own network namespace with its jobs, while retaining its separate Docker
 daemon; the runner reconnected. A fresh end-to-end build and registry
-publication remain unverified. Existing NAS deployment and its persistent
+publication remain unverified. Build `02695ae` passed container startup and
+25 administrator checks, then failed one of 69 HTTP cases: the mixed Richese
+Homeworld fixture allowed an unrelated earlier automated shipment before its
+scripted two-force move. The fixture now suppresses those unrelated turns and
+asserts the zero-to-two transition; its focused HTTP case passes locally. The
+CI log did not preserve the precise earlier action, so the exact cause of its
+extra visitor remains unproven. Existing NAS deployment and its persistent
 storage remain untouched.
 
 **Semuta before Basic Moritani ally retention — 28 October. Prototyped /