Create first optimized workflow masters

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