Add static site generation for GitHub Pages deployment

[michielbdejong]

Summary

This PR adds static site generation capabilities to enable deploying the application as a static site to GitHub Pages. A new Node.js script crawls all public routes and renders them to static HTML files, which are then deployed instead of the raw repository.

Key Changes

• New static-export.js script: Implements a complete static site generation pipeline that:

  • Discovers all public routes by scanning controller files in the os-app directory
  • Generates URLs for each route, including language-specific variants
  • Starts the Express server and fetches each route's rendered HTML
  • Writes responses to .static/ directory with proper directory structure
  • Copies built assets alongside rendered pages for a self-contained static site

• Updated GitHub Actions workflow (static.yml):

  • Changed target branch from master to main
  • Added Node.js setup and dependency installation steps
  • Added build and static export steps before deployment
  • Changed artifact upload path from entire repository ('.') to only the generated .static directory
  • Improved workflow documentation

• Updated package.json:

  • Added static-export npm script that runs the new static generation script
  • Added magic-string version override to resolve dependency conflicts

Implementation Details

• The static exporter intelligently handles different URL types (root paths, language-prefixed routes, and file extensions) and generates appropriate file structures (e.g., /about → .static/about/index.html)
• Routes are filtered to exclude redirects, hidden routes, stub routes, and non-GET methods
• The script waits up to 60 seconds for the server to become ready before crawling
• Redirect responses (3xx status codes) are skipped during crawling
• The server process is properly terminated after static generation completes

https://claude.ai/code/session_01AcjKc8vk2fb84yYZsE8k5d