docs: wiki staleness sweep (Fable-orchestrated Opus audit)

Audited all 40 docs/ against the live codebase; fixed factual staleness in 23,
14 were clean. Highlights (all verified against code):
- equipment -> machines (ADR-011 rename) in INSTALL/DEPLOY-WINDOWS-IIS,
  PLUGIN-GUIDE, GE-ENFORCE, ROADMAP.
- Versions refreshed: contract 0.10.0 -> 0.13.0, product 0.5.0 -> 0.7.0, plus
  plugin example core_version pins.
- Bundled set corrected to the current 13 (PLUGINS.md 7 -> 13 rows; DEPLOY
  eleven -> thirteen).
- Per-plugin Alembic chain workflow (ADR-008) replacing stale core-chain steps
  in PLUGIN-QUICKSTART / BACKUP-RESTORE; deploy adds plugin upgrade-all.
- Frontend plugin staging (ADR-010) replacing 'no frontend plugin system yet'
  in PLUGIN-GUIDE; view/route paths repointed to plugins/<name>/frontend/.
- Corrected file paths (MapView.vue, manifest_schema.json), CLI (shelf-list),
  API gating (GET /api/plugins is optional-jwt), WJF 15 -> 16 stages, and
  retired Collector/PC-Types settings pages (ADR-012).
- ge-enforce proposal marked ACCEPTED/built.

docs/BACKUP-RESTORE.md

@@ -96,18 +96,42 @@ CREATE DATABASE shopdb_flask CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
 tar xzf instance-2026-07-10.tar.gz    # restores ./instance/
 ```
 
-The docker-compose api container reads `instance/` from the repo working
-directory; make sure it is present before starting `api`.
+The default `docker-compose.yml` does NOT bind-mount `instance/` into the api
+container (its only volume is `- ./plugins:/app/plugins:ro`, and the image never
+copies `instance/`), so the container's Flask instance path is an empty
+`/app/instance` and a restored host `./instance` is invisible to it. To make the
+restored `instance/` visible, add a bind mount to the api service before starting
+it:
+
+```yaml
+  api:
+    volumes:
+      - ./plugins:/app/plugins:ro
+      - ./instance:/app/instance
+```
+
+Make sure `./instance` is present on the host before starting `api`.
 
 ### Step 4: Bring up the API and reconcile migrations
 
 ```bash
 docker compose up -d api
 docker compose exec api flask db upgrade
+docker compose exec api flask plugin upgrade-all
+```
+
+For a non-docker deploy:
+
+```bash
+flask db upgrade
+flask plugin upgrade-all
 ```
 
 `flask db upgrade` is a safety net: if the dump predates the current code, this
-applies any newer migrations. If the dump is at the same version it is a no-op.
+applies only the core Alembic chain. `flask plugin upgrade-all` then applies any
+newer per-plugin migrations (each bundled plugin owns its own chain, ADR-008);
+without it, plugin-owned tables stay un-migrated. If the dump is at the same
+version both are no-ops.
 
 ### Step 5: Verify