Fix Block wiring, model migration and workflow readiness - #6
Merged
Merged
Conversation
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.
Summary
Fix the workflow authoring defects found during the text-to-image workflow review:
Public controls and sockets remain available. Existing saved libraries are not rewritten. Auto qualification and custom-code consent remain intact.
Paired backend
Backend contract commit:
a0d29db8484f8f06f9d42f6782634cd66e1ac996(also pinned in client CI).Paired backend PR: sdevil7th/MoDiff#6. It includes the generated client bundle from this source commit.
Validation
npm ci: passed; zero reported vulnerabilities.npm run check: passed (format, lint, types, catalog, unit/contracts, build, bundle limits and shell module identity).npm run check:ui: shared controls 3/3; full mocked run 225/230. All five initial failures were fixed and passed in a focused rerun of eight affected scenarios, including native creation/model-change persistence and scalar sockets. No browser failures remain unaddressed./proccleanup-test race (ESRCH); the final complete rerun passed without changing that test.Live backend evidence:
These are focused live checks, not all-model qualification. FLUX Auto refusal remains correct without an accepted exact recipe; SDXL prompt adherence is not changed.
Compatibility and review