changes

docs/v2.0/node-manager-ui.md

@@ -8,6 +8,7 @@ This page documents key WebUI (Node Manager) views and operational behavior in t
 - Widget-based overview of throughput, retransmits, RTT, flow counts, and queue activity.
 - Dashboard content can vary by version and enabled features.
 - Executive Summary provides a compact operational view for large networks, with drilldown pages for executive heatmaps and leaderboards.
+- Bakery provides dedicated status for queue apply state, recent Bakery events, qdisc safety/preflight results, and the existing circuit-activity graph.
 - Some charts may take a short time to populate after first opening a tab, especially on busy systems or immediately after a service restart.
 - During a Bakery full reload, queue-count cards keep showing the last known HTB/CAKE/fq-codel values and mark them as `Reloading` instead of briefly zeroing them.
 

docs/v2.0/treeguard.md

@@ -86,6 +86,10 @@ When enabled and not dry-run, TreeGuard may persist decisions to:
 
 TreeGuard is designed to avoid fighting operator-owned overrides. If operator overrides exist for enrolled entities, TreeGuard skips those entities and reports warnings.
 
+TreeGuard virtual-node decisions are runtime overrides. They are not materialized back into the
+base `network.json` by the scheduler, so disabling or clearing TreeGuard does not permanently
+rewrite operator-authored topology.
+
 TreeGuard also refuses to manage nodes that are already marked `"virtual": true` in the base `network.json`. If stale TreeGuard-owned node-virtualization overrides exist for those nodes, TreeGuard clears its own override layer and falls back to the base topology definition.
 
 For circuit SQM management, TreeGuard treats duplicate `device_id` values as unsafe identity collisions. If the same `device_id` appears in more than one circuit in `ShapedDevices.csv`, TreeGuard skips those affected circuits and clears any TreeGuard-owned SQM overrides for those duplicate device IDs.