Deploy runbooks as static site to GCS for improved UX and availability

Problem

Our runbooks are currently difficult to use:

• Browsing through Git repos is slow during incidents
• No search functionality across all runbooks
• Local checkouts are often outdated
• Unavailable when GitLab is down (as seen in incident production#19996 (closed))

Solution

Create a dedicated runbooks site with better UX for incident responders.

Requirements

• Fast search - Find any runbook or procedure in seconds
• Clean interface - Optimized for reading during incidents
• Always current - Auto-deploys on every merge

Implementation Steps

1. Select static site tool
2. Add static site generation to runbook repo
3. Set up GCS bucket + static hosting
4. Create CI/CD pipeline to deploy on merge
5. (optional) Set up vanity domain in Cloudflare

Success Criteria

• Runbooks accessible independently of main GitLab instance
• Search works without server dependencies
• Updates deploy automatically within 5 minutes
• Page loads in < 2 seconds

References

• Incident: production#19994 (closed)
• Incident Review: production#19996 (closed)

/cc @rnienaber @sarahwalker @kkyrala @swainaina