[mrbobbytables]

Remit: required CI check latency. "End-to-end coverage" is now the longest required check (~6 min, 210s of it the Playwright run at --workers=2).

What changes

• test:e2e:coverage no longer passes --workers=2, so the lane uses the config's workers: 4 like the gating lane. The cap dates from test: measure source-mapped browser coverage without gating merges #916, when the lane was non-gating, and nothing recorded a reason for it.

Verification

• Experiment: compare this PR's "Run e2e tests with coverage" step against the 210s baseline and confirm the coverage report still renders and passes its gate. Close without merging if not faster or if artifacts conflict.

[netlify]

✅ Deploy Preview for endusers ready!

Name	Link
🔨 Latest commit	42f92aa
🔍 Latest deploy log	https://app.netlify.com/projects/endusers/deploys/6ade6009710f03e50cfd7865
😎 Deploy Preview	https://deploy-preview-1912--endusers.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[hivecommons-hive]

42f92aa

ℹ️ Sentinel notice — informational; author is trusted (owner), merge is not blocked

Hive flagged this PR (author @mrbobbytables, head 42f92aa1422c) because it matches behaviors that can override security controls, escalate privileges or damage the codebase. This is a heuristic, not an accusation — a maintainer should confirm the change is intended before it merges.

• sensitive_path — changes 1 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
  • package.json

Hive did not add the sentinel-alert label because this author is trusted. The finding remains recorded for audit and the dashboard Security tab; set sentinel.trusted_authors_block: true to require the blocking label for trusted authors too.

[mrbobbytables]

Measured: "Run e2e tests with coverage" took 152s with 4 workers (this PR) and 152s with 2 workers (#1913, same day, same runner class). The coverage lane is CPU-bound on V8 coverage collection rather than on page I/O, so the extra workers buy nothing. Closing without merging, as the description said; the --workers=2 cap stays.