fix(pi): prove packaged workers end to end

.project-docs/30-worklog/tasks/20260824-pi-release-proof-3e725ac7.md

@@ -8,7 +8,7 @@
 - Worktree: D:\Datas\OthersProjects\makelore-pi-release-proof-3e725ac7
 - Base commit: 977445ba450f4ad32b6e6db2caf048517513ab39
 - Owner: codex-root
-- Status: Ready for Planner Re-review (platform release blockers remain)
+- Status: In Progress (second planner Spec review fixes required)
 
 ## Scope
 
@@ -37,10 +37,9 @@
   risks, never Pass; every substitute report retains
   `realTurnVerified=false`.
 - The user explicitly skipped macOS validation. Do not manufacture or reuse
-  static/cross-platform evidence for macOS x64 or arm64. Their missing final
-  artifact, closure/native/resource, loopback, and performance evidence remains
-  an explicit release blocker, so this task cannot claim cross-platform
-  release-ready or PI-150 Done.
+  static/cross-platform evidence for macOS x64 or arm64. Per the planner's
+  second review this evidence is deferred to PI-160: it remains Not Pass and a
+  final cross-platform release blocker, but is not a PI-150 blocker.
 - The canonical project memory at this base is stale and still describes
   OpenCode. Treat the planner-owned PI Spec/ticket and current source as the
   task authority; do not edit canonical memory in this feature worktree.
@@ -85,10 +84,12 @@
   under the pinned upstream `@earendil-works/pi-ai/dist/providers/opencode*`
   closure remain classified separately because Pi imports them; they are not
   Makelore-owned runtime residue.
-- The five requested fixes are ready for planner re-review, but PI-150 remains
-  blocked from `Done`, PI-160 must not start, and the product is not
-  cross-platform release-ready: macOS x64/arm64 was explicitly skipped and no
-  independent native non-WSL Linux desktop/compositor acceptance run exists.
+- The second planner review accepted the ASAR enumeration and RPM fixes but
+  found three remaining P1 proof defects: final subagent still used a fake
+  in-process child, managed milestone reports joined different probe samples
+  and omitted `worker.queue_wait`, and the 4+4 PIDs were placeholder Node
+  processes rather than real Pi workers. PI-150 remains blocked and PI-160 must
+  not start until those defects and native non-WSL Linux evidence are resolved.
   QG-004/QG-005 remain `Explicitly Waived / Accepted Risk`, with
   `realTurnVerified=false`.
 
@@ -147,16 +148,17 @@
 
 ## Follow-ups
 
-- Request planner re-review of `c7e7772..df1151b`. The five prior findings now
-  have direct final-product implementation and structured Windows/Linux
-  evidence; no source-only unit-test result is used as their release proof.
+- Planner re-review of `c7e7772..dc166a1` returned `Standards Pass / Spec Needs
+  Fix`. ASAR enumeration and RPM are closed; final packaged subagent dispatch,
+  a single Main-owned cold/warm timeline including zero-valued queue wait, and
+  real persistent-parent/ephemeral-child 4+4 pressure remain P1.
 - Do not start PI-160 or integrate `df1151b` while PI-150 remains blocked by the
   accepted platform evidence boundary. If the planner accepts the five fixes,
   keep PI-150 as the active frontier until the missing platform decision or
   evidence is resolved.
 - Keep missing macOS x64/arm64 artifact/runtime/resource/performance evidence as
-  a release blocker; do not promote a cross-platform release-ready or PI-150
-  `Done` conclusion without independent macOS execution.
+  `Deferred to PI-160 / Not Pass`; do not promote a final cross-platform release
+  without independent macOS execution, but do not use it to block PI-150.
 - Keep the lack of an independent native non-WSL Linux
   desktop/compositor/distribution run explicit. The WSL2/WSLg run qualifies the
   generated Linux artifacts and final process seam but does not erase that