feat(producer): support entryFile for rendering individual compositions

[miguel-heygen]

Changes

• Add optional entryFile parameter to render API endpoints (/v1/render and /v1/render-stream)
• Enable rendering individual sub-compositions by extracting them from index.html context when the entry file is a <template> wrapper
• Change base64 audio/video linting from detecting "fabricated" media to prohibiting all inline base64 media
• Add manifest path resolution for bundled producer deployments

API Changes

• RenderConfig — new optional entryFile field for specifying HTML file to render
• server.ts — parses entryFile from request body, validates file exists in project directory
• executeRenderJob — uses entryFile instead of hardcoded "index.html"

Template Extraction

• extractStandaloneEntryFromIndex — extracts sub-composition hosts from index.html and creates standalone render context
• Handles <template> entry files by finding matching data-composition-src in index.html and isolating that host
• Resets data-start to 0 for standalone rendering

Linting Updates

• Change rule feat(core): add compiler entry point and runtime composition fixes #3.7 from detecting "fabricated" base64 media to prohibiting all inline base64 audio/video
• Lower detection threshold from 100+ to 20+ base64 characters
• All base64 media now triggers error severity with clearer messaging about file size bloat

Usage

POST /v1/render-stream
{ "projectDir": "/path/to/project", "entryFile": "compositions/intro.html" }

Omit entryFile for default behavior (renders index.html).

[miguel-heygen]

Merge activity

• Mar 27, 3:28 AM UTC: @miguel-heygen merged this pull request with Graphite.