test: stabilize browser assertions under CI load

frontend/playwright.config.ts

@@ -6,6 +6,10 @@ export default defineConfig({
   // it mutates demo data via a reset and is run explicitly, not as part of the suite.
   testIgnore: process.env.CAPTURE_EVIDENCE === "1" ? undefined : "**/_*.spec.ts",
   timeout: 30_000,
+  // CI exercises the browser while image scans and container services share the
+  // same runner. Keep assertions strict, but allow successful API-backed route
+  // transitions enough time to render under that bounded load.
+  expect: { timeout: 15_000 },
   fullyParallel: false,
   workers: 1,
   snapshotPathTemplate: "{testDir}/__screenshots__/{arg}{ext}",

n8n/workflows/MANIFEST.md

@@ -121,4 +121,4 @@ this handler was not observed live.
 | Active status | Imported inactive by default; production deployment must publish it before enabling Alertmanager. |
 | Error Workflow | `Fleet Ops — Workflow Error Handler` (wired) |
 | Safety | Strict Alertmanager payload shape, bounded to 25 alerts and bounded text fields. |
-| Checksum (sha256) | `3672ad3d14b65c603c8c3f2067197cc50372e9d4c2fc314d1c9b6aaf3ecef444` |
+| Checksum (sha256) | `4eb1ae41c4e675a9bb51a43722a507da8a6eae8a6ce8649b7e3a57417911a418` |