ADR-015: stop shipping one site's values, and make the rule a gate

The scanner has been reporting the same count for weeks, which is what a rule
that only prints becomes. It now FAILS the build, and it looks where the leaks
actually were: PowerShell, the installer, the seeds, generated JSON, the
frontend - case-insensitively, across plugins, shopdb, scripts, deploy, tools.
A line that is deliberate declares itself with an ADR-015-OK marker and a
reason, so the claim is visible in review instead of tolerated in silence.

What it found, fixed here:

- The shadow client wrote one site's ShopDB URL into HKLM whenever the registry
  disagreed. At the site it was written for that reads as healing drift;
  anywhere else it overwrites the site's own address on every enforce cycle,
  and the site cannot win because the cycle repeats. The bay's value now wins,
  an explicit -BaseUrl seeds it, and with neither there is nothing honest to
  write, so it says so and skips.
- The kiosk dispatcher fell back to one plant's host when HKLM was unset, so a
  kiosk elsewhere quietly opened a server it has no business reaching. The
  fallback is now this site's site_base_url, baked in at seed time, and the
  dispatcher refuses rather than guessing when neither is set. Its legacy
  shortcut matcher derives the host from that URL instead of naming one.
- The OpenAPI generator hardcoded a production hostname into every spec it
  generated, which then published to a public wiki. The relative mount is the
  only server it can honestly name; a site passes its own by environment.
- Placeholders and examples in the UI and the client help offered real internal
  subnets and a real production URL. They now use documentation ranges.

Both publication gates - the export scrub and the docs publishability test -
carry the site patterns, which neither did. One plant's hostname, FQDN and
internal networks are out of the documentation and the generated specs.

Comments naming the reference site are reworded rather than deleted: the
reasoning is worth keeping, the plant name is not what makes it true.

docs/adr/ADR-015-site-specific-configuration.md

@@ -17,9 +17,12 @@ That is not a hypothetical drift. A scan of `plugins/` and `shopdb/` for a site
 host, a site FQDN or a site network returns 19 hits, of which roughly 8 are a
 shipped default or a hardcode rather than a comment:
 
-- `plugins/geenforce/seed_display_scope.py` bakes `https://tsgwp00525.wjs.
-  geaerospace.net/shopdb` and `device.geaerospace.net` into an inline PowerShell
-  payload. A sister site cannot override either without editing the source.
+- `plugins/geenforce/seed_display_scope.py` baked one site's own ShopDB URL and
+  `device.geaerospace.net` into an inline PowerShell payload. A sister site
+  could not override either without editing the source. FIXED 2026-08-14: the
+  kiosk base URL now comes from the `site_base_url` setting at seed time and
+  from HKLM at run time, and the dispatcher refuses rather than guessing when
+  neither is set.
 - `plugins/backups/services/registry.py` defaults the backup share root to a WJ
   UNC path.
 - `shopdb/core/api/settings.py` ships `device.geaerospace.net` and