Bring the wilm branch into main: endpoints plugin, agent, policies, CSV import

Ports the corporate-GitHub wilm branch onto main, keeping the two branches
separate. Thirteen upstream commits arrive with their authorship intact; the
review fixes and the portability work below are on top.

What arrives:

  endpoints plugin  - a ShopDB agent reporting endpoint state, telemetry,
                      services and interfaces, with a command channel the agent
                      long-polls. Ingest stays on the generic collector route
                      (ADR-006); the agent key is a UI-managed single-scope
                      token whose revocation is an instant kill switch.
  computers policies - Configuration and Business Policies (RMM-style), scope
                      trees validated at write time, actions checked against
                      the endpoints command allowlist. Feature-gated: every
                      route 404s while the setting is off, so enabling it can
                      never half-expose the surface.
  asset CSV import  - templates, a collector script carrying the site path, and
                      a validate-then-commit import. A plugin can own a virtual
                      column plus a post-write row hook, which is how a PC's
                      machine number becomes a controls link without a
                      hand-built relationships sheet.
  agent/            - the Windows agent and its installer.

Contract 0.21.0 -> 0.24.0, additive throughout: register_import_hook (0.22),
mint/list/revoke_service_token (0.23), collector_authorized (0.24). The stability
table had no rows for any of them and now does.

MySQL 5.6 portability. The branch stored three policy columns as sa.JSON, the
only JSON columns in the product, and 5.6 has no JSON type: the migration failed
with a bare syntax error near the word JSON. They are TEXT now, through a
JSONText type decorator, so all seventeen call sites still read and write dicts.
The convention elsewhere is already TEXT (guides.blocksjson,
geenforce.manifestjson).

Review fixes carried on top:

  - six policy GETs were jwt_required(optional=True), which authenticates a
    caller without checking anything; they require computers.view now, and six
    redundant jwt_required decorators are gone
  - the agent installer took a default BaseUrl and CollectorKey, so a mistyped
    run silently pointed an endpoint at the wrong instance; both are mandatory
    and a non-https BaseUrl throws unless -AllowInsecureHttp is passed
  - a committing CSV import wrote no audit row

Documentation: the 34 new routes are described in docs/api-inventory.json, which
is hand-maintained on purpose, and the generated spec now covers 331 paths and
477 operations across 22 surfaces. DEVELOPMENT-SETUP's 1071 troubleshooting row
said "use MySQL 8 for dev" and now gives the actual fix, including the trap that
5.6 downgrades ROW_FORMAT=DYNAMIC to Compact with a warning instead of an error.

Full suite 2123 passed, vitest 260 passed, all seventeen plugin chains migrate
clean on MySQL 5.6 and the naming, docs, parity and read-surface gates are green.

.env.example

@@ -4,7 +4,7 @@
 # refuses to boot when SECRET_KEY, JWT_SECRET_KEY, DATABASE_URL, or
 # CORS_ORIGINS are missing or use the dev defaults.
 #
-# See docs/DEPLOY.md for the full per-site deployment runbook.
+# See the DEPLOY wiki page for the full per-site deployment runbook.
 
 # ---- Flask ----
 FLASK_APP=wsgi.py
@@ -25,7 +25,7 @@ JWT_SECRET_KEY=change-this-to-another-secure-random-string
 # Format: mysql+pymysql://<user>:<password>@<host>:<port>/<database>?charset=utf8mb4
 # In docker-compose, host is `db` (the service name).
 # The ?charset=utf8mb4 keeps the connection on utf8mb4; create the database as
-# utf8mb4 too (see docs/DEPLOY.md). Both must be utf8mb4 to match the schema.
+# utf8mb4 too (see the DEPLOY wiki page). Both must be utf8mb4 to match the schema.
 DATABASE_URL=mysql+pymysql://shopdb:CHANGE_ME@db:3306/shopdb_flask?charset=utf8mb4
 
 # ---- CORS (required, no wildcards in production) ----
@@ -64,6 +64,7 @@ ZABBIX_TOKEN=
 # COLLECTOR_API_KEY_<PLUGINNAME> first, then COLLECTOR_API_KEY as fallback.
 # COLLECTOR_API_KEY=
 # COLLECTOR_API_KEY_COMPUTERS=
+# COLLECTOR_API_KEY_ENDPOINTS=
 
 # ---- Trusted plugin publisher keys (ADR-013, optional) ----
 # Public-key PEM paths (OS path separator: ':' on Linux, ';' on Windows) used
@@ -107,5 +108,5 @@ ZABBIX_TOKEN=
 # Serve the app under a URL prefix instead of the server root, e.g. as an IIS
 # Application at /ops under an existing site. The frontend must be rebuilt with
 # the matching base: VITE_BASE_PATH=/ops/ npm run build. Leave unset when the
-# app owns its own site/port (the default). See docs/INSTALL-WINDOWS-IIS.md.
+# app owns its own site/port (the default). See the INSTALL-WINDOWS-IIS wiki page.
 # MOUNT_PATH=/ops