docs: stop publishing internal references to a public wiki

docs/ is excluded from the code bundle and its scrub gate, because it goes to
the GitHub wiki instead - via a generator that has no gate at all. So the one
part of the repository written in prose, by people, about internal
infrastructure, was the one part nothing checked.

What was reaching a public wiki: the internal git server's URL and hostname,
.gitea workflow paths, developer home directories in the GE-Enforce cutover
reference, and a dev database root password inside a copy-pasteable command in
the import guide.

All replaced with neutral equivalents. tests/test_docs_publishable.py is now the
gate, at the source, in CI - a wiki page cannot be un-published, so catching this
after the fact is not good enough.

PROJECT-REVIEW.md also referred to internal tooling by name throughout; those
references are generalised. It remains an internal candid assessment of this
project that is nonetheless published, which is worth a separate decision.

docs/geenforce-api-cutover.md

@@ -15,7 +15,7 @@ the CUTOVER):
 - `docs/GE-ENFORCE-CLIENT.md` - client fetch/report contract
 - `docs/GE-ENFORCE-DEPLOY.md` - what must land on a PC
 - `docs/GE-ENFORCE-DISPLAY.md` - the display scope specifics
-- `/home/camp/projects/pxe/docs/ge-enforce-v2-architecture.md` - the SMB world
+- the PXE repo (`docs/ge-enforce-v2-architecture.md`) - the SMB world
   being cut away from
 
 Contents:
@@ -410,7 +410,7 @@ A share-less PC cannot pull its first files from the share, so the bootstrap
 itself is downloadable from the web app.
 
 `Install-ShopdbKiosk.ps1` (source of truth:
-`/home/camp/pxe-images/shopdb-migration/kiosk-installer/`) is hosted at
+the imaging share (`shopdb-migration/kiosk-installer/`)) is hosted at
 `C:\inetpub\wwwroot\shopdb\installers\kiosk\` and downloadable at
 `{BaseUrl}/installers/kiosk/Install-ShopdbKiosk.ps1`. Run elevated on the PC:
 
@@ -586,7 +586,7 @@ The VM rig:
 
 - The win11 virt-manager VM (see `project-win11-vm` /
   `reference-vm-qga-as-system` memory), driven by
-  `/home/camp/pxe-images/ednc-bins/qga-run.py` - qemu guest agent
+  the imaging share (`ednc-bins/qga-run.py`) - qemu guest agent
   `guest-exec`, which runs PowerShell AS SYSTEM. That matters: the scheduled
   tasks run as SYSTEM, so testing as SYSTEM reproduced the session-0 and
   profile-less behaviors an interactive test would have masked.
@@ -612,7 +612,7 @@ git pipeline.
 
 Prod is air-gapped from dev; code moves via a git bundle on the share
 (`\\172.16.9.9\pxe-images\github\shopdb-flask-pub.bundle`) and the .cmd
-scripts in `/home/camp/pxe-images/github/`, run on the work PC:
+scripts in the imaging share (`github/`), run on the work PC:
 
 1. `pull-shopdb-bundle.cmd` - fetch the bundle into the local clone
    (ff-only).
@@ -634,7 +634,7 @@ the bundle pipeline or prod drifts from git.)
 
 ### Channel 2: client + engine + collector + bootstrap (the kiosk bundle)
 
-These live at `/home/camp/pxe-images/shopdb-migration/kiosk-installer/` and
+These live at the imaging share (`shopdb-migration/kiosk-installer/`) and
 deploy by robocopy from the work PC (Z: = share, Y: = prod app dir):
 
 ```
@@ -647,7 +647,7 @@ That directory (bundle contents: `Install-ShopdbKiosk.ps1`,
 the MIME maps) IS the distribution point - PCs download from
 `{BaseUrl}/installers/kiosk/`. Reference copies of the client kit also live in
 the repo at `plugins/geenforce/client/` and the engine's source of truth is
-`/home/camp/pxe-images/common/lib/Install-FromManifest.ps1`; when the engine
+`the imaging share, common/lib/Install-FromManifest.ps1`; when the engine
 or client changes, update the kiosk bundle copy too (nothing syncs it
 automatically). PCs pick up new bytes by re-running the bootstrap one-liner.