Conversation
This was referenced Sep 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #354
Summary
sceneas a first-class input and output for model extension nodes/generate/from-artifactroute while preserving/generate/from-imageScope
This PR deliberately supports the reviewable model-node shapes needed by scene workflows:
scene -> meshscene -> scene-> sceneIt fails closed for process extensions, mixed/multiple scene inputs,
capture, andvideo. Shared weight groups remain independent in #348.Shared-weight integration
The Pixal3D consumer requires both this scene contract and shared-weight PR #348. An isolated merge of #348 + #357 + video PR #358 found three overlapping validation conflicts in
generator_registry.py,extension-install-utils.ts, andipc-handlers.ts. The combined resolution preserves scene/video artifact validation, ordered nodeinputs, and node-specific shared-weight projection.The integrated state passed an exact six-node Pixal3D registry check, 100 focused Python tests, 9 focused Node suites, TypeScript
--noEmit, and the Electron/Vite production build. Either PR can merge first; the later branch must apply the documented combined resolution during rebase.Security and compatibility
/generate/from-imagebehavior compatibleValidation
--noEmit: passedelectron-vite build: passedgit diff --check: passedThe full packaging build reached a pre-existing built-in dependency reinstall and was interrupted by DNS (
EAI_AGAIN); the authoritative Electron/Vite production build passed directly.