Setup lists host processes only before writes and after waits
Draft
AN
8h ago+436+436+012345678901234567890123456789-45-45-01234567890123456789
Read-only planning and revalidation keep their supervised-auth and enrollment checks, but no longer list processes. Every publication still gets a fresh check. On Windows ARM without PowerShell 7 each listing costs 22-36 s.
Summary by cubic
Read-only setup planning no longer lists running host processes when run through the setup CLI, making setup faster on Windows ARM where each listing costs 22-36 seconds.
- Planning, revalidation, and preflight keep their supervised-auth and enrollment checks; only the process listing is dropped.
- Every journal or file publication still gets a fresh stopped-host check before writing.
- Pi vault activation fences only when the auth slot needs to change, and vault enrollment fences before running the grant command instead of before reading status.
- Direct callers of the exported local and vault helpers still list processes at entry; only the setup CLI marks calls as already checked by the shared runner.