docs: the sweep fix belongs in the v3.1.8 entry

Author: Kelsidavis

CHANGELOG.md

@@ -30,6 +30,7 @@
 - **Two faults in Warden's native relocation loop, both reachable from module bytes the server supplies.** The bounds check added four to a `uint32` target, so `FF FF FF FF` wrapped to 3 and let the write land at image + 0xFFFFFFFF; and the absolute form kept its form flag in the value, so every absolute entry came out past the end of any image the parser accepts and was rejected. From #122
 - **A module that will not unpack says why.** "Could not parse copy/skip pairs (all known layouts failed)" was the whole account, and the module cannot be attached to a report - it arrives encrypted under a key that is not kept. The log now carries the decompressed size, the header's own figure, the leading bytes, and per layout how far it got and which way out it took. A fourth layout and a search for a longer header come with it, both accepted only on an exact fill
 - **`framexml_run` could not be built on a Homebrew prefix.** It is built from wowee's own target properties, and three of the four were copied - libraries, includes, definitions - but not the link directories, which is where pkg-config puts the path for a bare library name
+- **Eight of the FrameXML sweeps read an interface that was not there and reported a clean tree.** `ROOT` was one contributor's absolute home directory, so each of them ran on exactly one machine - and `loaded_files` on a directory that does not exist returns an empty set, which is indistinguishable from a sweep that looked and found nothing wrong. Root is derived from the file's own location now, the way every other tool here does it, and the interface directory can be named on the command line so a sweep can be pointed at a particular expansion's. `framexml_live_stubs` was reading the defaults list out of the takeover source as well, which went with `WOWEE_FRAMEXML_UI`
 - **A macOS CI failure on Apple's developer agreement read as a broken build.** notarytool's output is captured and the 403 named, so an account problem is distinguishable from a build that does not compile. The policy is unchanged: a master build that cannot be notarized still fails
 
 ### Removed