unit test repairs

docs/BARE-METAL-SETUP.md

@@ -628,6 +628,37 @@ pm2 restart all
 
 ### Step 13: Test Error Tracking
 
+You can test Bugsink is working before configuring the flyer-crawler application.
+
+Switch to the bugsink user and open a Python shell:
+
+```bash
+sudo su - bugsink
+source venv/bin/activate
+bugsink-manage shell
+```
+
+In the Python shell, send a test message using the **backend DSN** from Step 11:
+
+```python
+import sentry_sdk
+sentry_sdk.init("https://YOUR_BACKEND_KEY@bugsink.yourdomain.com/1")
+sentry_sdk.capture_message("Test message from Bugsink setup")
+exit()
+```
+
+Exit back to root:
+
+```bash
+exit
+```
+
+Check the Bugsink UI - you should see the test message appear in the `flyer-crawler-backend` project.
+
+### Step 14: Test from Flyer-Crawler Application (After App Setup)
+
+Once the flyer-crawler application is installed and configured with the DSNs from Step 12:
+
 ```bash
 cd /opt/flyer-crawler
 npx tsx scripts/test-bugsink.ts

src/tests/setup/global.ts

@@ -3,6 +3,8 @@ import { mockLogger } from '../utils/mockLogger';
 
 // Globally mock the logger service so individual test files don't have to.
 // This ensures 'import { logger } from ...' always returns the mock.
+// IMPORTANT: Must also export createScopedLogger as it's used by aiService.server.ts
 vi.mock('../../services/logger.server', () => ({
   logger: mockLogger,
-}));
+  createScopedLogger: vi.fn(() => mockLogger),
+}));