Website: machine estimator v2 — fold-out categories and the memory bar (still unlisted, R-997)

Each category is a native <details>, closed at first, with an 'n selected' count;
a preset opens what it ticks. A sticky memory bar (0-64 GB, marks 8/16/24/32/48/64+):
solid fill = smallest box memory where the selection fits well, thin mark = where it
fits, but tight; one line names the box to buy. minBoxGb() inverts guestMib() by
bisection on it, so the rule is still written once. Box sizes 12/24/48/64 added;
tests cover seven sizes and the inverse (red-proofed); SIZING.md table gains 24 GB.

scripts/CHANGELOG.md

@@ -1,3 +1,12 @@
+## 2026-10-13 (afternoon) — estimator v2: `build_sizing_web.py` box sizes, tests for the inverse
+
+- `build_sizing_web.py`: `boxes_gb` = 8, 12, 16, 24, 32, 48, 64; new `bar_marks_gb` and `bar_max_gb`.
+- `test_build_sizing_web.py` (8 tests): the four cases × seven sizes, with the recommended („fits well”) and the
+  smallest „tight” size each; the inverse agrees with the forward rule (the guest at the answer holds the need, one
+  step smaller does not); SIZING.md's table is read by its header and must carry the 24 GB column; `sizing.js` may
+  hold only 0, 1, 2, 100 and 1024. Red-proofed: a wrong 24 GB cell, a missing 24 GB column, a hard-coded 64 in the
+  JS, and an inverse 1 GB too big each convicted.
+
 ## 2026-10-13 — `build_sizing_web.py` + `site_gates.py` UNLISTED pairs and gate 25
 
 - **`build_sizing_web.py`** builds `website/assets/sizing-data.json` (the machine estimator's data) from