From b26868247d3ee98ffd0507cc798dcd30b72ba5e6 Mon Sep 17 00:00:00 2001
From: haohuaijin <haohuaijin@gmail.com>
Date: Tue, 3 Nov 2026 20:23:19 +0800
Subject: [PATCH] docs: note how remote node profiles nest in the profile types

---
 src/flight/src/profile.rs | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/flight/src/profile.rs b/src/flight/src/profile.rs
index 0556a6aa8c..f8fcf7e6ad 100644
--- a/src/flight/src/profile.rs
+++ b/src/flight/src/profile.rs
@@ -38,7 +38,7 @@ pub struct ProfileNode {
     pub metrics: Vec<ProfileMetric>,
     #[serde(default, skip_serializing_if = "Vec::is_empty")]
     pub children: Vec<ProfileNode>,
-    /// Only on a remote scan, which then has no children: one entry per remote node.
+    /// Only on a remote scan, which then has no children: one entry per node it called directly.
     #[serde(default, skip_serializing_if = "Vec::is_empty")]
     pub remote: Vec<RemoteNodeProfile>,
 }
@@ -85,6 +85,7 @@ pub struct RemoteNodeProfile {
     pub skipped: bool,
     #[serde(default, skip_serializing_if = "Option::is_none")]
     pub scan_stats: Option<ScanStats>,
+    /// The plan this node ran; its own remote scans nest the nodes below it the same way.
     #[serde(default, skip_serializing_if = "Option::is_none")]
     pub plan: Option<ProfileNode>,
 }