bees-config-v2: align embedded config comments with scanner model

The built-in v1 config comments are the source that docs/config-file.md
documents, so they must use the same object model: each [scan.extent.NAME]
section configures one scanner (a size tier), not "one crawler scanning
extents", and first-transid describes where a newly-created scanner
starts relative to existing scanners.

Assisted-by: Claude-Code:claude-opus-4-8

diff --git a/src/bees-config-v2.cc b/src/bees-config-v2.cc
index 7eac9ee4057b89ecf60ecdbe5fb40d61f6cf0a18..24dd4d60733f5e1a642445a09fb12065cd2dd76b 100644 (file)
--- a/src/bees-config-v2.cc
+++ b/src/bees-config-v2.cc
@@ -233,8 +233,12 @@ static const char bees_config_v2[] = R"--v2-config--(
 
 [state]
 
+# The [scan.subvol] section controls legacy subvol scanners (scan modes 0-3).
+
+[scan.subvol]
+
 # The [scan.extent.*] sections define extent-scan size tiers.  Each section
-# corresponds to one crawler scanning extents in the named size range.
+# configures one scanner that processes extents in the named size range.
 # Section names are opaque labels; the size range is set by size-min/size-max.
 # The legacy-id key maps beescrawl.dat root IDs to section names on upgrade.
 # See docs/config-file.md for recommended filter-chain ordering and
@@ -248,10 +252,10 @@ static const char bees_config_v2[] = R"--v2-config--(
         # 1 = scan_next_extent
         method = 0
 
-        # Where a newly-created crawler starts scanning, used only the first
+        # Where a newly-created scanner starts, used only the first
         # time a tier is created (no saved position in beespoint.ini).  An
         # existing tier always resumes from its saved position regardless.
-        #   min     = lowest min-transid of existing crawlers (default)
+        #   min     = lowest min-transid of existing scanners (default)
         #   zero    = beginning of the filesystem; scan all existing data
         #   current = current filesystem transid; skip all existing data
         first-transid = min