docs: REPORT + CONTEXT for the NAS verify-before-commit share (host-install v1.13.0)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PSK5g6qYLknKj8u3QAFEr6

CONTEXT.md

@@ -3,6 +3,16 @@
 > Created with the REUSE.md rollout (2026-07-03). Authoritative history: `hub/CHANGELOG.md` (hub),
 > `website/CHANGELOG.md`, `scripts/CHANGELOG.md`; end-of-task detail in `REPORT.md`.
 
+- **2026-07-11 — NAS verify-before-commit SHIPPED (agent v0.81.0 + controller v0.113.0 LIVE on demo;
+  host-install v1.13.0).** The spike's production task landed same-day: add = agent verify (retry=0
+  unit, journal-classified, auto-rollback) → controller uid-1000 write probe (--netprobe re-exec) →
+  register LAST; full rollback on any failure; §3.2 Hungarian error map (nfs_export merged);
+  storage_network.html redesigned (SMB-first, Route-A guidance); orphan rows; systemd-journal group
+  (NO sudoers). Live A–E validated vs an isolated sim NAS, Route A proven in production (alien-uid
+  1060 server-side). Feature doc: `documentation/controller/network-storage-nas.md`. NOT published
+  (no Gitea/Day-0 bump; Peti pending with the usermod one-liner). Record:
+  `felhom-controller/REPORT.md`.
+
 - **2026-07-11 — SPIKE: NAS verify mechanisms + NFS squash matrix — ALL FIVE QUESTIONS ANSWERED, no
   blocker.** Record: `documentation/audits/SPIKE-nas-verify-2026-07-11.md`. Q1 in-guest access DOES
   wake the host automount (make-or-break PASS; container bind-mount too); Q2 controller drops to uid