Files
felhom.eu/documentation/backlog
admin a2ca6eb413
gates / gates (push) Failing after 6m36s
Website: a page for people who search „felhő tárhely" (R-1033..R-1035)
Search Console (3 months, read 2026-10-14): 48 impressions, 1 click, average
position 73.6; the top query is „felhő tárhely" (19). No page on the site used
the phrase — Google was showing the home page by accident.

New pair /sajat-felho-tarhely + /en/own-cloud-storage: what cloud storage is and
the three ways to have one; what to do when the Google or iCloud storage is full
(the free clean-up first, linked to Google's and Apple's own help; the paid
options second); a five-year cost table; where the data sits; who should NOT
choose this; the closed test. Registered in site_gates.py TWINS/URL/SHELL, both
URLs in sitemap.xml (22 -> 24). FAQPage JSON-LD derived from the visible text.

Prices each read 2026-10-14 on the provider's own Hungarian page, with the URLs
and the date in an HTML comment and a visible „Árak" line: Google AI Plus (2 TB)
— Google One's 2 TB plan — 35 990 Ft/év (behind the „Éves" toggle; a plain fetch
sees only the monthly 3 590 Ft), iCloud+ 2 TB 4 490 Ft/hó, Microsoft 365 Családi
(2 TB shared, no longer 1 TB per person) 46 499 Ft/év.

Felhom's own cost follows what the site already said (operator ruling): machine
and install one-off, power, off-site storage monthly by volume, operation
OPTIONAL, no fee during the closed test. Power is stated as an idle measurement
(nyugalmi állapotban 7-9 W, ~75 kWh/év, from audits/night-power-2026-10-13) and
the page says a year with daytime use is more; no daytime figure and no
electricity tariff are given, because neither is measured or sourced.

FAQ corrected (both languages, JSON-LD re-derived): the cost answer carried
unsourced, undated prices and summed Spotify and a password manager into a
storage comparison; and the page contradicted itself on electricity („havi
néhány ezer forint" vs „évi 5.000–15.000 Ft"). App count 60 -> 62 in the four
places that were stale.

Three defects found on the rendered page and fixed: a .vs-row link fell back to
the browser-default blue (contrast 1.99 -> 7.17); 24px of horizontal scroll at
390px because .method-pros li is a nowrap flex row and the new items contain
links (each item's content wrapped in one span); .info-card and .method-pros
were scoped to the pages that first used them. site.css ?v=31 on all 26 pages.
The shared .content-section padding was NOT changed — it is identical on every
page; the new page only lacked the alt-bg alternation, and now has it.

R-1033 the apps page lags the catalog by two apps (plant-it, wger); R-1034 gate
17 checks the FAQ JSON-LD on two hard-coded pages only; R-1035 the SEO result,
with dated checks on 2026-11-11 and 2026-12-09.
2026-10-14 18:51:42 +02:00
..

documentation/backlog/

OPEN-ITEMS.md is the register of open work and the file to read first — it holds only what is open, one row per item, every row with a category, a severity, a state and an owner (the layout is at its top). CLOSED-ITEMS.md holds every finished row, compressed, with the commit that keeps its full text; a row moves there in the same commit that closes it (scripts/closed_register_gate.py RULE 3). ROADMAP.md holds intentions — features and spikes that do not exist yet — and ROADMAP-HISTORY.md the shipped and killed ones. An R-n id is minted once and never reused.

The other files in this folder — verdict per file (2026-10-03 triage)

File Verdict
SPEC-app-data-placement-2026-08-21.md KEEP — still referenced by open rows R-352 (placement still open) and R-368.
SPEC-r85-phase4-5-2026-07-26.md KEEP as history — a spec of shipped work (R-85, agent v0.104.0). CONTEXT.md and architecture/00-capability-map.md link here.
FOLLOWUP-nas-automount-guest-reboot-reassert.md FINISHED, kept in place — shipped in agent v0.84/v0.85 (CAMPAIGN-3). Not moved because CONTEXT.md, controller/network-storage-nas.md and felhom-controller/CONTEXT.md link to this path.

Moved to documentation/archive/ on 2026-10-03 (finished; nothing open refers to them):

  • FIX-M18-NOTES.md — dump re-validation every 5 min. FIXED in controller v0.62.0 @ f8afe5c (2026-06-14).
  • FIX-M19-NOTES.md — deriveStackName misattribution edge. FIXED in controller v0.62.0 @ 6bab68b (2026-06-14).
  • FOLLOWUP-golden-default-controller-tag.md — the golden baked a stale controller. FIXED in felhom-agent @ ceca355 (2026-07-03): build-golden.sh v2.0.0 makes the controller tag a mandatory argument. Evidence: ../audits/DRILL-golden-098-2026-07-03.md.
  • DIAGNOSIS-f9-storage-registration-gap-2026-06-14.md — a read-only diagnosis of June 2026, superseded by the shipped F9 fixes (controller CHANGELOG.md cites it as history).

The archive also holds OPEN-ITEMS-narratives-2026-10-03.md: the campaign write-ups, rulings and ranking paragraphs that sat between the register's tables until the triage, word for word.