I want to annotate VL.Fuse / vvvv gamma help patches.

The uploaded `.vl` file is XML. Please create a new annotated version of the patch.

Use this workflow:

1. Parse the XML structure.
2. Preserve the functional patch logic.
3. Do not change existing functional node IDs.
4. Do not change existing links.
5. Do not rewire pins.
6. Do not change NodeReferences, dependencies, NugetDependencies or functional values unless explicitly requested.
7. You may add new String IOBox pads as comments.
8. You may change `Bounds` of existing nodes and pads for layout only.
9. You may move nodes and existing pads spatially to create enough room for comments.
10. The output should be a valid `.vl` file.

Commenting style:

* Use English comments.
* Add one large `PATCH OVERVIEW` comment near the top.
* Add short explanatory comments next to important nodes.
* Use community-friendly wording.
* Explain what the node does in this patch, not only what the API name means.
* Explain GPU mental models clearly: threads, dispatch IDs, texture cells, buffers, shader values, domains, read/write passes.
* Use comments like `<- Explains this node...` when the comment is placed to the right of a node.
* Use longer comments for orchestration nodes such as `ComputeGraph`, `ComputeGraph2D`, `ComputeGraph3D`, `RendererScheduler`, `DrawShaderGraph`, `Raymarch`, `TextureSet`, `DispatchThreadId`, `ComputeBuffer`, `AppendBuffer`, `TextureIn`, `BufferIn`, `SampleTexture`, or similar central nodes.

Layout rules:

* Do not simply insert comments into the existing dense layout.
* First identify the main functional chains.
* Stretch those chains vertically, especially on the Y axis, so every comment box has enough room.
* Place comments to the right of the node or node group they explain.
* Make comment boxes wide and tall enough for the entire text to be visible.
* Avoid clipped comment text.
* Avoid relying on scrolling inside comment boxes.
* Avoid overlap between comments, nodes, links, and existing pads.
* Keep the visual dataflow readable from top to bottom or left to right.
* Prefer a clean educational layout over preserving the compact original layout.
* Use the height of each comment box to determine how much vertical spacing is needed before placing the next node or comment.

Comment box sizing rules:

* Make every comment box large enough so the full text is visible in vvvv gamma.
* Do not consider the layout finished until all comment text is fully visible without clipping or scrolling.
* Estimate the required height from the amount of text.
* Short one-sentence comments should still get enough padding.
* Multi-line comments should be wide and tall enough to show all lines.
* Prefer wider comment boxes over very narrow tall boxes.
* If a comment is long, either increase the box height or split it into two nearby comment boxes.
* Leave additional vertical spacing below tall comment boxes before placing the next node or comment.

Validation:

Before returning the file, compare the original and annotated patch:

* Number of functional nodes should stay the same unless only comment pads were added.
* Existing links should stay the same.
* Existing functional node IDs should stay the same.
* New elements should mainly be String comment pads.
* Report what changed: node count, pad count, link count, and whether links were preserved.
* Confirm that only layout/comment changes were made, unless explicitly requested otherwise.

Use this overall style:

* Large overview at the top.
* Explanatory node comments beside the relevant nodes.
* Enough vertical spacing so comments do not overlap.
* Comment boxes large enough that the full text is readable.
* Educational, practical explanations rather than dry API descriptions.
* Preserve the patch as a working VL.Fuse help patch.

Goal:

Create a community-friendly, annotated `.vl` help patch that explains the GPU/Fuse concepts directly inside the patch while preserving the original patch logic.
