test: mock the image-integrity boundary in download/residency suites

The new extraction-completeness + load-time integrity checks run real RNFS validation.
Four pre-existing suites (imageDownloadActions/resume, imageDownloadRecovery,
activeModelService) mock RNFS/services and never lay a complete model dir on disk, so the
new gate threw ImageModelIncompleteError where they expected success. Those suites cover
download/residency ORCHESTRATION, not the completeness rule (which has its own dedicated
tests in imageModelIntegrity.test + imageGenerationFlow), so mock the integrity boundary to
"complete" in each. Full suite green (330 suites, 6960 tests).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: alichherawalla

__tests__/integration/models/activeModelService.test.ts

@@ -27,6 +27,12 @@ import { createDownloadedModel, createONNXImageModel, createDeviceInfo } from '.
 jest.mock('../../../src/services/llm');
 jest.mock('../../../src/services/localDreamGenerator');
 jest.mock('../../../src/services/hardware');
+// Integrity is a boundary for these residency/memory tests (the model files aren't laid
+// down on a real disk here). The completeness rule has its own dedicated tests.
+jest.mock('../../../src/utils/imageModelIntegrity', () => ({
+  validateImageModelDir: jest.fn(async () => ({ complete: true, missing: [] })),
+  ensureImageExtractionComplete: jest.fn(async () => {}),
+}));
 
 const mockLlmService = llmService as jest.Mocked<typeof llmService>;
 const mockLocalDreamService = localDreamGeneratorService as jest.Mocked<typeof localDreamGeneratorService>;

__tests__/integration/models/imageDownloadRecovery.test.ts

@@ -12,6 +12,13 @@ const mockModelManager = {
   addDownloadedImageModel: jest.fn(),
 };
 
+// Integrity is a boundary for this recovery test (it exercises the resume/move
+// orchestration, not the completeness rule — that has its own dedicated tests).
+jest.mock('../../../src/utils/imageModelIntegrity', () => ({
+  validateImageModelDir: jest.fn(async () => ({ complete: true, missing: [] })),
+  ensureImageExtractionComplete: jest.fn(async () => {}),
+}));
+
 jest.mock('../../../src/services/backgroundDownloadService', () => ({
   backgroundDownloadService: mockBackgroundDownloadService,
 }));

__tests__/unit/screens/ModelsScreen/imageDownloadActions.test.ts

@@ -25,6 +25,14 @@ jest.mock('react-native-zip-archive', () => ({
   unzip: jest.fn(() => Promise.resolve('/unzipped')),
 }));
 
+// Integrity is a boundary here (these tests cover download orchestration, not the
+// completeness rule — that has its own tests). Default it to "complete" so the mocked
+// RNFS fixtures don't trip the post-unzip gate.
+jest.mock('../../../../src/utils/imageModelIntegrity', () => ({
+  validateImageModelDir: jest.fn(async () => ({ complete: true, missing: [] })),
+  ensureImageExtractionComplete: jest.fn(async () => {}),
+}));
+
 jest.mock('../../../../src/components/CustomAlert', () => ({
   showAlert: jest.fn((...args: any[]) => ({ visible: true, title: args[0], message: args[1], buttons: args[2] })),
   hideAlert: jest.fn(() => ({ visible: false })),

__tests__/unit/screens/ModelsScreen/imageDownloadResume.test.ts

@@ -18,6 +18,13 @@ jest.mock('react-native-zip-archive', () => ({
   unzip: jest.fn(),
 }));
 
+// Integrity is a boundary here (resume orchestration is under test, not the completeness
+// rule). Default to "complete" so mocked RNFS fixtures don't trip the post-unzip gate.
+jest.mock('../../../../src/utils/imageModelIntegrity', () => ({
+  validateImageModelDir: jest.fn(async () => ({ complete: true, missing: [] })),
+  ensureImageExtractionComplete: jest.fn(async () => {}),
+}));
+
 jest.mock('../../../../src/services', () => ({
   modelManager: {
     getImageModelsDirectory: jest.fn(),