admin
97d3c29f9c
gates / gates (push) Successful in 5m24s
Second Facebook task of the day. Page settings changed by hand in the operator's Chrome; every edit read back from a channel other than the one that made it, because Meta's toasts have lied here before (2026-10-08: "A modositas nincs mentve" arrived with a partial save). - Contact (B1) was ALREADY SET, by the operator, before this run: Graph reads emails ["info@felhom.eu"] and phone "+36702378499". Verified, not typed. - Place (B2) already city-only Budapest, as the operator chose. Service area REFUSED: Facebook offers the field but its picker has no "Magyarorszag", only cities. Control: "Szeged" returns Szeged. Left unset rather than narrowed to Budapest, which would shrink a coverage claim nobody authorised. - Categories (B3) DONE: Informatikai vallalat (kept first, the only one shown) + Internetes ceg + Szoftverceg. Facebook's Hungarian list has no IT-support, IT-consulting or cloud category; eleven terms searched, and the one true match is a repair counter, which the fences rule out. - Hours (B4) CANNOT be set and need not be: Facebook requires a street address first, which the fences forbid. Measured on the rendered page with controls present -- Zarva 0, Nyitva 0 while Budapest 1, Informatikai vallalat 1. The Page will never show "Zarva". - Messenger FAQ (B5) REFUSED -> R-920: the automation does not exist for this Page. Catalogue holds exactly three templates; search "kerdes" returns none while the control "uzenet" returns two. COPY.md section 5 is written anyway, questions verbatim from gyik.html and answers condensed from each question's own answer, and waits like section 2 does (R-917). - Link preview correct in both languages, re-scraped once each; only the expected fb:app_id warning, deliberately not fixed. Both report HTTP 206 where a plain curl gets 200 -- Facebook's scraper, preview complete. fb_probe.py read now also reports emails, phone, category_list, location, single_line_address and hours, ONE FIELD PER CALL: a batched fields= list fails whole when any member is unreadable, which would let one refused field hide the other five. Refusals are logged verbatim and never retried; "null" and "not returned" are logged apart. hours is never returned by Graph, which is why B4's read-back had to come from the rendered page. Also corrects the "Business & legal" header, which read 12 rows (P2 5) over a section holding 11 (P2 4); with R-920 it is 12 (P2 4, P3 1, P4 7). Only the section this commit edits -- the other drifting headers belong to a session that owns the register. No post, no invite, no money, no app or portfolio change, website unchanged.
Felhom — Documentation
Felhom is a managed home-server service for Hungarian households, built on a three-component model over Proxmox:
- Hub — operator backend on k3s (
hub.felhom.eu). Repo:felhom.eu/hub/. - Host agent — one per Proxmox host; operator-tier; owns all Proxmox interaction. Repo:
felhom-agent/. - In-guest controller — one per customer LXC; Docker-only; manages the customer's apps. Repo:
felhom-controller/.
This directory is the central, code-verified documentation home for all three components plus the platform and the security-audit record.
Sections
Controller (in-guest) — controller/
The Docker-only app-domain controller. Full per-area docs grounded in current source (v0.59.0).
→ controller/README.md: module map, deploy & stack lifecycle, backup
architecture, storage/monitoring/metrics, auth/hub/sync/integrations.
Where we stand — architecture/where-felhom-stands.*
The operator's one-page picture of what is proven, built, partial and missing.
architecture/where-felhom-stands.html— generated; do not hand-editarchitecture/where-felhom-stands.yaml— the data behind it; every claim cites its source. Gate:scripts/check_stands.py; regenerate withscripts/render_stands.pyarchitecture/where-felhom-stands-2026-08-09-snapshot.html— a dated snapshot, NOT maintained. The original React bundle, kept for the record; its statuses are those of 2026-08-09 before the verification pass
Host agent & platform — architecture/, proxmox-platform.md
The operator-tier agent and the Proxmox platform.
architecture/01-topology-and-trust.md— topology & trust modelarchitecture/03-host-agent.md— the host agent (Go; v0.29.1)architecture/04-control-plane-authorization.md— signing, escrow, authzarchitecture/02-controller-module-map.md— historical v0.33 planning map; the live map iscontroller/module-map.mdproxmox-platform.md— Proxmox platform referencearchitecture/11-os-updates.md— operating-system updates: host, guest, Docker engine (NOT RATIFIED, 2026-10-04)
Hub (operator backend) — architecture/05
architecture/05-hub-architecture.md— hub architecture (v0.11.0)
Security audits & remediation — audits/
audits/deep-sweep-2026-06-13.md— cross-repo deep audit (controller + agent) with remediation statusaudits/bughunt-reconcile-2026-06-13.md— reconciliation of the v0.30.3 BUGHUNT against current code + merged fix list
Spike & test findings — tests/
Per-slice spike/validation findings (phases 0–5, slices 7–10). See tests/.
Conventions
- Code-verified, not memory-derived. Architectural claims here are checked against the actual current source; if a claim can't be verified it is omitted and flagged, not guessed.
- Per-repo operational working files (
CLAUDE.md,CONTEXT.md,CHANGELOG.md,BUGHUNT.md,REPORT.md,TASK.md) live in their own repos — they are operational, not published docs. - Authoritative versions at last refresh: controller v0.59.0, agent v0.29.1, hub v0.11.0.