fix(producer): skip @font-face injection for OS system fonts

[Pran-Ker]

Problem

GENERIC_FAMILIES only covers CSS generic keywords (sans-serif, serif, monospace, etc.) but not named OS system fonts. When a composition uses a font-family stack like:

font-family: 'Courier New', Courier, monospace;

The compiler extracts Courier New and Courier as unresolved web fonts and attempts Google Fonts resolution for them. In headless render environments (the primary use case for hyperframes render) this produces [non-blocking] Failed to load resource: 404 for every system font in every stack — one per font name per composition.

The noise appears in the render output like this:

[Compiler] Injected deterministic @font-face rules for 2 requested font families
[non-blocking] Failed to load resource: the server responded with a status of 404 (Not Found)
[non-blocking] Failed to load resource: the server responded with a status of 404 (Not Found)

Even when the fallback to the OS font works correctly, this is misleading and wastes resolution time. For fonts without an alias (e.g. Arial, Tahoma, Georgia, Helvetica Neue) the compiler hits Google Fonts — which always fails in a sandboxed headless renderer — before falling back.

Fix

Add a SYSTEM_FONTS constant covering ~120 well-known pre-installed fonts across Windows, macOS, and Linux. Extend the skip guard in extractRequestedFontFamilies() to bail on these alongside the existing GENERIC_FAMILIES check.

if (!normalized || GENERIC_FAMILIES.has(normalized) || SYSTEM_FONTS.has(normalized)) {
  continue;
}

System fonts are already present on the render machine — injecting @font-face for them is unnecessary and actively harmful in headless environments.

Fonts covered

• Windows: Arial, Calibri, Cambria, Comic Sans MS, Consolas, Courier New, Georgia, Impact, Palatino Linotype, Segoe UI, Tahoma, Times New Roman, Trebuchet MS, Verdana, and ~30 more
• macOS: Helvetica, Helvetica Neue, SF Pro, SF Mono, Menlo, Monaco, Optima, Futura, Gill Sans, Baskerville, and ~20 more
• Linux: DejaVu, Liberation, Ubuntu, Cantarell, Droid, Noto families

Testing

Reproduce before this fix by creating a composition with font-family: 'Courier New', Courier, monospace and running npx hyperframes render. The 404 noise disappears after this change.

[jrusso1020]

@Pran-Ker Thanks for raising this PR and surfacing the issue! After a deeper look I put up a PR here #313 to help suppress the noisy log.

The concern with the approach you took is that it could change our font resolution logic leading to visual inconsistencies between preview and render, so we wanted to take a slightly safer route!