Orisha Adds Tiered Static Serving

This is a pragmatic upgrade to Orisha’s compile-time performance thesis: keep the fast path frozen into the binary without forcing entire sites into read-only memory.

• –Glob, size, and date rules decide which assets bake and which stay on disk
• –Disk-served files retain strong ETags, conditional requests, cache headers, compression negotiation, and HEAD support
• –Local testing cut generated output from 429 MB to 394 MB while keeping baked and disk latency roughly comparable
• –The tradeoff is operational: disk-tiered assets must ship alongside the binary, and content changes still require careful deployment coordination
• –Profile-guided tiering could eventually automate the hot-versus-cold split instead of relying on hand-written patterns