Skip to content

feat(workflows): support video model artifacts - #358

Draft
DrHepa wants to merge 2 commits into
lightningpixel:devfrom
DrHepa:feat/345-video-model-artifacts
Draft

DrHepa wants to merge 2 commits into
lightningpixel:devfrom
DrHepa:feat/345-video-model-artifacts

Conversation

@DrHepa

@DrHepa DrHepa commented Sep 21, 2026 •

Copy link
Copy Markdown
Contributor

Closes #345

Summary

  • add scalar video input support for model extension nodes
  • add a durable Load Video workflow source and video artifact registration
  • carry validated video snapshots through Electron, FastAPI, the extension subprocess, and the isolated runner
  • preserve exact composite-model pinning and typed artifact dispatch

Dependencies and review scope

This is a stacked PR on top of scene-artifact PR #357 because both use the generic typed /generate/from-artifact route. Until #357 merges, the diff includes its scene commit. The video-only implementation is commit c60d93df.

The Pixal3D consumer also depends on shared-weight PR #348. A temporary integration merge of #348 + #357 + #358 exposed three overlapping validation conflicts (generator_registry.py, extension-install-utils.ts, and ipc-handlers.ts). The combined resolution preserves both artifact validation and node-specific shared-weight projection and passes the integration checks below. After #348 and #357 land, this branch will be rebased onto current dev, those verified resolutions applied, and the PR marked ready.

Scope

This PR deliberately supports scalar model video artifacts. It rejects video arrays, process-extension video I/O, mixed unsupported inputs, traversal, symlink/reparse escapes, file replacement after validation, and oversized files.

Validation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant