docs/wrong: document per-tier extent scan task names

After scan-next renamed the per-extent scan task prefix from the static
"next_" to the scanner's name, a thread named like "128K_205ad76b1000_24K"
appears in status output with no matching entry in the thread-name
decoder list.  Add a bullet for it and for the "extent_<tier>" enumerator
task, keyed to the same example extent so the pipeline stages read
together.

Refresh the stale "extent_250_32M_16E" example, which encoded the old
subvol-id plus size-range scheme; extent-scan tiers are now named after
their [scan.extent.NAME] config section.

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

diff --git a/docs/wrong.md b/docs/wrong.md
index f986b1e6af3ee311c3966e541994f3bdd5df211e..33bf908302b8f2b07df51258ca635ae7e563f269 100644 (file)
--- a/docs/wrong.md
+++ b/docs/wrong.md
@@ -61,7 +61,8 @@ Most other threads have names that are derived from the current dedupe
 task that they are executing:
 
  * `ref_205ad76b1000_24K_50`:  extent scan performing dedupe of btrfs extent bytenr `205ad76b1000`, which is 24 KiB long and has 50 references
- * `extent_250_32M_16E`:  extent scan searching for extents between 32 MiB + 1 and 16 EiB bytes long, tracking scan position in virtual subvol `250`.
+ * `128K_205ad76b1000_24K`:  extent scan tier `128K` scanning btrfs extent bytenr `205ad76b1000` (24 KiB long) for dedupe candidates
+ * `extent_128K`:  extent scan tier `128K` enumerating extents in its size range, walking the btrfs extent tree in physical address order
  * `crawl_378_18916`:  subvol scan searching for extent refs in subvol `378`, inode `18916`.
 
 ### Dump kernel stacks of hung processes