docs: record final PI planner approval

.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 (PI-150 remains externally blocked by native non-WSL Linux evidence)
+- Status: Implementation and Spec Pass; PI-150 externally blocked by native non-WSL Linux evidence
 
 ## Scope
 
@@ -117,6 +117,12 @@
 - QG-004/QG-005 remain `Explicitly Waived / Accepted Risk`, with
   `realTurnVerified=false`; concurrency, credential isolation, and protocol
   compatibility against real Provider accounts are not claimed as Pass.
+- The planner's fourth fixed-range review closed both remaining P1 findings,
+  reported `Standards: Pass` and `Spec implementation review: Pass` with zero
+  new P0/P1/P2 findings, and independently reconfirmed the Windows packaged
+  delayed Provider milestone plus failure-injection/retry cleanup. The PI-150
+  gate itself remains `Blocked / Not Done` only because native non-WSL Linux
+  desktop/compositor evidence is still absent.
 
 ## Verification
 
@@ -170,14 +176,18 @@
   provider-shaped smoke issued six requests per protocol (distinct cold, warm,
   and abort-isolation paths); real Provider verification remains false by the
   explicit waiver.
+- Planner re-review of `ead9d1d..6d2232c` passed the fixed diff and
+  documentation gates. Its independent Windows packaged rerun measured cold
+  and warm Provider-first milestones at `127/129 ms`, both sourced from
+  `pi.assistant_message_start` and strictly later than `agent.start`; cleanup
+  unit tests passed `2/2`, and the real 4+4 injected-failure run retained the
+  same handle for a successful retry with every PID, counter, permit, dispatch,
+  lease, and Provider request returning to zero.
 
 ## Follow-ups
 
-- Request planner re-review of `ead9d1d..09841c8`. In addition to the earlier
+- Planner re-review is complete: Standards and Spec implementation both pass,
-  packaged subagent, correlated timeline, and real 4+4 fixes, this range makes
+  the two remaining P1 findings are closed, and no new finding was raised.
-  Provider first-event timing response-backed with delayed-response assertions
-  and makes pressure cleanup bounded, failure-safe, and retryable with both
-  unit and final-product fault-injection evidence.
 - Do not start PI-160 or integrate the candidate while PI-150 remains blocked
   by the native non-WSL Linux platform evidence boundary. If the planner finds
   no new implementation defect, keep PI-150 as the active frontier until that