feat(studio-server): preview variable injection + render variables forwarding

Fourth PR of the template-variables Studio stack — the HTTP plumbing. - preview routes (/preview and /preview/comp/*) accept ?variables=<url-encoded json> and inject `window.__hfVariables = {...}` into <head>, before the runtime and any composition script — the exact global the engine sets via evaluateOnNewDocument at render time, so preview-with-values cannot diverge from render output. Values are escaped against </script> breakout, malformed payloads 400 instead of silently previewing defaults, and the ETag is salted with a hash of the payload so cached previews revalidate when values change. - POST /projects/:id/render accepts variables ({variableId: value}) and forwards them through StudioApiAdapter.startRender into the producer's RenderConfig.variables — the same channel `hyperframes render --variables` uses. Wired in both adapters (CLI embedded server + vite dev adapter). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-09-03 12:54:29 +00:00 · 2026-07-09 13:31:03 -07:00
parent 91831f3f8e
commit 2e0b884521
8 changed files with 269 additions and 16 deletions
@@ -413,6 +413,7 @@ export function createStudioServer(options: StudioServerOptions): StudioServer {
            outputResolution: opts.outputResolution,
            ...(manualEditsRenderScript ? { renderBodyScripts: [manualEditsRenderScript] } : {}),
            ...(opts.composition ? { entryFile: opts.composition } : {}),
+            ...(opts.variables ? { variables: opts.variables } : {}),
          });
          renderJob = job;
          const onProgress = (j: { progress: number; currentStage?: string }) => {