Why: Complete the approved U2/U3 fix pass and prevent shared host fixture collisions.
Evidence: Native SELF receipts record complete Backend suite, Frontend 221 tests, meaningful startup regression failures and the bounded baseline model batch.
Impact: Pin the corrected Backend and Frontend and allocate owned recovery fixture ports; no existing service deployment.
Refs: modules/documents/docs/proposals/2026-10-13-fast-slow-u2-u3-plan.md