# felhom.eu — task reports

> **Overwrite** this file with a summary of the most recent task only (uniform with the other repos; not cumulative). The cumulative hub history lives in [hub/CHANGELOG.md](hub/CHANGELOG.md); the scripts history lives in [scripts/CHANGELOG.md](scripts/CHANGELOG.md).

## N100 polish — F5 guest auto-sizing (host-install v1.17.0) + docs — 2026-07-17

Closes `documentation/tests/VALIDATION-n100-baremetal-2026-07-16.md` **F5 (MEDIUM)**. Companion to the
controller v0.141.0 F6/F7 fixes (see the felhom-controller REPORT). `bash -n` + the mode harness pass.

### F5 — appliance guest auto-sizing (`scripts/felhom-host-install.sh` v1.17.0)
The golden default (2 GB RAM) reached the guest on a 16 GB host because appliance mode passed no
`--memory`/`--cores`. Now, in **appliance** mode with no explicit cap, the guest is auto-sized from
the host: `autosize_guest_caps` runs right after mode validation (before the plan summary + provision)
and fills `MEM_MIB`/`CPU_CORES`:
- RAM = `clamp(host-4096, min 4096, max host-2048)` then a hard ceiling `host-1024` (never
  over-commit). Sizing: 8 GB→4096, 16 GB→12288, 32 GB→28672 MiB; a 4 GB host→3072 (min capped at the
  ceiling — the edge rule).
- cores = `host-1, min 2`.
- An explicit `--memory`/`--cores` ALWAYS wins untouched; byo mode still requires explicit caps (never
  auto-sized). The values flow into the existing `cap_args` → the agent's `-memory`/`-cores`.
- Host reads (`MemTotal`/`nproc`) are overridable via `FELHOM_FAKE_MEMTOTAL_MIB`/`FELHOM_FAKE_NPROC`.
- **Red-proof:** `hostinstall-mode-harness.sh` new F5 section (8/16/32 GB + small-host edge +
  explicit-flag precedence) — the auto-size log line is emitted before any PVE contact, so it asserts
  portably; pre-fix (auto-size disabled) FAILs, post-fix PASSes.

**Same commit (R-16 doc-drift leftover, R-20 closure note):** the operator-signing-keys "EMPTY by
default" comment was stale (the keys are PINNED to the real `felhom-op-1`/`felhom-rec-1` ceremony
keypairs) — corrected, comment-only, no behavior.

### NOT live this task
F5 is validated by harness only — live at the next from-scratch rehearsal (Viktor's planned
delete/re-create run); stated in the ROADMAP and the VALIDATION disposition.

### Docs updated
VALIDATION-n100 F5/F6/F7 dispositions → FIXED-in-vX (erratum style); capability map drive-wizard row →
F6 fresh-USB wizard enroll+format **PROVEN-LIVE**; ROADMAP R-16 (doc-drift bit closed), R-22 & R-13
already PROVEN-LIVE, new **R-24** (guest resources as hub desired-state / live resize — the F5
follow-on); operator-sidebar item #1 (BIOS "State After G3 → Power On") added to `scripts/iso/README.md`.

### Operator sidebar (Viktor — CC does NOT do these; recorded verbatim)
1. **BIOS "State After G3" → "Power On"/"Last State"** before final sign-off — added to
   `scripts/iso/README.md` hardware-prep notes.
2. **campaign6 autofs orphan** — clears at the next host reboot.
3. **tied-CreatedAt flash duplicates** (audiobookshelf/komga/romm) — standing action item.