admin
b14b5a65d9
ROADMAP: - R-39 gains the full live diagnosis and REFUTES the brief's hypothesis. The generation IS bumped (SetHostDesired bumps unconditionally, 2->3) and applyPBSDR is exonerated, so no hub fix was shipped. The real mechanism is a signal mismatch: the hub's re-consume signal is a generation bump + poke, while the agent re-applies on a change of the DESCRIPTOR CONTENT HASH (manager.go ~L235). An ep0 re-issue re-keys the secret of an EXISTING token, so token_id/fingerprint are unchanged, the descriptor is byte-identical, the hash never moves, and the fresh secret is never consumed -> 401 forever. Proof: consumed-failed.json carries the same hash a4e5424... as the marker written two minutes before the re-issue. Records the second defect found while healing (wrapper reconcile passing --server, fixed in agent v0.90.1), marks the box HEALED with evidence (pvesm active, token 200, a real 9.7 GB encrypted backup listed PBS-side), and leaves the fleet fix explicitly pending its own spec. - R-33 collapses to SHIPPED (scripts v1.21.0), incl. why TimeoutStartSec=infinity is the load-bearing half. - Pre-invite checklist: golden target moves 0.145.x -> 0.146.0 and notes it is now MORE stale, since v0.146.0 is live on the demo box while the golden still bakes 0.143.0. REPORT overwritten with the train: R-39 diagnosis verbatim + heal evidence, the two ISO shas with the byte-identical-payload verification, the nav polish and why the screenshot leg could not be done (the demo controller password is customer-owned since the claim flow, so the build-server credentials are stale), Phase 4 skipped cleanly, and Phase 5 deferred rather than half-run. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Nn3VgQk9iwEGgyx6QJ2NvE
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.
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 reference
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.