Create first optimized workflow masters

optimized/README.md

@@ -26,6 +26,14 @@ These workflows are intended to become the practical default choices for each ca
 - `text-to-video/`
 - `upscale-restoration/`
 
+## Current best-current masters
+
+- `text-to-image/zimage-turbo-3070-fast-start/`
+- `image-edit/zimage-turbo-3070-inpaint-start/`
+- `image-edit/flux2klein-9b-fp8-edit-master/`
+- `image-to-video/ltx23-3070-simple-master/`
+- `text-to-video/minimax-h3-3070-turbo-master/`
+
 ## Workflow format
 
 Each optimized workflow should have its own folder and usually include:

optimized/image-edit/README.md

@@ -1,3 +1,8 @@
 # Image Edit Masters
 
 Home for maintained category masters focused on image editing, inpainting, outpainting, and reference-driven edits.
+
+## Current masters
+
+- `zimage-turbo-3070-inpaint-start`
+- `flux2klein-9b-fp8-edit-master`

optimized/image-edit/flux2klein-9b-fp8-edit-master/README.md

@@ -0,0 +1,61 @@
+# FLUX.2-klein 9B FP8 Edit Master
+
+## Summary
+
+Best current `FLUX.2-klein` image-edit master for your setup.
+
+This is built from the official `9B distilled` template because it matches your `9B fp8` preference while still leaning toward practicality rather than the heavier `base` route.
+
+## Status
+
+- `best-current`
+- `not-yet-tested-on-chris-box`
+
+## Workflow asset
+
+- `workflow.json`
+
+## Built from
+
+- `models/flux2klein/image-edit-9b-distilled/`
+
+## Why this is the current master
+
+- Matches your default family: `FLUX.2-klein 9B fp8`
+- Official Comfy template is a safer foundation than community pages with weak provenance.
+- Distilled is the most sensible first optimization bias for a `3070`.
+
+## What I intentionally kept
+
+- official Comfy node layout
+- official `9B fp8` model path
+- official text-encoder pairing
+- speed-first distilled route
+
+## What I intentionally did not add yet
+
+- community `GGUF` ideas
+- KV-cache experimentation
+- extra custom-node edits with unclear payoff
+- a fake outpainting claim before we prove it on your machine
+
+## Required models
+
+- `models/diffusion_models/flux-2-klein-9b-fp8.safetensors`
+- `models/text_encoders/qwen_3_8b_fp8mixed.safetensors`
+- `models/vae/flux2-vae.safetensors`
+
+## Required custom nodes
+
+- none beyond current official Comfy support for the template nodes
+
+## Monday test checklist
+
+- Confirm the model paths line up with your local layout.
+- Test a plain edit, then an expand-canvas outpaint attempt.
+- Compare `9B distilled` behavior against any `4B distilled` outpaint workflow you already trust.
+
+## Next optimization candidates
+
+- clone this into a dedicated outpaint master if the graph behaves well
+- borrow only proven community prompt or graph hygiene improvements

optimized/image-edit/zimage-turbo-3070-inpaint-start/README.md

@@ -0,0 +1,61 @@
+# Z-Image Turbo 3070 Inpaint Start
+
+## Summary
+
+Best current `Z-Image` edit starter for inpainting on tighter VRAM.
+
+This master is a curated hold of the community inpainting workflow because it gives us a real edit path while still staying more plausible on a `3070` than heavier image stacks.
+
+## Status
+
+- `best-current`
+- `not-yet-tested-on-chris-box`
+
+## Workflow asset
+
+- `workflow.json`
+
+## Built from
+
+- `models/zimage/z-image-turbo-inpainting-community/`
+
+## Why this is the current master
+
+- It is the strongest actual `Z-Image Turbo` edit workflow we have right now.
+- Editing matters more than toy text-to-image wins for practical day-to-day use.
+- The graph is specific enough to be useful without being a giant kitchen-sink workflow.
+
+## What I intentionally kept
+
+- inpainting-focused graph shape
+- existing `ZImageFunControlnet` route
+- community sampler path that is already wired for edit work
+
+## What I intentionally did not add yet
+
+- control-union extras from the separate community workflow
+- any manual sampler surgery before real testing
+- any claim that this is better than `FLUX.2-klein` for edits
+
+## Required models
+
+- `models/text_encoders/qwen_3_4b.safetensors`
+- `models/diffusion_models/z_image_turbo_bf16.safetensors`
+- `models/vae/ae.safetensors`
+
+## Required custom nodes
+
+- `rgthree-comfy`
+- the package that provides `LanPaint_KSampler`
+- the package that provides `ZImageFunControlnet`
+
+## Monday test checklist
+
+- Confirm missing custom nodes first.
+- Check whether masked edits are stable enough to keep.
+- Compare it directly against the `flux2klein` edit master on the same input.
+
+## Next optimization candidates
+
+- reduce custom-node dependency count if the graph is good but fragile
+- borrow only the useful control ideas from the community control-union workflow

optimized/image-to-video/README.md

@@ -1,3 +1,7 @@
 # Image-to-Video Masters
 
 Home for maintained category masters focused on image-to-video generation.
+
+## Current masters
+
+- `ltx23-3070-simple-master`

optimized/image-to-video/ltx23-3070-simple-master/README.md

@@ -0,0 +1,56 @@
+# LTX 2.3 3070 Simple Master
+
+## Summary
+
+Best current `LTX 2.3` low-complexity starter for local video work.
+
+This master uses the simple single-pass workflow instead of the more ambitious first-last-frame or character-sheet variants because your `3070` needs a realistic first foothold, not the fanciest graph on paper.
+
+## Status
+
+- `best-current`
+- `not-yet-tested-on-chris-box`
+
+## Workflow asset
+
+- `workflow.json`
+
+## Built from
+
+- `models/ltx/ltx23-i2v-t2v-simple-single-pass/`
+
+## Why this is the current master
+
+- Most plausible `LTX` starting point on tighter VRAM
+- Simpler graph means less time chasing broken helper nodes
+- Supports both `image-to-video` and `text-to-video` style experimentation from one baseline
+
+## What I intentionally kept
+
+- single-pass graph shape
+- split-model assumption from the source pack
+- lighter starting complexity than the bigger RuneXX graphs
+
+## What I intentionally did not add yet
+
+- first-last-frame complexity
+- character-sheet consistency branches
+- extra memory-efficiency gadgets unless needed
+
+## Required custom nodes
+
+- `ComfyUI-KJNodes`
+- `rgthree-comfy`
+- `easy use` / `easy showAnything`
+- optional `ComfyUI-GGUF` support remains present in the source graph
+
+## Monday test checklist
+
+- Confirm whether it loads at all on the `3070`.
+- Check whether preview/decode settings feel like the real bottleneck.
+- If it works, then try the heavier first-last-frame workflow second.
+
+## Next optimization candidates
+
+- strip unused optional loader paths if they create confusion
+- create a separate `first-last-frame` master only if the simple master proves viable

optimized/notes/README.md

@@ -11,3 +11,12 @@ Use it to capture:
 - what should be ignored next time
 
 These notes exist so future review passes do not have to re-trawl every collected workflow from scratch.
+
+## Current note files
+
+- `flux.md`
+- `flux2klein.md`
+- `ltx.md`
+- `minimax.md`
+- `zimage.md`
+- `reviews/`

optimized/notes/ltx.md

@@ -0,0 +1,35 @@
+# LTX Notes
+
+## Current default assumptions
+
+- Low-VRAM practicality matters more than graph sophistication.
+- The first question is whether `LTX 2.3` is usable at all on Chris's `3070`.
+
+## Strong current source workflows
+
+- `models/ltx/ltx23-i2v-t2v-simple-single-pass/`
+- `models/ltx/ltx23-t2v-simple-single-pass/`
+- `models/ltx/ltx23-first-last-frame/`
+- `models/ltx/ltx23-character-sheet-best-face-id/`
+
+## Strong current heuristics
+
+- Start with simple single-pass before trying larger consistency graphs.
+- Prefer split-model and extracted-model routes when the source pack says they are easier locally.
+- Treat first-last-frame and character-sheet workflows as second-wave tests, not the baseline.
+
+## Current weak areas
+
+- No real proof yet for what is genuinely practical on Chris's box.
+- Community packs bundle lots of helper nodes, which raises import fragility.
+
+## Best current optimization direction
+
+- Keep `optimized/image-to-video/ltx23-3070-simple-master/` as the first `LTX` default.
+- Only promote first-last-frame or character-sheet variants after the simple master proves viable.
+
+## What needs Monday proof
+
+- whether the simple master loads and runs at all on the `3070`
+- whether preview/decode or the core model path is the real bottleneck
+- whether `LTX` has any realistic chance of displacing `MiniMax` for local use

optimized/notes/minimax.md

@@ -0,0 +1,35 @@
+# MiniMax Notes
+
+## Current default assumptions
+
+- `MiniMax H3` is promising, but brute-force paths are too heavy to be the first bet on a `3070`.
+- Speed-first and low-VRAM community workflows matter more than official purity for the first real test.
+
+## Strong current source workflows
+
+- `models/minimax/minimax-h3-official-t2v/`
+- `models/minimax/minimax-h3-official-i2v/`
+- `models/minimax/minimax-h3-turbo-lora-community/`
+- `models/minimax/minimax-h3-int8-r2v-community/`
+
+## Strong current heuristics
+
+- Prefer Turbo LoRA for the first `text-to-video` attempt.
+- Prefer INT8-based community workflows for `reference-to-video` exploration.
+- Keep attention and memory-efficiency helpers if they are already integrated and well documented.
+
+## Current weak areas
+
+- No proof yet that MiniMax is truly practical on Chris's box.
+- Custom-node stack is more fragile than the current `flux2klein` path.
+
+## Best current optimization direction
+
+- Keep `optimized/text-to-video/minimax-h3-3070-turbo-master/` as the first MiniMax default.
+- Keep the INT8 reference-video workflow as the next donor for future low-VRAM optimization.
+
+## What needs Monday proof
+
+- whether the Turbo LoRA workflow is just technically possible or actually usable
+- whether the source-recommended `8`-step path holds up in quality
+- whether MiniMax feels like a real challenger to `LTX` locally

optimized/notes/process.md

@@ -13,7 +13,7 @@
 2. `zimage`
 3. `ltx`
 4. `minimax`
-4. category masters in:
+5. category masters in:
    - `image-edit`
    - `image-to-video`
    - `text-to-video`

optimized/notes/reviews/2026-08-08-first-pass.md

@@ -0,0 +1,42 @@
+# Optimization Review 2026-08-08
+
+## Scope
+
+First manual optimization pass before the Sunday cadence has enough historical material to build from.
+
+## Created masters
+
+- `optimized/text-to-image/zimage-turbo-3070-fast-start/`
+- `optimized/image-edit/zimage-turbo-3070-inpaint-start/`
+- `optimized/image-edit/flux2klein-9b-fp8-edit-master/`
+- `optimized/image-to-video/ltx23-3070-simple-master/`
+- `optimized/text-to-video/minimax-h3-3070-turbo-master/`
+
+## Source workflows used
+
+- `models/zimage/z-image-turbo-official-example/`
+- `models/zimage/z-image-turbo-inpainting-community/`
+- `models/flux2klein/image-edit-9b-distilled/`
+- `models/ltx/ltx23-i2v-t2v-simple-single-pass/`
+- `models/minimax/minimax-h3-turbo-lora-community/`
+
+## What was optimized in this pass
+
+- Chose low-complexity or speed-first baselines instead of heavier graphs.
+- Aligned `flux2klein` with Chris's `9B fp8` preference.
+- Treated `LTX` and `MiniMax` as "prove viability first" families.
+- Added durable notes so future passes can build on judgments instead of re-reading everything.
+
+## What was deliberately not done
+
+- no graph surgery without testing
+- no blind node removal
+- no fake "one workflow to rule them all" claims
+- no promotion of first-last-frame or INT8 reference-video paths to default status yet
+
+## Monday proof needed
+
+- whether the two `Z-Image` masters are actually lighter and pleasant to use
+- whether `flux2klein 9B distilled` behaves well enough for edit/outpaint work
+- whether the `LTX` simple master is viable on a `3070`
+- whether `MiniMax Turbo` is practically usable or still too tight

optimized/text-to-image/README.md

@@ -1,3 +1,7 @@
 # Text-to-Image Masters
 
 Home for maintained category masters focused on text-to-image generation.
+
+## Current masters
+
+- `zimage-turbo-3070-fast-start`

optimized/text-to-image/zimage-turbo-3070-fast-start/README.md

@@ -0,0 +1,61 @@
+# Z-Image Turbo 3070 Fast Start
+
+## Summary
+
+Best current `text-to-image` starter for a lighter local box.
+
+This master stays close to the official `Z-Image Turbo` example because that is still the cleanest and most portable `Z-Image` graph in the repo.
+
+## Status
+
+- `best-current`
+- `not-yet-tested-on-chris-box`
+
+## Workflow asset
+
+- `workflow.png`
+- Load it by dragging the PNG into ComfyUI.
+
+## Built from
+
+- `models/zimage/z-image-turbo-official-example/`
+
+## Why this is the current master
+
+- Official source beats community guesswork for a first baseline.
+- `Z-Image Turbo` looks like one of the strongest fast-image candidates for a `3070`.
+- The graph is simple enough to troubleshoot without drowning in custom-node noise.
+
+## What I intentionally kept
+
+- Official model wiring
+- Official `qwen_3_4b` text encoder path
+- Embedded PNG workflow format for easy import
+
+## What I intentionally did not add yet
+
+- community patch nodes
+- extra control branches
+- reference-image complexity
+- "magic" speed hacks without proof
+
+## Required models
+
+- `models/text_encoders/qwen_3_4b.safetensors`
+- `models/diffusion_models/z_image_turbo_bf16.safetensors`
+- `models/vae/ae.safetensors`
+
+## Required custom nodes
+
+- none beyond current official Comfy support
+
+## Monday test checklist
+
+- Confirm it imports cleanly from PNG on your current Comfy build.
+- Check whether it really feels lighter than your usual FLUX path.
+- Check whether prompt adherence is good enough to justify keeping it as the `fast-start` master.
+
+## Next optimization candidates
+
+- merge in useful edit/reference ideas from the community `Z-Image` graphs
+- build a stronger prompt preset if the base graph is good but inconsistent

optimized/text-to-video/README.md

@@ -1,3 +1,7 @@
 # Text-to-Video Masters
 
 Home for maintained category masters focused on text-to-video generation.
+
+## Current masters
+
+- `minimax-h3-3070-turbo-master`

optimized/text-to-video/minimax-h3-3070-turbo-master/README.md

@@ -0,0 +1,65 @@
+# MiniMax H3 3070 Turbo Master
+
+## Summary
+
+Best current `MiniMax H3` speed-first starter for local text-to-video tests.
+
+This master is built from the community Turbo LoRA workflow because standard MiniMax paths are too expensive to be the first serious attempt on a `3070`.
+
+## Status
+
+- `best-current`
+- `not-yet-tested-on-chris-box`
+
+## Workflow asset
+
+- `workflow.json`
+
+## Built from
+
+- `models/minimax/minimax-h3-turbo-lora-community/`
+
+## Why this is the current master
+
+- Explicitly optimized for lower step count
+- Much more aligned with your hardware than generic official baselines
+- Clear developer guidance exists for key settings
+
+## What I intentionally kept
+
+- Turbo LoRA route
+- `8`-step recommendation from the source notes
+- `euler` sampler direction
+- MiniMax acceleration helpers already wired in the graph
+
+## What I intentionally did not add yet
+
+- INT8 reference-video complexity from the separate community workflow
+- extra latent upscale stages
+- broad claims that MiniMax beats `LTX` before we see real results
+
+## Required custom nodes
+
+- MiniMax-compatible Comfy support
+- `ComfyUI-KJNodes`-style helper nodes present in the graph
+- optional acceleration stack may include SageAttention, Sol Attention, Gradient, and Spectrum support
+
+## Expected source model route
+
+- Turbo LoRA source notes recommend:
+  - `minimax_h3_turbo_v4_step600_ema_pruned_comfyui.safetensors`
+  - `8` steps
+  - `euler`
+  - `beta`
+  - LoRA strength `1.0`
+
+## Monday test checklist
+
+- Confirm whether all MiniMax helper nodes resolve.
+- Try the source-recommended settings before changing anything.
+- Judge whether this is merely "possible" or actually practical on your box.
+
+## Next optimization candidates
+
+- merge proven low-VRAM ideas from the INT8 R2V workflow
+- split out an `image-to-video` MiniMax master if the family proves worth keeping