5 Commits

Include renames

Author	SHA1	Message	Date
admin	cb2d3a54ae	Website: „Milyen gép kell?" becomes a main menu item; no „tight from" below 8 GB ... The estimator leaves the Apps group and sits right after it, with the sprite's chip icon, on every page of both languages. The legend's tight-from item and the thin marker hide when that size is below the smallest named box (it read 2,1 GB on an empty selection); test pinned, red-proved. sizing.js?v=5.	2026-10-13 20:42:32 +02:00
admin	fc0441348d	Website: machine estimator v3.1 — bar never below an 8 GB box; a single leftover app keeps its name (R-997) ... Empty or tiny selections drew a ~2.3 GB box whose base system (1,636 MB) no real box has; the bar is now floored at the smallest named size (8 GB) for its parts only — the recommendation and the rule are unchanged. Grouping applies only to two or more leftover apps; a ninth app is shown by name in the group's colour. Tests: 12, the new ones red-proofed.	2026-10-13 16:31:56 +02:00
admin	92e9d45cf5	Website: machine estimator v3 — the bar shows what the box's memory is used for (still unlisted, R-997) ... The bar keeps its length (the fits-well box memory) and is split into base system (box - guest), Felhom's own services, each app's peak (largest first, the dashboard's palette minus amber and its first blue; beyond 8 apps one group) and spare room (guest - peak) — all from the one rule; a test proves the parts sum to the bar within 1 MB. A legend under it (not sticky) and one sentence explain the recommended size. Typical figure moved into the method fold-out. English: 'an 8 GB machine'.	2026-10-13 16:08:00 +02:00
admin	16dca64834	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.	2026-10-13 15:38:45 +02:00
admin	d5ef93b13b	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.	2026-10-13 14:31:44 +02:00