diff --git a/REPORT-release-2a-2026-11-14.md b/REPORT-release-2a-2026-11-14.md new file mode 100644 index 00000000..0dfc7cfd --- /dev/null +++ b/REPORT-release-2a-2026-11-14.md @@ -0,0 +1,131 @@ +# REPORT — release 2a: the box removes its old kernels, and refreshes its security profiles after a kernel change (2026-11-14, attended at one STOP) + +## 1. Claims in the prompt that turned out wrong, named first + +1. **„A night can be started on a test box by an existing path" — FALSE.** The agent starts the night leg only + after the night's OWN whole-guest backup. A manual backup does not start it, by design (R-899), and the debug pass + runs with trigger `debug`, which the kernel step and the clean-up refuse, by design. So the real clean-up on + Tester 1 was **started by hand** with the agent's own command line, not „through the night leg's own path". The + step by the agent at night is **not proven yet**. Filed: R-1394. +2. **„Tester 1 — the first real clean-up by the program" needed something the prompt did not name.** Tester 1 is + ring 1 and has **no root-owned ring-0 mark**, and the release runs the clean-up on ring-0 boxes only (the prompt's + own scenario 8). The program answered „not run" there, correctly. CC wanted to set the mark by hand; Claude Code's + own safety check refused that, rightly. CC asked at the STOP; **the operator said yes** to the mark for the test. + It was set for under a minute and is back as before (proven in the evidence). +3. **„The wrapper is reached by `--plan` only, so a new mode needs no new sudo line" — TRUE.** Pinned by a test, and + seen live: both new modes ran through the one existing line. +4. **„The result can ride the existing OS-update report" — TRUE in part.** A clean-up that removed kernels reaches + the hub as a kernel-layer report; the hub stores it and shows „cleaned