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.

docs/OPERATE-WINDOWS.md

@@ -11,7 +11,7 @@ C:\shopdb-flask\shopdb-admin.ps1
 
 The Start Menu folder **ShopDB-Flask** has shortcuts for the common tasks. Run it
 with no arguments for a menu, or pass a command directly. It needs
-Administrator — it will ask, except for `open`.
+Administrator - it will ask, except for `open`.
 
 ---
 
@@ -20,11 +20,11 @@ Administrator — it will ask, except for `open`.
 | Command | What it does | Safe at any time |
 |---|---|---|
 | `status` | Is it published, running, responding; database and table count | yes |
-| `restart` | Recycles the application pool. **Use this after any config change.** | yes — drains requests rather than cutting them off |
+| `restart` | Recycles the application pool. **Use this after any config change.** | yes - drains requests rather than cutting them off |
 | `stop` / `start` | Takes the site down / brings it back | yes, but `stop` makes it unavailable |
 | `logs` | Last lines of the application and install logs | yes |
 | `check` | Full health check | yes |
-| `check -Json` | The same, machine-readable — see [Getting help](#getting-help) | yes |
+| `check -Json` | The same, machine-readable - see [Getting help](#getting-help) | yes |
 | `verify` | Which build this is, and whether what is installed still matches it | yes |
 | `sessions` | IIS worker processes and memory | yes |
 | `plugins` | Which features are installed, which are available | yes |
@@ -50,7 +50,7 @@ Examples:
 ```
 
 Writes to `C:\ProgramData\ShopDB-Flask\backups` unless you pass a directory. The
-dump is **verified complete** before it is reported as good — a truncated backup
+dump is **verified complete** before it is reported as good - a truncated backup
 is deleted rather than left to be discovered later.
 
 Two things to know:
@@ -85,7 +85,7 @@ go backwards, and restores if a migration fails. See
 
 Only features **shipped in this build** can be added. Each site's installer is
 built for that site's chosen feature set, so a feature nobody asked for is not on
-the server at all — adding it means a new installer built from an updated
+the server at all - adding it means a new installer built from an updated
 profile. `plugins` shows you which is which.
 
 ---
@@ -119,7 +119,7 @@ immediately if it is not:
 .\shopdb-admin.ps1 restart
 ```
 
-**4. Check the database is reachable** — `status` reports the host and whether it
+**4. Check the database is reachable** - `status` reports the host and whether it
 could count tables. A site that starts but shows no data is usually a database
 problem, not an application one.
 
@@ -129,7 +129,7 @@ problem, not an application one.
 .\shopdb-admin.ps1 verify
 ```
 
-This flags packages that no longer match what shipped — which usually means
+This flags packages that no longer match what shipped - which usually means
 somebody ran a `pip install` on the server by hand.
 
 ---
@@ -147,13 +147,13 @@ whether it responds, database host and reachability, Python version, installed
 features, and any errors. **It contains no passwords** and is safe to paste into
 a chat window or a ticket.
 
-The install log is also safe to share — secrets are deliberately kept out of it.
+The install log is also safe to share - secrets are deliberately kept out of it.
 
 Offline reference on the server itself:
 
-- `/api/docs` on the site — the full API reference, self-hosted, no internet.
-- `C:\shopdb-flask\docs\` — these runbooks.
-- `C:\shopdb-flask\sbom.cdx.json` — every component this build contains.
+- `/api/docs` on the site - the full API reference, self-hosted, no internet.
+- `C:\shopdb-flask\docs\` - these runbooks.
+- `C:\shopdb-flask\sbom.cdx.json` - every component this build contains.
 
 ---
 
@@ -178,12 +178,50 @@ Nothing found means this server does not carry it.
 
 ---
 
+## Adding HTTPS
+
+**The installer publishes over HTTP.** It has no certificate to use and no way to
+get one on an air-gapped server, so it does not pretend otherwise. On an internal
+network behind the site firewall that is often accepted; confirm it against your
+own policy rather than assuming.
+
+If you installed **under an existing site** (the subpath option) and that site
+already has a certificate, you are already on HTTPS - nothing to do.
+
+For a site of its own, once you have a certificate in the machine store:
+
+```powershell
+Import-Module WebAdministration
+
+# 1. Add the binding. Get the thumbprint from the certificate you imported.
+New-WebBinding -Name shopdb-flask -Protocol https -Port 443
+$cert = Get-ChildItem Cert:\LocalMachine\My | Where-Object { $_.Subject -like '*yourserver*' }
+Get-Item "IIS:\SslBindings\0.0.0.0!443" -EA SilentlyContinue | Remove-Item -EA SilentlyContinue
+New-Item "IIS:\SslBindings\0.0.0.0!443" -Value $cert
+
+# 2. Open the port.
+New-NetFirewallRule -DisplayName "shopdb-flask 443" -Direction Inbound `
+    -Protocol TCP -LocalPort 443 -Action Allow
+```
+
+Then **update `CORS_ORIGINS` in `C:\shopdb-flask\.env`** to the `https://` address
+and restart:
+
+```powershell
+.\shopdb-admin.ps1 restart
+```
+
+That last step is not optional. `CORS_ORIGINS` is an exact origin match, so a
+site reached over `https://` while `.env` still says `http://` loads the page and
+then fails every data request - which looks like the application is broken rather
+than a configuration mismatch.
+
 ## Where things live
 
 | | |
 |---|---|
 | Application | `C:\shopdb-flask` |
-| Configuration and secrets | `C:\shopdb-flask\.env` (locked down — do not loosen) |
+| Configuration and secrets | `C:\shopdb-flask\.env` (locked down - do not loosen) |
 | Application logs | `C:\shopdb-flask\logs` |
 | Install logs | `C:\ProgramData\ShopDB-Flask\logs` |
 | Backups | `C:\ProgramData\ShopDB-Flask\backups` |