docs(project): complete Pi provider recovery task

.project-docs/30-worklog/tasks/20260826-fix-pi-model-provider-8d4c2a71.md

@@ -8,7 +8,7 @@
 - Worktree: D:\Datas\OthersProjects\makelore-fix-pi-model-provider-8d4c2a71
 - Base commit: 9f05e2d7e194b3ae3507c019de53e437aaed9458
 - Owner: codex-root
-- Status: In Progress
+- Status: Ready for Integration
 
 ## Scope
 
@@ -127,6 +127,16 @@
 - This client correction cannot repair a persistently invalid Works backend
   account mapping. It makes one fresh-credential retry possible and attributes
   any continuing failure to the correct Provider boundary.
+- Implementation commit `a09826676e224a699f7ee6a05a931c14e5238aca`
+  produced the final Windows candidate. The clean-worktree artifact verifier
+  bound the installer to that exact `verificationHead`; this repository does
+  not embed the optional `buildCommit` field in packaged `package.json`.
+- Final Windows installer:
+  `D:\Datas\OthersProjects\makelore-fix-pi-model-provider-8d4c2a71\release\Makelore-2.0.0-win-x64.exe`;
+  `208162564` bytes; SHA-256
+  `A02F79FCD3273FB0B013450492DC788B6E5ED7BBC1007468FB83BE949B8CB30D`;
+  Authenticode `NotSigned`. Final `app.asar` SHA-256 is
+  `A8394D0F7324B27D2C95469ABD4E2A39C739EABCC6D8B41E1D65BA4B41FB9D39`.
 
 ## Verification
 
@@ -137,24 +147,42 @@
   addition; final projector file 12/12 passed.
 - `pnpm run typecheck`: passed.
 - Scoped ESLint: passed.
-- `pnpm test`: 181 functional files / 1540 passed / 2 skipped, plus REN-008
+- Clean-candidate `pnpm test`: 181 functional files / 1541 passed / 2 skipped,
-  pressure 1/1 passed. The final added projector assertion is covered by a
+  plus REN-008 pressure 1/1 passed.
-  subsequent isolated 12/12 pass and will be included in the clean-candidate
-  rerun.
 - `pnpm run lint:check`: 0 errors / 5 pre-existing warnings.
 - `pnpm run build:vite`: passed.
 - `pnpm run test:electron:windows`: 2 files / 4 tests passed.
-- A dirty-worktree staging/package smoke completed after the GitHub UV download
+- `pnpm run package:stage:win-x64` and clean-candidate electron-builder Windows
-  timed out twice; exact verified uv 0.10.0 binaries were reused from the prior
+  packaging passed. The external GitHub uv download timed out twice, so the
-  accepted Windows candidate. This smoke is not final artifact evidence because
+  exact verified uv `0.10.0` Windows binaries were reused from the immediately
-  packaged Git metadata still points at the base commit. A clean committed
+  preceding accepted candidate; no runtime version or source change was made.
-  rebuild and all artifact/final-ASAR verifiers remain required.
+- `pnpm run verify:publish-runtime`: passed with npm `11.6.2`.
+- `pnpm run verify:artifact:win`: passed from clean `a098266`; Electron
+  `43.4.0`, Node `24.18.1`, bundled Python/pip/sqlite/SSL, uv `0.10.0`, npm,
+  msgpackr, Canvas native assets, Unicode copy, final NSIS, and app.asar were
+  verified from the product artifact.
+- `pnpm run verify:artifact:pi -- --samples 2`: passed; exact Pi `0.84.2`, 130
+  production packages, six runtime assets, five unpacked native assets,
+  session reopen, prompt/settle, abort isolation, and clean exit were verified.
+  Cold/warm ready p95 was `705/659 ms`; exit p95 was `22 ms`.
+- `node scripts/run-pi-subagent-packaged-smoke.mjs`: passed from the final
+  executable and packaged app.asar Main. It covered the materialized extension,
+  real ephemeral read-only child, 4 persistent parent + 4 child live processes,
+  12-second prompt/compact confirmation uncertainty, late terminal settlement,
+  background lifecycle, intentional/unexpected/protocol-invalidated stops,
+  failure-safe cleanup, Composer unlock, and zero lingering tracked PIDs.
+- A read-only ASAR inspection confirmed the compiled Main contains both the
+  exact Works context classifier and the fixed Provider-auth projection. The
+  structured ignored reports are `release/pi-model-provider-artifact-win.json`,
+  `release/pi-model-provider-artifact-pi.json`, and
+  `release/pi-model-provider-final-product-proof.json`.
+- Real external Provider success remains unverified by explicit user waiver:
+  `realTurnVerified=false`. The final packaged loopback/fault-injection proof is
+  not recorded as a real Provider Pass. macOS and native non-WSL Linux were not
+  run by this task.
 
 ## Follow-ups
 
-- Commit the implementation candidate, rebuild from that clean commit, and run
-  Windows artifact/Pi/final-ASAR verification with a self-bound structured
-  report before completing this feature task.
 - After feature acceptance, use a separate Integration Gate to resolve the old
   `main` integration lock, reconcile canonical project memory, and merge. Do
   not conflate this feature branch with integration ownership.