Files
felhom.eu/REPORT.md
T

28 lines
2.1 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# 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).
## NAS verify-before-commit — felhom.eu share (host-install v1.13.0 + feature doc) — 2026-07-11
Part of the cross-repo task (agent **v0.81.0** + controller **v0.113.0**, both LIVE on the demo;
full task-wide record incl. red-proofs + the AE live-validation transcripts:
`felhom-controller/REPORT.md`). This repo's commit: `27e2fb0`.
- **`scripts/felhom-host-install.sh` v1.13.0** — the agent-user setup adds `felhom-agent` to the
**`systemd-journal` group** (idempotent `usermod -aG`): the verify pipeline classifies mount
failures from an UNPRIVILEGED `journalctl` read; group membership instead of a sudoers grant.
Existing installs: `usermod -aG systemd-journal felhom-agent && systemctl restart felhom-agent`
**applied to the demo host (felhom-pve) during this task's live validation**; Peti's box gets
it only when the NAS feature reaches him. Also fixed: the header still said v1.11.0 while
`SCRIPT_VERSION` was 1.12.0 (the 1.12.0 bump had no changelog entry either) — both now 1.13.0.
- **NEW `documentation/controller/network-storage-nas.md`** — the authoritative network-storage
feature doc (none existed; the knowledge lived only in the two spike docs): the locked recipes
(incl. `retry=0` + its evidence), the verify pipeline, the §8 mount-truth table, the Q4 error
taxonomy (with the merged `nfs_export` honesty rule), the protocol-honest NAS-side recipes
(SMB plain-user; NFS map-all-users vs full-fidelity `anonuid=<uid+100000>`), Route A caveats
incl. the operator-facing "chmod succeeds and persists" nuance, and the open items (Q1c
restart-window test, appliance pass).
No hub/website/manifest changes; nothing to deploy from this repo (the script ships via the Day-0
supply chain on the operator's publish decision — NOT triggered by this task).