test(proc): recognize the Windows recorder by executable path

Problem: The Windows fallback control missed its recorder marker and could
not remove the still-running taskkill test executable.

Root cause: exec.Command("taskkill", ...) preserves the bare command in
argv[0]. The recorder compared that argument with taskkill.exe, missed its
special entry point, and entered the complete package suite instead.

Fix: Identify the recorder with os.Executable, require LookPath to select
the fixture's same file, and fail closed on an unexpected recorder entry.
Add a bare-command alias probe whose fallback selector runs only the inert
helper. Run/Wait completes before temporary-directory cleanup. Keep the
production ownership repair unchanged and extend the native inventory to
seven pass events versus four expected failures and three passing controls.

Verification: Windows cross-compile, Windows vet and pinned Windows proc
lint pass; full root vet/lint and make check pass at unchanged baseline.
All 6268 selected Darwin inputs match the previous qualified commit; this
append changes only the Windows fixture, verifier inventory and docs.
The complete original Windows failure log is preserved. Fresh native
Windows execution on this new commit remains required, not inferred.

scripts/published-job-evidence.mjs

@@ -9,6 +9,7 @@ const required = [
   'TestPublishedJobNoPIDFallback/cancelled_wait',
   'TestPublishedJobUsesKernelTree',
   'TestPublishedJobFallbackControl',
+  'TestPublishedJobRecorderAlias',
 ];
 const failures = new Set(required.slice(1, 5));
 const [mode, destination] = process.argv.slice(2);