Adds generate_bridge.js, a small ES-module shim over the untouched
app/shell/run.js + session.js + pipeline.js + client.js, and rewires
store.js's generate()/generateMontage()/generateSelected()/interrupt()/
init() reattach to go through it instead of the now-permanently-stubbed
API.generate/status/active. PipelineState (pipeline_state.js) stays the
one client-side copy of the live pipeline; the bridge only adds the
run/queue/socket layer on top of it.
Single scene (or the whole active timeline, for a non-chain pipeline like
H3) per real queue -- v5 has no chain-sampler/montage stage. REINS captures
and the anchor-guide i2v bypass are said loudly (console.warn) rather than
silently dropped, since neither has a v5 equivalent yet. Reference-image
wiring is left as a placeholder: legacy's saveProject/getProject adapter
doesn't round-trip source_image/references yet, so there is nothing to
wire in from there today.
Live-verified against the real dev server: a real Generate click built the
scene's prompt, POSTed it through /funpack/api/pipeline's check, and
surfaced the genuine refusal reason (an unset model loader) in the existing
status UI, with the button correctly re-enabled after. 688/689 JS tests
and 548/548 Python tests pass (the one JS failure is the pre-existing,
unrelated projects.test.js import-race flake).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
