docs: wiki update for API docs, printer installer, geenforce cutover, timezone

Execute WIKI-UPDATE-PLAN.md (14 items):
- NEW docs/PRINTER-INSTALLER.md: install-list / pc-default / install-batch
  contract + public installer map page.
- NEW-shape docs/API-REFERENCE.md: index + pointer to the live generated docs
  (/api/docs Redoc, openapi.json, llms.txt, MCP), replacing a stale full dump.
- geenforce cutover + GE-ENFORCE-DISPLAY/CLIENT/DEPLOY: server-first display
  dispatcher (display-role by FQDN, display-type.txt fallback), dashboarddefaults
  FQDN keying, legacy kiosk autostart self-heal (Wow6432Node), per-PC-type
  cutover status.
- PLUGINS: printers/slides rows + plugin-permissions note (slides.manage).
- IMPORT-API: dashboarddefaults FQDN-first keying.
- CONFIG: word-wise search, site_timezone setting.
- PILOT-DEPLOY: servers-to-network reclassify step. IMPORT-ADOPTION: fixup note.
- CLAUDE.md: test count 1077->1159, HTTPS-cutover state. CHANGELOG: timezone +
  kiosk-autostart fixes, site_timezone setting.

docs/PILOT-DEPLOY.md

@@ -80,12 +80,28 @@ import API. It is site glue, not product code.
    printers -> dependents -> relationships -> subnets -> usb -> verify). It is
    idempotent - a crashed run resumes from `idmap.json`.
 
+3. Reclassify servers into network devices. The classic DB stored servers as
+   PCs, so the import lands them as `computer` assets. Re-point them in place:
+
+   ```
+   DATABASE_URL=... venv/bin/python scripts/reclassify_servers_to_network.py            # dry run, prints matches
+   DATABASE_URL=... venv/bin/python scripts/reclassify_servers_to_network.py --commit   # apply
+   # match on an exact computer type instead of the SVR- name prefix:
+   ... --type "Server" --commit
+   ```
+
+   The assetid does not change: communications, relationships, map position, and
+   audit history carry over. Only the extension row is swapped (computers ->
+   networkdevices) and the asset type flipped; reclassified devices get the
+   `Server` networkdevicetype. Run the dry run, eyeball the list, then commit.
+   Re-running is safe (already-moved assets no longer match).
+
 Expected magnitude (from the WJ dumps used in development - your fresh dumps will
 differ slightly):
 
 | entity | count |
 |---|---|
-| assets | ~983 (computer ~663, machine ~76, network ~58, measuring-tool ~136, printer ~50) |
+| assets [*] | ~983 (computer ~663, machine ~76, network ~58, measuring-tool ~136, printer ~50) |
 | locations | ~24 |
 | employees | ~415 |
 | installs | ~850 |
@@ -97,6 +113,16 @@ differ slightly):
 | subnets | ~37 |
 | USB devices / events | ~18 / ~232 |
 
+[*] Counts taken AFTER `scripts/reclassify_servers_to_network.py --commit`.
+Servers imported as computers are re-pointed to network devices, so the computer
+count drops and network rises by the same amount versus a raw import.
+
+> PLACEHOLDER - re-measure before publishing. The computer/network split shown
+> in the assets row above still reflects a RAW import (pre-reclassify). Re-run
+> the counts on the current prodscratch AFTER the reclassify step above and drop
+> in the actual numbers; do not carry these development figures forward as if
+> they already account for the reclassify.
+
 The `verify` stage prints a source-vs-target row-count audit; the gaps are the
 documented skips (inactive rows, duplicate machinenumbers, LocationOnly, the
 9999 placeholder).