ci: bound the demo and pre-commit jobs

[vringar]

Stacked on #1233 — same concern, making CI's time budget coherent rather than arbitrary.

Only tests sets timeout-minutes. demo and pre-commit inherit GitHub's default of 360 minutes, and both are required status checks, so the merge queue blocks on them.

That has two consequences:

1. A hung job burns six hours. demo drives a real browser; if it wedges, nothing stops it for the rest of the working day.
2. The queue's timeout cannot be derived. check_response_timeout_minutes should be the maximum time any required check can take, plus an allowance for runner wait. With two of the nine required contexts bounded only by a six-hour default, "the maximum" is six hours, so any queue timeout is a guess.

Ten minutes, against observed runtimes of roughly 2m17s (demo) and 2m27s (pre-commit) — generous by a factor of four.

Why this makes the queue timeout principled

The two clocks measure different things and start at different moments:

entry created ─── waiting for a runner ─── job starts ─── job runs ─── reports
                  ^^^^^^^^^^^^^^^^^^^^^                   ^^^^^^^^^
                  queue counts this                       both count this
                  timeout-minutes does not

timeout-minutes bounds execution; the merge queue bounds time to hear back, which additionally contains the runner wait — unbounded, and inside no job's timeout. With grouping_strategy: ALLGREEN the batch waits on the slowest of all nine required contexts at once.

After this change every required check is capped at 30 minutes, so the queue's 60-minute setting is exactly that maximum plus an equal allowance for contention, instead of a number picked to be larger than the worst run anyone happened to observe.

Context: merge queue entries were timing out against the previous 20-minute setting while every underlying run succeeded — observed merge-queue durations of 27, 33, 39 and 42 minutes. That setting has been raised to 60 separately, in the ruleset.

actionlint passes.

[Copilot]

🟢 Approval recommended

The change is minimal, valid YAML, and cleanly achieves the stated goal without altering job logic.

Pull request overview

This PR makes the CI time budget more predictable by explicitly bounding the demo and pre-commit GitHub Actions jobs, which previously inherited GitHub’s 360-minute default timeout and could block required status checks for hours.

Changes:

• Add timeout-minutes: 10 to the pre-commit job.
• Add timeout-minutes: 10 to the demo job.

File summaries

File	Description
.github/workflows/run-tests.yaml	Adds explicit 10-minute timeouts to pre-commit and demo, bringing all required checks under explicit caps (with tests already at 30 minutes).

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.23%. Comparing base (14745c4) to head (c01d9d3).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1234      +/-   ##
==========================================
- Coverage   62.34%   62.23%   -0.11%     
==========================================
  Files          40       40              
  Lines        3930     3930              
==========================================
- Hits         2450     2446       -4     
- Misses       1480     1484       +4     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.