test(e2e): let the economy screens finish reading the chain before judging them

The nine screens the owner named read the chain, and the render check clears at
2.5s. MEASURED on /dashboard/treasury at 3/8/15/25/40s: at 2.5s it still shows
"…" and "Reading token balances…", and it has settled by 3s — no permanent
skeleton, just a check that was looking too early. So the evidence screenshots
were of a half-loaded page and the chain-context assertion was reading an
ellipsis where the address had not arrived yet.

One 3s settle in the economy block only. It does not soften the assertion —
/dashboard/{safes,mpc,bridge,dex,deploy} still show no network, chainId,
address or height at 3/3 viewports.

Co-authored-by: Hanzo Dev <[email protected]>

e2e/61-console.spec.ts

@@ -129,6 +129,14 @@ test.describe('Economy screens — the owner\'s named surfaces', () => {
     test(`${route} names what it is and which chain it is on`, async () => {
       const r = await expectRendered(page, CLOUD + route, `economy screen ${route}`)
 
+      // These nine screens read the chain, so give them a beat past the 2.5s
+      // paint check before judging what is on them. MEASURED: /dashboard/treasury
+      // shows "…" and "Reading token balances…" at 2.5s and has settled by 3s
+      // (checked at 3/8/15/25/40s — no permanent skeleton). Without this the
+      // owner's evidence screenshots are of a half-loaded page and the context
+      // check below reads an ellipsis instead of an address.
+      await page.waitForTimeout(3_000)
+
       // Says what it is.
       expect(r.heading.length,
         `${route} renders with no heading — an operator cannot tell what screen they are on`)