test: harden federation e2e timeout

Author: ddx-checkpoint

CHANGELOG.md

@@ -13,7 +13,8 @@ registry entries are pruned during normal UI/MCP inspection instead of leaving
 blank stale rows that can confuse queue monitors. The frontend CI path now runs
 unit and functional Playwright suites separately so visual/video capture specs
 do not dirty release checks, and the affected E2E helpers serialize DDx binary
-builds to avoid Go build-cache races under high host load.
+builds to avoid Go build-cache races under high host load. Federation E2E now
+allows enough time for the full offline/restart cycle on slower CI runners.
 
 ### Fixed: release and security workflow follow-through
 

cli/internal/server/frontend/e2e/federation-2node.spec.ts

@@ -214,7 +214,7 @@ function firstNonLoopbackIPv4(): string | null {
 // ─── Federation 2-node tests ───────────────────────────────────────────────
 
 test.describe('federation 2-node e2e', () => {
-	test.setTimeout(90_000);
+	test.setTimeout(150_000);
 
 	test('hub /federation lists both nodes; scope=federation merges data; offline+restart cycle', async ({
 		page