Website: the machine estimator (/gepigeny, /en/sizing), live but unlisted; SIZING.md §5 in three verdicts; R-997 filed

A household ticks apps and sees, for an 8, 16 and 32 GB box: fits well / fits, but
tight / does not fit, the totals, and the apps that burst on CPU. One rule in
assets/sizing.js, every number from assets/sizing-data.json (built by
scripts/build_sizing_web.py from the 2026-10-13 N100 measurement; test: 7 cases,
red-proofed). Unlisted: noindex, robots Disallow, not in the sitemap, linked from
nowhere — site_gates.py gate 25 enforces it (UNLISTED twin pairs keep every twin
check). SIZING.md §5 corrected: the 8 GB line contradicted its own x1.5 rule; guest
sizes 4.0/11.4/27.4 GB with the measured 612 MiB MemTotal shortfall. R-993 gains the
fact that the installer accepts a host below any minimum.

documentation/audits/sizing-2026-10-13/SIZING.md

@@ -159,8 +159,23 @@ and the page cache is what makes a photo library feel fast.
 **Disk, why:** the installer gives the guest a 32 GB system volume and, from the free space, a 70 / 130 / 250 GB data
 volume; the host keeps three daily guest dumps (19 GB on this box). Image sizes per app were **not measured** in this run.
 
-**What each size runs** (the installer gives the guest: 8 GB → 4 GB, 16 GB → ≈ 11.6 GB, 32 GB → ≈ 27.6 GB):
-- **8 GB:** the household set **without Immich** (peaks 2.0 GB + platform) with room to spare; Immich only on its own or with
-  one or two light apps (its import alone peaks at 3.1 GB of the guest's 4 GB). The floor of the offer.
-- **16 GB:** the whole household set at peak (≈ 5.5 GB) twice over, plus a dozen light apps. The recommended box.
-- **32 GB:** the household set plus most of the catalog: all 62 installable apps typical together ≈ 13.3 GB, at peak ≈ 21.3 GB.
+**What each size runs — three verdicts, the same rule as the estimator page** (`/gepigeny`, `website/assets/sizing.js`).
+*Corrected 2026-10-13:* the lines here first said an 8 GB box runs Immich „on its own” while this section sizes a box at
+peak × 1.5 — which Immich alone does not meet on 8 GB ((470 + 3,061) × 1.5 ≈ 5.2 GB > 4 GB), though its peak fits
+(3.4 GB). Three verdicts say both honestly. The guest is the installer's rule on MemTotal = label − 612 MiB (the
+16 GB N100 reports 15,772 MiB): **8 GB → 4.0 GB, 16 GB → 11.4 GB, 32 GB → 27.4 GB** (the first version said 11.6 / 27.6).
+**Fits well:** peak × 1.5 ≤ guest · **fits, but tight:** peak ≤ guest < peak × 1.5 — works, but a large photo import or
+a backup at the same time can slow it down · **does not fit:** guest < peak. Peak = 470 MB platform + the apps' peaks summed.
+
+<!-- sizing-verdicts: generated from the rule; scripts/test_build_sizing_web.py checks this table -->
+| Selection | Peak | 8 GB | 16 GB | 32 GB |
+|---|---|---|---|---|
+| Household set | 5.4 GB | does not fit | fits well | fits well |
+| Household set without Immich | 2.4 GB | fits well | fits well | fits well |
+| Immich alone | 3.4 GB | fits, but tight | fits well | fits well |
+| All 62 apps | 21.3 GB | does not fit | does not fit | fits, but tight |
+<!-- /sizing-verdicts -->
+
+- **8 GB:** the household set without Immich fits well; Immich alone fits, but tight; the whole household set does not fit.
+- **16 GB:** the whole household set fits well.
+- **32 GB:** the household set fits well; all 62 apps at once fit, but tight.