diff --git a/docs/plans/2026-09-06-campaign-vt-slice1-files-and-columns.md b/docs/plans/2026-09-06-campaign-vt-slice1-files-and-columns.md
index 1e2cbde8..3f622531 100644
--- a/docs/plans/2026-09-06-campaign-vt-slice1-files-and-columns.md
+++ b/docs/plans/2026-09-06-campaign-vt-slice1-files-and-columns.md
@@ -63,7 +63,10 @@ back as `.af` that metaf itself accepts. Proof: (1) every
 `.af` conversion equals our model loaded from the matching `.af` in `af/`
 where both exist; (4) the writer's output for at least five fixtures is
 byte-identical to metaf's canonical emission after comment stripping. Also:
-the `.utl` `BuffedInt/Double` base-key-exists gate; the jump-charge clamp to
+the `.utl` `BuffedInt/Double` base-key-exists gate AND the branch selector
+mis-port found by the KB 05 citation pass (`VtankLootRequirementEvaluator.cs:445`
+tests `Bonus` where VTClassic tests `Change`, `ComputedItemInfo.cs:244`; carry
+both fields in the table); the jump-charge clamp to
 2000 ms applied to `jmp` nodes at load. Each with a real-file fixture and a
 round-trip test. Line-numbered parse errors (file:line, what was expected).
 
diff --git a/docs/research/vtank-kb/09-commands-and-interop.md b/docs/research/vtank-kb/09-commands-and-interop.md
index 50b4eacb..a245482c 100644
--- a/docs/research/vtank-kb/09-commands-and-interop.md
+++ b/docs/research/vtank-kb/09-commands-and-interop.md
@@ -13,9 +13,9 @@ plugin, `MosswartMassacre/vTank.cs` + `VtankControl.cs`. acdream side:
 `src/AcDream.App/Plugins/AppAutomationSurface.cs`,
 `src/AcDream.Core/Plugins/PluginCommandRegistry.cs`. All decompiled facts
 are cited `file:line` against `refs/vtank/decompiled/...` unless another
-root is named. `utilitybelt.service` at
-`C:\Users\erikn\source\repos\utilitybelt.service` was checked and has **no**
-VTank/uTank2 integration in its available source (see §6).
+root is named. UtilityBelt's VTank integration lives in the full source at
+`C:Userseriknsource
eposutilitybelt.gitlab.io` (the older
+`utilitybelt.service` clone has none) — see §6 for the Harmony-patch route.
 
 ## How `/vt` reaches the parser