test(memory): mock getOverrideAvailableMemoryGB in the override-chain integration test

Fix A routed the override survival-floor check through the new
getOverrideAvailableMemoryGB; the override-chain integration test mocks the
hardware boundary and hadn't defined it (auto-mock → undefined → NaN < floor
never refused). Delegate it to getAvailableMemoryGB (no swap in this scenario)
so both the loads-after-evict and hard-limit-refuses cases stay accurate.

Blast-radius caught by pre-push --findRelatedTests (the §D hub rule in action).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: alichherawalla

__tests__/integration/models/loadAnywayOverrideChain.test.ts

@@ -155,6 +155,12 @@ describe('Load Anyway override chain (UI helper → service → residency)', ()
     mockHardwareService.getAvailableMemoryGB.mockImplementation(() =>
       reclaimed ? 6 : 1,
     );
+    // The override survival-floor check now reads getOverrideAvailableMemoryGB (physical +
+    // free ZRAM swap on Android; == available on iOS). This scenario has no swap headroom, so
+    // it tracks getAvailableMemoryGB — delegate so it follows each test's dynamic value.
+    mockHardwareService.getOverrideAvailableMemoryGB.mockImplementation(async () =>
+      mockHardwareService.getAvailableMemoryGB(),
+    );
 
     // Force a small residency budget so the ~3 GB model can't fit without eviction —
     // deterministic, independent of the device-RAM heuristics under test elsewhere.