K2 Plan Report

K2 Plan Report is the "show your working" node of the K2 Lab suite in comfyui-FVMtools. K2 Compose compiles your regions, LoRAs, emphases, and projector into a plan; this node prints that plan to a string so you can read it. It does the same job as Compose's report output, but as a standalone output node you can drop into any workflow when you want the diagnostics without re-thinking the whole graph.

What the report tells you

• Token spans per region - the compiled prompt, annotated with which token range each region clause owns.
• LoRA routing decisions - which targets each LoRA's delta was applied to, and which were skipped.
• locality_skipped_targets - the count of non-local targets a strict regional LoRA deliberately leaves alone (typically 56 of 256; the wk/wv projections are read by every image query, so they can't be location-bound).
• Projector state - whether a projector delta is active and what it's doing.
• Spatial attention summary - the router's calls, which is how you confirm it actually installed.

The point of the node, per the description, is to check that a regional LoRA really matched Krea targets before spending a generation on it. Regional routing can fail silently in ways that look like a bad LoRA: a typo'd region name, a LoRA whose target namespaces don't line up, a region that never got tokens. All of that shows up here.

What to look for

The one number that matters most is in Compose's own report when you sample through K2 Regional Sampler: spatial_attention.main_stream_attention_calls must be greater than zero - 28 blocks × steps, so it's a big number when it's working. Zero means the sequence length didn't line up and the router never fired. LoRA-wise, delta_rms of 0 means the LoRA isn't acting. And the warnings list should be empty; the author's own guidance is that an empty list is good.

For the routing report in this node specifically: a regional LoRA with an impossible assignment shows up as skipped targets, and looks_like_krea2 from K2 LoRA Info tells you whether the file was ever capable of routing at all. Run both when something's off.

Install

Same as the whole pack:

cd ComfyUI/custom_nodes
git clone https://github.com/ping1979ping/comfyui-FVMtools

Restart ComfyUI, find it under FVM Tools/K2. No extra dependencies. It's an output node - feed it a plan from K2 Compose and read the report string, or wire the string to a text display/save node if you want it in a file.

This is the node that separates "I hope this works" from "I can see it will work." Once you've read a few of these reports you'll spot routing problems before they cost you renders, which is the entire point of it existing.