ci: cap validate-build at 15 minutes

[JakeSCahill]

Summary

Adds timeout-minutes: 15 to the build job in validate-build.yml. Successful runs finish in 1-2 minutes; without a cap, a wedged npm ci occupies a runner for GitHub's full 6-hour default before being cancelled.

This is exactly what hit #395: the branch had been idle 9 days, so the node_modules cache had been evicted, the resulting real npm ci stalled on the registry with no output, and the job hung for 6 hours before GitHub killed it - reported as an opaque check failure on a commit that only touched a header partial. (A re-run passed with no changes.)

15 minutes is ~7x headroom over the slowest observed successful run, and the workflow already uses timeout-minutes on its Go lint step.

Test plan

• validate-build passes on this PR (the change is the workflow itself)

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for docs-ui ready!

Name	Link
🔨 Latest commit	8955b03
🔍 Latest deploy log	https://app.netlify.com/projects/docs-ui/deploys/6a96edbbf3e95200082ecf70
😎 Deploy Preview	https://deploy-preview-429--docs-ui.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 28 (🟢 up 2 from production) Accessibility: 89 (no change from production) Best Practices: 83 (🔴 down 9 from production) SEO: 89 (no change from production) PWA: - View the detailed breakdown and full score reports
🤖 Make changes	Run an agent on this branch

---

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

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 16116d16-ff5c-495a-8deb-629d1cf68bbf

📥 Commits

Reviewing files that changed from the base of the PR and between 663019b and 8955b03.

📒 Files selected for processing (1)

• .github/workflows/validate-build.yml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The validate-build workflow now sets a 15-minute timeout on its build job. An explanatory comment states that normal runs take 1–2 minutes and that the limit prevents a stalled npm ci from using GitHub’s default six-hour runner limit.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 8955b

This change caps the build validation job at 15 minutes to prevent indefinitely hung runs; no actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: limiting the validate-build workflow to 15 minutes.
Description check	✅ Passed	The description accurately explains the timeout change, its purpose, observed runtime context, and test plan.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jake/validate-build-timeout

---

_{Comment @coderabbitai help to get the list of available commands.}