docs: how another site points these tools at its own ShopDB

The asset reporter and EventSaver are both already built to be repointed - the
server URL, the API key and the targeting are parameters, an ini file and
manifest targeting, not code. Nothing said so, so the question "can another shop
use this" had no answer that did not involve reading PowerShell.

Worked examples for all three deployment paths, because sites have different
management planes and the choice is not ours to make: Intune (a remediation for
the reporter, a Win32 app for the screensaver, plus a Machine Configuration/DSC
form for estates already governed that way), a GE-Enforce manifest entry, and
manual installation for a pilot or a single bay.

The two traps are written down rather than left to be discovered. EventSaver
falls back to a path compiled into the binary when its ini is missing, and that
path belongs to the reference site - a missing ini is not a neutral default. And
a config enforced by hash reverts a hand edit on the next cycle, which is the
feature working correctly and reads exactly like a bug.

Also notes the reporter's -ApiUrl default still points at the reference site, so
every example passes it explicitly until that is fixed.

CHANGELOG.md

@@ -83,6 +83,14 @@ ADR-007 and ADR-002.
   returning nothing and leaving the caller to guess.
 - The display client module updates itself through the manifest, so a client
   change no longer means hands on every kiosk.
+- `docs/ADOPTING-AT-ANOTHER-SITE.md`: how another site repoints the asset
+  reporter and the EventSaver screensaver at its own ShopDB, with worked
+  examples for Intune (including Machine Configuration/DSC), a GE-Enforce
+  manifest entry, and manual installation. Both tools were already built to be
+  repointed - the URL, the key and the targeting are inputs - but nothing said
+  so, and the two things that catch people out are written down: EventSaver's
+  compiled-in fallback path is not neutral, and a config enforced by hash
+  reverts a hand edit by design.
 - `docs/PROJECT-MAP.md`, generated by `scripts/gen_project_map.py`: versions,
   the plugin inventory, every Alembic chain head, the ADR index and the size of
   the codebase, derived from the code. The hand-written equivalents in CLAUDE.md