rcourtman 26a975f461 Keep red e2e shards inside the CI budget ... Proving run 28925348032 showed a shard can still hit the 45-minute job timeout while the suite carries many real failures: shard 4 held the visual crawl (5.3 minutes per attempt, currently failing) plus dozens of 14-second failing attempts, and with two retries the failure storm outran the budget even under the 20-failure cap. Retry once instead of twice on CI, and run the visual crawl only on the desktop project. The mobile emulation projects keep their dedicated mobile specs; a per-project 5-minute crawl was the single most expensive line in the suite.		2026-07-08 09:15:38 +01:00
..
integration	Keep red e2e shards inside the CI budget	2026-07-08 09:15:38 +01:00
migration	Clear all errcheck and gofmt violations so make lint gates on real findings	2026-06-09 21:42:21 +01:00