# REPORT — agent 0.175.1 (2026-11-15) Released and vouched in the attended run of 2026-11-15. The full report is felhom.eu `REPORT-release-2b-3-2026-11-15.md`. - **What:** trust in Proxmox by a copy of the box's own root CA, with the move from a pinned certificate; the report carries the clock at sending; a refused signed job, a guest-power give-up, the kernel clean-up detail and the profile refresh reach the hub; a boot key that a clock step cannot move; a cut write of `agent.json` is repaired at start; root files older than the agent are not a trust problem on a pinned box. - **Versions:** 0.175.1 — binary sha256 `38b1e2350de90a7940c16f8cd2a21d83fcd535410d1017a7df0fee14f0904612`, bundle `07ebf86362ed9d44776416bd5c2c4b6b629e44d34595a8120fd8fc3f4d9277ff`, from `88d5d56`, CI run 2678; vouched 2026-11-15 11:07:35 CET; the day-0 pin is set. 0.175.0 (from `db01ae0`) was released the same morning, reached Tester 1 only, and is NOT vouched: it raised one false trust alarm between the agent update and the root-files update. - **Proven on boxes:** Tester 1, demo-hp and the N100 moved (a working call with the copy first, the fingerprint cleared last); two forced new Proxmox certificates on demo-hp with no restart and no alarm; a wrong CA copy repaired at start; a fresh install starts with the copy and no fingerprint; the clock alarm at the hub. - **Tests only:** the repair after a real power cut; the refused-job and give-up messages. - **Open:** a fully blind box sends no report (felhom.eu R-1396 gap 2); one Proxmox call answered 500 at day-0 with no ERROR line (R-1397).