fix(installer): correct a false security claim, and clear the should-fix list

CLIENT IP / SPOOFABILITY. docs/geenforce-api-cutover.md claimed that removing the
IIS rewrite rule made the allowlist fail closed and that it does NOT become
spoofable. The opposite is true. IIS never sets X-Forwarded-For on its own; the
rule is the only thing that does. Remove it and IIS still forwards whatever
X-Forwarded-For the CALLER sent, waitress trusts it because it arrives from
127.0.0.1, and remote_addr becomes attacker-controlled - so a token-less caller
can fetch manifests from anywhere on the network. The document and the
_trusted_client_ip docstring now say so, waitress runs with
--trusted-proxy-count=1, and stage 5 checks the rule is actually live rather than
assuming it. The wizard question is rephrased to something an operator can verify
with their network team instead of guessing at.

NON-ASCII. The style gate only ever checked .py/.vue/.js/.ts, so documentation
accumulated em-dashes, arrows and box-drawing characters against this repo's own
convention - including in files added this week. Cleaned, and the gate now uses
INCLUDES_ALL so Markdown, JSON and YAML are covered.

PLUGIN DEFAULTS. The wizard pre-ticked measuringtools and printedparts, both of
which ship default_enabled=false, so every site taking the defaults installed and
enabled them against their manifests. Inno has no JSON parser so the list must be
hardcoded, but tests/test_installer_defaults.py now fails when it drifts.

UPGRADES. The payload copy merges, so a plugin dropped from a site's profile kept
its code forever - which defeats a lean build and leaves core's optional-import
guards succeeding for a plugin the site no longer has. Stale plugin directories
are now deregistered and removed before the copy.

add-plugin used 'plugin install', which for the five default_enabled=false
plugins left them installed but DISABLED - and printed a green success line
anyway. It now goes through apply-profile, and the success line is gated on the
exit code. Invoke-Flask records its own exit status, because $LASTEXITCODE keeps
a stale value when flask.exe is missing and no native command runs.

CHARSET. The utf8mb4 compiler hook lived inline in migrations/env.py, so it
covered the CORE chain only: plugin baselines inherited the server default, which
on a latin1 server means two charsets in one database. It is now
shopdb/utils/mysql_charset.py, imported by both, and preflight reports the
database's default charset.

BACKUP HONESTY. The dump was described as 'all of your asset data'. Uploaded
branding and floor-map images live in instance\ on disk, not in the database, so
a restore from the .sql alone comes back with no map. backup now archives
instance\ alongside it and says both are needed.

VERSIONING. AppVersion was hardcoded at 0.9.0 while the product, the frontend and
the newest tag said 0.7.0 - and 0.9.0 collides with a retired contract version.
Both builders now generate version.iss from shopdb/__init__.py.

Smaller: rollback overwrites .env before deleting it, as uninstall already did;
appcmd unlocks are scoped to this site's location rather than server-wide, with
the wide unlock as a fallback; DEVELOPMENT-SETUP says Python 3.14; the README
plugin list gains printedparts; prune-schema --force is documented as
first-provisioning-only; HTTPS is documented as not-the-default with the steps to
add it; the DBA SQL is on the wizard's database page; the features page says
unticking does not remove an installed feature; and the installer README states
that bundle-lock cannot vouch for the exe itself - that needs signing or an
out-of-band hash, neither of which is wired up.

CHANGELOG.md

@@ -12,6 +12,54 @@ ADR-007 and ADR-002.
 
 ### Added
 
+- Air-gapped Windows installer (`deploy/windows/installer/`). One `.exe` per
+  site, built from that site's plugin profile, containing Python, the wheels,
+  the SPA, the IIS modules and optionally MySQL. Operator docs:
+  `docs/INSTALL-WINDOWS.md` and `docs/OPERATE-WINDOWS.md`, both shipped onto the
+  server. `docs/INSTALL-WINDOWS-IIS.md` and `docs/DEPLOY-WINDOWS-IIS.md` are now
+  reference-only, for hand-built servers.
+- `bundle-lock.json`: an exact sha256 + size record of the installer's
+  third-party payload (wheels, Python installer, IIS MSIs). Verified as set
+  equality by both builders and again on the server before anything runs; there
+  is no install-time override. Regenerate with `refresh-bundle-lock.ps1`.
+- CycloneDX SBOM (`sbom.cdx.json`) generated on every build from
+  `requirements.txt` and `package-lock.json`, covering both ecosystems, staged
+  into the application tree so an air-gapped server can answer "do we carry this
+  component" locally: `shopdb-admin.ps1 verify -Path <name>`.
+- `shopdb-admin.ps1`, the operator console: status, start/stop/restart, logs,
+  health check, backup, plugins, verify. `check -Json` emits secret-free
+  structured state for pasting into a support ticket or an AI assistant.
+- `build-installer.ps1`, the whole build natively on Windows, so a work PC needs
+  no Bash. Shares `scripts/resolve_plugin_closure.py` with `build-site.sh`.
+- URL Rewrite is bundled and the wizard asks where client IPs come from
+  (`-ClientIpSource direct|proxy`). Without the rule IIS sends no
+  `X-Forwarded-For` at all and every client reads as 127.0.0.1.
+
+### Changed
+
+- `requirements.txt` and `requirements-dev.txt` are compiled `--universal
+  --generate-hashes`. Installs run under `pip --require-hashes`, so a wheel whose
+  sha256 is not listed is refused. The dev lockfile is constrained to the
+  production pins; the two had drifted.
+- Python 3.14 across the Dockerfile, CI, `web.config` and the docs, which
+  previously declared four different versions.
+- The naming/style gate covers Markdown, JSON and YAML, not just code.
+
+### Fixed
+
+- `plugins/employees` imported `shopdb.core.models` directly, failing the
+  contract-surface test on `main` since the dashboard employee-name resolver
+  landed.
+- `scripts/build-site.sh` copied all of `deploy/` into its own output directory,
+  which recursed when the output was staged inside it - the documented Windows
+  build could not complete.
+- Plugin baseline migrations inherited the MySQL server's default charset: the
+  utf8mb4 compiler hook lived in `migrations/env.py` and so covered the core
+  chain only. It is now `shopdb/utils/mysql_charset.py`, imported by both.
+  `flask db-utils preflight` reports the database's default charset.
+
+### Added
+
 - Configurable site timezone: a `site_timezone` site setting (default
   `America/New_York`, public-readable), editable in Settings > Site >
   Localization. Notification start/end times are entered and displayed in this
@@ -53,7 +101,7 @@ ADR-007 and ADR-002.
 - Shopfloor kiosk header text is readable (light on the dark navy header).
 
 
-### Added
+### Added (continued)
 
 - Collector-driven PC -> printer relationships. The computers collector schema
   gained optional `defaultprinter` (string) and `printers` (array of strings)