/*
[RFC-0210] Feature-video runtime. Lazily upgrades native
- Do not touch ambient/background
- RFC-1175: autoplay capability gate — prefers-reduced-motion / navigator.connection.saveData suppress data-autoplay playback (poster stays; manual play unaffected).
- RFC-1175: close Lighthouse gaps — directive-allowlist robots (Schemamap retired, ROBOTS-SURFACE-01), capability-gated video (preload=none, data-bg-video, saveData/reduced-motion), single fetchpriority=high per page (IMG-DELIVERY-05), inlined shared texture token, 24px QR touch targets; RFC-1177 security-headers draft
- RFC-1175 AC-5: plyr.css moved from top-level import into the Plyr branch — keeps the stylesheet lazy so the orchestrator single-chunk import carries no feature-player CSS.
- warpgogol-m000170: plyr.css via ?inline + <style> injection — the plain css import emitted a preload to an asset inlineStylesheets:'always' never writes, so Plyr init threw and silently fell back to native controls on prod.
- warpgogol-m000196: icon sprite served same-origin — `plyr/dist/plyr.svg?url` + `iconUrl` replaces Plyr's cdn.plyr.io default, whose third-party request the axiom capture policy blocks (console-error → certify gate fail).
RFC-0210, RFC-0950, RFC-1311
*/
// RFC-1175: plyr.css is imported inside the Plyr branch below so the
// orchestrator chunk stays free of feature-player styles until a
// [data-video-player] element actually mounts. m000170: the import uses
// Vite `?inline` — astro's inlineStylesheets:'always' removes standalone
// .css assets, so the plain css import left a preload link pointing at a
// file that never shipped (404 → new Plyr never ran). The ?inline string
// rides inside the lazy JS chunk; the