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/IMPORT-ADOPTION.md

@@ -25,6 +25,11 @@ implementation #1. Read it alongside this guide.
 - `run.py` - ordered `stage_*` functions. Each reads a slice of the source,
   POSTs it, and records the crosswalk later stages resolve foreign keys against.
 
+Post-import fixups that re-point existing assets (example:
+`scripts/reclassify_servers_to_network.py`, servers imported as PCs moved to
+network devices in place) belong in the site loader's verify stage, not in the
+stable API layer.
+
 ### Stage order matters
 
 Reference/lookup tables first (so foreign keys resolve), then the entity hub,