diff --git a/STATUS.md b/STATUS.md
index 5f0fe313..3a1e7369 100644
--- a/STATUS.md
+++ b/STATUS.md
@@ -2,11 +2,11 @@
**Ready for the first real tester (Tester-2): yes. Tester 2 (a laptop) is off; nothing was sent to it.**
-**Updated 2026-10-12 (evening): demo-hp, demo-felhom and Tester 1 run agent 0.154.0 and controller 0.309.0. The open-items list is at 125 (2026-10-13; the newest row is the machine estimator to try, R-997). Reports: `REPORT-usenet-2026-10-12.md`, `REPORT-newapps-2026-10-12.md`, `REPORT-disk-evening-2026-10-12.md`, `REPORT-answers-2026-10-12.md`, `REPORT-m3-2026-10-11.md`, `REPORT-redesign-2026-10-10.md`, `REPORT-testers-2026-10-10.md`, `REPORT-register-shrink-2026-10-10.md`, `REPORT-new-apps-2026-10-10.md`, `REPORT-release-2026-10-10.md`, `REPORT-break-the-circle-2026-10-09.md`, `REPORT-dooplex-survival-2026-10-09.md`, `REPORT-day4-2026-10-09.md`.**
+**Updated 2026-10-12 (evening): demo-hp, demo-felhom and Tester 1 run agent 0.154.0 and controller 0.309.0. The open-items list is at 126 (2026-10-13; the machine estimator was listed and its row R-997 closed). Reports: `REPORT-usenet-2026-10-12.md`, `REPORT-newapps-2026-10-12.md`, `REPORT-disk-evening-2026-10-12.md`, `REPORT-answers-2026-10-12.md`, `REPORT-m3-2026-10-11.md`, `REPORT-redesign-2026-10-10.md`, `REPORT-testers-2026-10-10.md`, `REPORT-register-shrink-2026-10-10.md`, `REPORT-new-apps-2026-10-10.md`, `REPORT-release-2026-10-10.md`, `REPORT-break-the-circle-2026-10-09.md`, `REPORT-dooplex-survival-2026-10-09.md`, `REPORT-day4-2026-10-09.md`.**
-## Tuesday 2026-10-13 (afternoon): the machine estimator is built — live, but unlisted
+## Tuesday 2026-10-13 (night): the machine estimator is public
-- **Waiting on you — decide:** try https://felhom.eu/gepigeny (English: https://felhom.eu/en/sizing), tick a few apps, and say „list it” or what to change (R-997). If you do nothing: the page stays unlisted and nobody finds it.
+- **Done:** https://felhom.eu/gepigeny (English: https://felhom.eu/en/sizing) is in the menu, the site map, the FAQ and the apps page; search engines may show it (R-997 closed). It still names no minimum machine — that waits on you (R-993).
## Tuesday 2026-10-13: what a Felhom box needs — measured
diff --git a/documentation/backlog/CLOSED-ITEMS.md b/documentation/backlog/CLOSED-ITEMS.md
index 24770444..267a85a7 100644
--- a/documentation/backlog/CLOSED-ITEMS.md
+++ b/documentation/backlog/CLOSED-ITEMS.md
@@ -26,6 +26,12 @@
---
+## 2026-10-13 (night) — the machine estimator is listed
+
+| Row | What | Closed | Evidence |
+|---|---|---|---|
+| **R-997** | **Operator: try the machine estimator at https://felhom.eu/gepigeny (English: /en/sizing) and say „list it” or what to change.** (P3) | CLOSED 2026-10-13 — **listed** on the operator's word after the reviewer's v3.1 browser check (Playwright, 19:20: console clean; empty selection = the 8 GB split 4096/470/3626 MB; 9 apps all named, 10 apps 8 named + „további 2 alkalmazás”). The pair moved from `UNLISTED` to `TWINS` in `site_gates.py` (gate 25 stays, with an empty list); noindex and the two robots.txt Disallow lines removed; both URLs in sitemap.xml with their hreflang pair; „Milyen gép kell?” / „Which machine do I need?” in every page's Alkalmazások / Apps menu group; one sentence + link at the end of the FAQ answer „Milyen gépre van szükségem?” (and its twin, JSON-LD equal); one line under the apps page intro. The explaining sentence's base figure was already the base of the box the bar draws (4.0 GB on an 8 GB bar, 4.6 GB for the household preset) — now pinned by `test_sentence_base_is_the_drawn_box_base` (red-proved). Built v1 d5ef93b1, v2 16dca648, v3 92e9d45c, v3.1 fc044134; listed in the commit that moved this row. **Reasoning kept:** the page names no minimum machine — that stays R-993. | `website/gepigeny.html`, `website/en/sizing.html`, `scripts/test_build_sizing_web.py`, `documentation/audits/sizing-2026-10-13/` |
+
## 2026-10-12 (evening) — security review: the two hub exposures
Found by the security review of 2026-10-12 (`documentation/audits/security-review-2026-10-12/`). Both rows were born
diff --git a/documentation/backlog/OPEN-ITEMS.md b/documentation/backlog/OPEN-ITEMS.md
index 7002f94e..5a8d46e3 100644
--- a/documentation/backlog/OPEN-ITEMS.md
+++ b/documentation/backlog/OPEN-ITEMS.md
@@ -121,7 +121,6 @@ stopping line that lies.
| **R-516** | Install & onboarding | P3 | **[P3-LOW] English a customer meets on a fresh box and its apps' first screens — enumerated by the big night.** MEASURED 2026-09-14 (BIGNIGHT, VM 333, ISO 1.27.1, controller 0.242.0). Felhom-owned: (1) the dashboard menu item **„Debug"**; (2) the dashboard CPU tile **„Load: 0.29 / 0.39 / 0.37"**; (3) the launcher tile **„Filebrowser"** opens a login in English with no Felhom text (R-513); (4) the storage page mixes formal „Adjon hozzá / Csatlakoztasson" with the product's „te". App first screens a household meets before any Felhom text helps: (5) **Uptime Kuma 2.4 opens on „Which database would you like to use?"** (SQLite / Embedded MariaDB, „Next") — the app card's „Első lépések" does not mention it; (6) PrivateBin, Gokapi, AdventureLog and FileBrowser UIs are English (the apps' own). Already rows: the Proxmox installer screens (R-495, answered by the guide), `wiki.DOMAIN` (R-498). **Fix shape:** rename „Debug"/„Load" (controller); add the Uptime Kuma database step to its card, or pre-seed `db-config.json` for SQLite in the template (catalog). **Added by F4 (20:04:54Z):** (7) the storage page prints the disconnect time as a raw ISO UTC string „Leválasztva: 2026-09-14T19:58:02Z"; (8) the „Meghajtó leválasztva" banner appears twice on every page; (9) „4 telepített alkalmazás nem fut — nézze meg a rendszermonitort" uses the formal form. **Added by F7 (20:50–21:00Z, system disk at 95 %):** (10) a banner on every page in English, „**SSD disk usage high: 90%**"; (11) the dashboard tile reads „Rendszer (/) 61.8 GB / 68.7 GB (**90%**)" while `df` reports **95 %** (reserved blocks ignored), and „(/)" labels the data volume `/mnt/sys_drive`; the deploy page says nothing about free disk. **Added by the i18n spike (2026-09-17, controller v0.247.0):** (12) **six formal („ön") forms in the converted dashboard copy** — „Olvassa be telefonnal" (launcher QR hint), „Biztosan kikapcsolja a megosztást?" (launcher), „Ha újratelepíti … importálnia kell" (the layout's remove-app modal), „Kérjük, vegye fel a kapcsolatot" (backups empty state). They were NOT fixed — a localisation release may not change Hungarian bytes — and are now COUNTED by `controller/scripts/i18n_missing_gate.py` (`HU_FORMAL_CEILING` = 6, a ratchet: a new one convicts, fixing one lowers it). The inventory (`audits/I18N-INVENTORY-2026-09-17.md`) is the list this row closes against in localisation slice 6 (R-561). **Extended 2026-09-17 by slice 1 (controller v0.248.0–v0.250.0):** the converted copy now counts **16** formal forms (`HU_FORMAL_CEILING` 6 → 10 → 12 → 16, each raise stated, Hungarian unchanged by rule) — and the count is an UNDER-count: the gate's stem list sees 4 on the release C pages (storage, drive wizards, debug), while a wider list („írja be”, „adja meg”, „adjon hozzá”, „válassza ki”, „biztosan eltávolítja”, „engedélyezze”, „hozzon létre”, „kattintson”) finds at least **22** keys there alone (login „Adja meg a jelszavát”, the NAS guide, the storage confirms). Widen the stems when this row is worked; the ceiling rises with them. **NARROWED 2026-09-20 by localisation slice 6's walk, item by item** (`audits/i18n-slice6-2026-09-20/R-516-item-by-item.md`): item 2 FIXED (slice 1), items 3 and 6 APP-OWNED (and for an English household item 6 is an advantage), item 11 is a wrong NUMBER rather than a language and needs its own row, item 1 is correct English for an English reader and still open for a Hungarian one. **Items 4, 7, 8, 9 and 10 are NOT DECIDABLE FROM AN ENGLISH WALK** - they are about Hungarian copy quality, a disconnected drive and a full disk, none of which this walk had. **What this row is now waiting for is a HUNGARIAN walk on a box with a second drive**, not another English one; saying it closed would be the kind of closure that makes a register stop meaning anything. **-- 2026-10-08:** the recovery screen's own answers are Go literals in Hungarian only — 14 `renderRecovery` messages in `controller/internal/web/recovery_handlers.go` (seen: the safe default „A művelet nem fejeződött be…" rendered on an English page in a red-proof run). Today's new R-304 sentence is a bundle key in both languages; the 14 old ones are not. | **NARROWED 2026-09-20 - rank P3-LOW; owner: CC; needs a Hungarian walk** **2026-10-05 (burn-down night): items 1 and 4 FIXED on controller `main`** (`d7efa7b`): the menu says „Hibakeresés” (English „Debug”); the storage pages use the te-form (formal-form ceiling 17 → 14; 116 parity fixtures changed by exactly those bytes). Item 2 was already fixed. **Left:** items 5–6 (apps' own screens) and the rest. **2026-10-06: items 1 and 4 DELIVERED** (controller v0.298.0). **2026-10-06 (burn-down night, later): items 7–10 and 12 FIXED on controller `main`** (`e4774e6`, `2e5ef7e`): the disconnect time in local time; one banner per unplugged drive; „nézd meg”; the disk/memory/CPU/temperature banners in the household's language (`health.*` keys; the wire text to the hub unchanged and pinned); the last eleven counted formal forms are te-form (ceiling 14 → 0; 119 parity fixtures changed by exactly those bytes). **Left:** items 5–6 (apps' own screens); about 20 formal forms the gate does not count yet („írja be”, „adja meg”, „hozzon létre”, …) on the debug, storage, network-storage and security pages. Item 11 moved to its own row **R-889**. **2026-10-06 02:40: the bundle has NO formal form left** (controller `4c3c203`, unreleased): 49 sentences in the te-form; the gate's stem list widened (it counted 61 on the previous bundle, 0 now) with decoys and one listed third-person exception. **Left (narrowed):** Felhom-owned formal forms in Go and template literals the gate cannot read yet — the network-storage attach errors, escrow and share handlers, the single-copy notice, a settings refusal, the SMART mail, a fill-watch „Kérjük”, and the setup wizard pages; each moves into the bundle in the te-form. Items 5–6 are the apps' own screens (not ours). **2026-10-06: items 7–10, 12 and the bundle's 49 formal forms DELIVERED** in controller v0.299.0. **2026-10-06 night: the Go-literal leftover moved** (controller main `3d6ba28`, unreleased): 22 Go-literal messages — escrow handler (6), share password page (2), export upload (1), network-storage uid/remove/attach failures (13) — are bundle keys (`api.escrow.*`, `api.share.*`, `api.export.*`, `api.netstorage.*`) in the te-form with English (14 were formal); a detached attach failure renders in the reader's language; the NAS refusal says „Válassz". `TestR516_GoLiteralFormalFormsAreGone` (source scan + positive control), `TestR516_NetAddFailureFollowsTheReader`; red-proofs `audits/night-burndown-2026-10-06/ctrl/R-516-red*.txt`. **Left:** the setup wizard and recovery-info.txt (R-554); the SMART and fill-watch texts (the hub event's message — wire text, needs the household-copy producer shape); items 5–6 (apps' own screens). | — | — | CC |
| **R-991** | Install & onboarding | P3 | **Nothing a buyer can read says which machines Felhom installs on, and a quarter of the forum beginners own only machines it cannot install on.** FOUND 2026-10-12 (forum research, `audits/forum-research-2026-10-12/FELHOM.md` §2). Searched `documentation/architecture/`, `website/` (`gyik`, `technologiak`, `letoltes`) and `scripts/felhom-host-install.sh`: no CPU-architecture, RAM, disk or network floor is written anywhere. The download page says only that the installer is built on Proxmox VE 9.2 — x86-64 only (inferred from Proxmox, not stated on the page). Of the 33 forum beginners who name what they own, 8 own only a Synology/QNAP/other NAS box, a router with a USB disk or a Raspberry Pi. The selfh.st survey reading reached the same gap independently (R-989, its recommendation 1). **Needs (operator):** the floor itself (RAM and disk minimum; whether thin clients and old laptops with 4–8 GB are accepted) — then one short section on the download page and in the FAQ. Not changed here: the research task forbade website edits. | **WAITING-ON-OPERATOR** — filed 2026-10-12 | the operator naming the floor | Operator: name the minimum (RAM, disk, x86-64); then CC writes the section on `letoltes.html` and `gyik.html` (both languages). If nothing is done: a buyer with a Pi or a Synology downloads an ISO that cannot run | operator |
| **R-993** | Install & onboarding | P3 | **Operator: approve the minimum machine in `documentation/audits/sizing-2026-10-13/SIZING.md` §5** (the input R-991's hardware page needs). MEASURED 2026-10-13 on the N100 demo box (61 apps deployed and removed through the product, 15 min at rest each; heavy apps with one real action). Proposal: **minimum** x86-64, 4 cores (N100 class), **8 GB**, 256 GB SSD; **recommended 16 GB**, 512 GB SSD; out: ARM / Raspberry Pi, Synology-QNAP, routers, cloud VPS. Worked from the floor (2.5 GB for the whole box with no apps) + Immich, Jellyfin, Nextcloud, Home Assistant, Vaultwarden, Paperless-ngx at their peaks (5.0 GB) + 50 % headroom ≈ 12.3 GB. 8 GB runs that set without Immich; 16 GB runs all of it twice over. Data for the estimator: `sizing.json`. **2026-10-13 (estimator session) — the installer accepts a host BELOW this minimum:** `autosize_guest_caps` has no floor on the host, only on the guest; on a 4 GB box (MemTotal ≈ 3.5 GiB) the guest gets host − 1 GB ≈ 2.4 GB and Proxmox keeps ≈ 1 GB, where it used ≈ 2.0 GB on the N100 (SIZING.md §1). Whatever minimum is approved, nothing enforces it at install today. The three-verdict wording of §5 now matches the estimator page (`/gepigeny`, R-997). | **WAITING-ON-OPERATOR** — filed 2026-10-13 | the operator's decision | Operator: approve or change §5. If nothing is done: no hardware page; a buyer with a Raspberry Pi can still download the installer (R-991 stays open) | operator |
-| **R-997** | Install & onboarding | P3 | **Operator: try the machine estimator at https://felhom.eu/gepigeny (English: /en/sizing) and say „list it” or what to change.** BUILT 2026-10-13: 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 which apps make the CPU work hard for a short time; numbers from the 2026-10-13 N100 measurement (`documentation/audits/sizing-2026-10-13/`). LIVE but UNLISTED: noindex, `Disallow` in robots.txt, not in the sitemap, linked from nowhere — `site_gates.py` gate 25 keeps it that way. It names no minimum machine (R-993) and gives no power or noise figure. Its JavaScript was never run by CC (no browser or JS engine on DooPlex): the operator's try is its first real run. **To list it** (one website task, after the power readings): move the pair from `UNLISTED` to `TWINS`, drop noindex and the two Disallow lines, add both URLs to the sitemap, link it from the menu and the FAQ. **v2 live 2026-10-13 afternoon:** fold-out categories and a memory bar (solid = fits well, thin mark = tight) with one line naming the box to buy; the reviewer's v1 browser check (Playwright: console clean, 390 px without sideways scroll, only felhom.eu + stats.felhom.eu) asked for the shorter page. **v3 live 2026-10-13 evening:** the bar shows what the box memory is used for (base system, Felhom, each app, spare room) with a legend and one explaining sentence; „an 8 GB machine” fixed. The reviewer's v2 browser check: console clean, 1,677 px tall at 390 px (was 4,592), the bar sticky at 53 px and 124 px tall. **v3.1 2026-10-13 night:** the bar never drawn below an 8 GB box (no more 1.6 GB base system on an empty selection); a single leftover app keeps its name. | **WAITING-ON-OPERATOR** — filed 2026-10-13 | the operator's try | Operator: open the link, tick a few apps, then say „list it” or what to change. If nothing is done: the page stays unlisted and nobody finds it | operator |
| **R-494** | Install & onboarding | P4 | **NARROWED 2026-09-14 by operator ruling → [P3-LOW] the hub COULD create the tunnel at customer creation, for a domain already on Cloudflare. Not blocking: every customer has their own domain and the operator creates the tunnel per day-0 A.1 (`architecture/01-topology-and-trust.md`).** *Original finding, kept:* **[P1-HIGH] A new customer's dashboard has NO reachable address unless the operator hand-makes a Cloudflare tunnel — the link in the setup-code mail is dead.** MEASURED 2026-09-14 on a fresh install from the public ISO (drill intervention **I1**): the claim mail points at `https://felhom.drill0242.felhom.eu`; that name has **no A and no AAAA** record (`dig @1.1.1.1`, control `felhom.enkisfelhom.hu` resolves); the hub has **no tunnel- or DNS-creation code** (`hub/internal/cloudflare/` holds only geo-rule removal; `cf_tunnel_token` is a pasted, optional form field, `configs.go:1478`) — day-0 runbook A.1 makes it a manual Cloudflare-dashboard step that nothing on the customer-create page asks for; the box's own split-horizon resolver on the appliance LAN IP answered `google.com` but not the dashboard name at 13:27:39Z; the agent applied the record at **13:27:44Z** (`lanresolver: applied split-horizon record … ip=192.168.0.158`, 3 m 46 s after the controller started), so the box CAN answer the name — **but only to a device that uses the box as its DNS server, and no document, screen or mail tells a household to do that**; the router and the installer-offered DNS answer nothing. The page was reachable only at the guest's LAN address with the name forced (`curl --resolve …:443:192.168.0.158`). **A volunteer could not have done that.** **What it needs:** an operator ruling — the hub creates the tunnel and DNS at customer creation, or the product gives a household a LAN address that works with no DNS change. | **READY — rank P3-LOW; owner: CC** **Re-ranked 2026-10-03: P3→P4: operator-side automation; the operator creates the tunnel by hand per the day-0 runbook.** | — | — | CC |
| **R-504** | Install & onboarding | P4 | **[P3-LOW] `iso.felhom.eu` cannot show an index page on its own — its root returns 404, and the download page lives on the website instead.** MEASURED 2026-09-14: `https://iso.felhom.eu/` and `/index.html` → 404; only named objects answer. The host is an R2 bucket behind a custom domain; whether R2 would serve an uploaded `index.html` at `/` was **not measured** (uploading anything to the public bucket is a publication). The ISO v1.27.0 task puts the Hungarian download page at `felhom.eu/letoltes` (published with the ISO, after the operator's yes). **Remaining:** a redirect from `iso.felhom.eu/` to that page needs a Cloudflare rule the session has no credential for. | **WAITING-ON-OPERATOR — rank P3-LOW; owner: operator (Cloudflare rule)** **Re-ranked 2026-10-03: P3→P4: households are sent to the website's download page; the bare address is cosmetic.** | — | — | operator |
diff --git a/scripts/CHANGELOG.md b/scripts/CHANGELOG.md
index 636b2c39..77c799cb 100644
--- a/scripts/CHANGELOG.md
+++ b/scripts/CHANGELOG.md
@@ -1,3 +1,10 @@
+## 2026-10-13 (night) — site_gates: the machine estimator moves from UNLISTED to TWINS (R-997)
+
+- `site_gates.py`: the `gepigeny`/`en/sizing` pair is a normal twin; `UNLISTED` is empty and gate 25 stays for the next
+ such pair. The sitemap check now requires both URLs.
+- `test_build_sizing_web.py`: `test_sentence_base_is_the_drawn_box_base` (13 tests) — the sentence's base figure is the
+ bar box's base (4.0 GB at 8 GB, 4.6 GB for the household preset). Red-proved: a fixed 4,708 MB base fails it.
+
## 2026-10-13 (evening) — power-off spike on the N100: plugswitch, wall-power figures
- New `scripts/bench/plugswitch.py` (`on`/`off`/`status`) + `test_plugswitch.py` (7 tests): `off` refuses unless 20 s of
diff --git a/scripts/site_gates.py b/scripts/site_gates.py
index c386cdc9..9b23bbaa 100644
--- a/scripts/site_gates.py
+++ b/scripts/site_gates.py
@@ -84,6 +84,7 @@ TWINS = {
"letoltes.html": os.path.join("en", "download.html"), # R-559 (2026-09-18) — the first twin
"teszteles.html": os.path.join("en", "testing.html"), # 2026-10-10 — the tester recruitment page
"szolgaltatasok.html": os.path.join("en", "services.html"), # 2026-10-12 — was a section of the home page
+ "gepigeny.html": os.path.join("en", "sizing.html"), # 2026-10-13 — the machine estimator; listed the same day (R-997)
}
URL = {"index.html": "/", "alkalmazasok.html": "/alkalmazasok", "technologiak.html": "/technologiak",
"biztonsagimentes.html": "/biztonsagimentes", "gyik.html": "/gyik", "kapcsolat.html": "/kapcsolat",
@@ -114,7 +115,8 @@ NO_TWIN = {"szolgaltatasok-nonpublic.html", "404.html", "adatkezeles.html", "fel
# English page), and gate 25 adds what unlisted means: `noindex` on both pages, a `Disallow:` line for each URL in
# robots.txt, absent from sitemap.xml, and linked from no other page. To LIST it: move the pair into TWINS, drop
# noindex and the Disallow lines, add both URLs to the sitemap and a link from the menu — in one commit.
-UNLISTED = {"gepigeny.html": os.path.join("en", "sizing.html")}
+# Empty since 2026-10-13: the machine estimator was listed (R-997). The machinery stays for the next such pair.
+UNLISTED = {}
URL.update({"gepigeny.html": "/gepigeny", os.path.join("en", "sizing.html"): "/en/sizing"})
ALL_TWINS = dict(TWINS, **UNLISTED)
diff --git a/scripts/test_build_sizing_web.py b/scripts/test_build_sizing_web.py
index 228351aa..4c8f9824 100644
--- a/scripts/test_build_sizing_web.py
+++ b/scripts/test_build_sizing_web.py
@@ -158,6 +158,17 @@ class SizingWeb(unittest.TestCase):
self.assertEqual(dict(segs)["base"], 4096) # 8 GB: 8,192 - guest 4,096 — not the 1,636 of a 2.3 GB box
self.assertEqual(dict(segs)["spare"], 4096 - self.d["platform_mb"])
+ def test_sentence_base_is_the_drawn_box_base(self):
+ # the explaining sentence's „kb. {base} GB a gép alaprendszeréé” is the base part of the box the BAR draws,
+ # from the same rule: 4.0 GB when the bar is an 8 GB box, 4.6 GB for the household preset (a 12.7 GB bar)
+ for name, sel, want in (("files and passwords", ["nextcloud", "vaultwarden"], "4.0"),
+ ("household", HOUSEHOLD, "4.6")):
+ _, segs = segments(self.d, sel)
+ self.assertEqual("%.1f" % (dict(segs)["base"] / 1024), want, name)
+ js = io.open(JS, encoding="utf-8").read()
+ self.assertIn("base_mb: boxMb - guestMb", js)
+ self.assertIn(".replace('{base}', dec(r.base_mb / 1024))", js)
+
def test_grouping_keeps_a_single_leftover_named(self):
by_peak = [a["slug"] for a in sorted((a for a in self.d["apps"] if not a.get("builtin")), key=lambda a: -a["peak_mb"])]
named, grouped = legend_parts(self.d, by_peak[:9])
diff --git a/website/404.html b/website/404.html
index d108dd8e..0097208f 100644
--- a/website/404.html
+++ b/website/404.html
@@ -41,6 +41,7 @@
diff --git a/website/CHANGELOG.md b/website/CHANGELOG.md
index 4218df71..fe29ed3e 100644
--- a/website/CHANGELOG.md
+++ b/website/CHANGELOG.md
@@ -1,4 +1,15 @@
-## 2026-10-13 (night) — machine estimator v3.1: two fixes from the reviewer's browser check
+## 2026-10-13 (night) — the machine estimator is listed (R-997 closed)
+
+- **Public now:** `noindex` removed from `/gepigeny` and `/en/sizing`; their `Disallow` lines removed from robots.txt;
+ both in sitemap.xml with their hreflang pair.
+- **Menu:** „Milyen gép kell?" / „Which machine do I need?" is the last item of the Alkalmazások / Apps group on every
+ page of each language (active and open on the estimator itself).
+- **Links:** one sentence at the end of the FAQ answer „Milyen gépre van szükségem?" / „What machine do I need?" (the
+ JSON-LD carries it too), and one line under the apps page intro („Mekkora gép kell ezekhez? →").
+- **The explaining sentence:** its base figure was already the base of the box the bar draws (4.0 GB on an 8 GB bar,
+ 4.6 GB for the household preset); a test now pins that. No JS, CSS or data change, so no cache version moved.
+
+## 2026-10-13 (night) — machine estimator v3.1: two fixes from the reviewer's browser check
- **The bar is never drawn for a box smaller than 8 GB** (the smallest size the page names). With nothing or very
little ticked, the „fits well" size was about 2.3 GB, where the installer's ceiling clause gave a 1.6 GB base
diff --git a/website/adatkezeles.html b/website/adatkezeles.html
index 2a17805e..e7fa46a7 100644
--- a/website/adatkezeles.html
+++ b/website/adatkezeles.html
@@ -54,6 +54,7 @@
diff --git a/website/en/faq.html b/website/en/faq.html
index c6b4577b..ed3228eb 100644
--- a/website/en/faq.html
+++ b/website/en/faq.html
@@ -77,7 +77,7 @@
"name": "What machine do I need?",
"acceptedAnswer": {
"@type": "Answer",
- "text": "For most homes a mini PC (for example with an Intel N100 processor and 16-32 GB of RAM) is perfectly fine. They are quiet, energy-saving (15-35 W) and compact – one fits on the shelf next to the router. If you want more storage (for a film library, say), you can add a NAS or external hard drives. More detailed set-ups are on the Technology page."
+ "text": "For most homes a mini PC (for example with an Intel N100 processor and 16-32 GB of RAM) is perfectly fine. They are quiet, energy-saving (15-35 W) and compact – one fits on the shelf next to the router. If you want more storage (for a film library, say), you can add a NAS or external hard drives. More detailed set-ups are on the Technology page. To estimate how big a machine your own apps need, use the Which machine do I need? page."
}
},
{
@@ -398,6 +398,7 @@
For most homes a mini PC (for example with an Intel N100 processor and 16-32 GB of RAM) is perfectly fine. They are quiet, energy-saving (15-35 W) and compact – one fits on the shelf next to the router.
If you want more storage (for a film library, say), you can add a NAS or external hard drives. More detailed set-ups are on the Technology page.
diff --git a/website/en/sizing.html b/website/en/sizing.html
index ec6f3a0e..2865067e 100644
--- a/website/en/sizing.html
+++ b/website/en/sizing.html
@@ -6,7 +6,6 @@
Which machine do I need? — an estimate for the apps you pick | Felhom.eu
-
@@ -39,8 +38,8 @@
diff --git a/website/gyik.html b/website/gyik.html
index 31f48029..a83ab13b 100644
--- a/website/gyik.html
+++ b/website/gyik.html
@@ -77,7 +77,7 @@
"name": "Milyen gépre van szükségem?",
"acceptedAnswer": {
"@type": "Answer",
- "text": "A legtöbb otthoni felhasználónak egy mini PC (pl. Intel N100 processzorral, 16-32 GB RAM-mal) tökéletesen megfelel. Ezek csendesek, energiatakarékosak (15-35W fogyasztás), és kompaktak – elfér a polcon a router mellett. Ha nagyobb tárhelyet szeretnél (pl. filmes könyvtárhoz), egy NAS-al vagy külső merevlemezekkel bővíthető. Részletesebb konfigurációkat a Technológiák oldalon találsz."
+ "text": "A legtöbb otthoni felhasználónak egy mini PC (pl. Intel N100 processzorral, 16-32 GB RAM-mal) tökéletesen megfelel. Ezek csendesek, energiatakarékosak (15-35W fogyasztás), és kompaktak – elfér a polcon a router mellett. Ha nagyobb tárhelyet szeretnél (pl. filmes könyvtárhoz), egy NAS-al vagy külső merevlemezekkel bővíthető. Részletesebb konfigurációkat a Technológiák oldalon találsz. Hogy a te alkalmazásaidhoz mekkora gép kell, a Milyen gép kell? oldalon becsülheted meg."
}
},
{
@@ -398,6 +398,7 @@
A legtöbb otthoni felhasználónak egy mini PC (pl. Intel N100 processzorral, 16-32 GB RAM-mal) tökéletesen megfelel. Ezek csendesek, energiatakarékosak (15-35W fogyasztás), és kompaktak – elfér a polcon a router mellett.
Ha nagyobb tárhelyet szeretnél (pl. filmes könyvtárhoz), egy NAS-al vagy külső merevlemezekkel bővíthető. Részletesebb konfigurációkat a Technológiák oldalon találsz.
+
Hogy a te alkalmazásaidhoz mekkora gép kell, a Milyen gép kell? oldalon becsülheted meg.