docs(project): qualify Pi session reopen installer

.project-docs/30-worklog/tasks/20260825-pi-session-reopen-installer-8c3e7a91.md

@@ -8,7 +8,7 @@
 - Worktree: D:\Datas\OthersProjects\makelore-pi-session-reopen-installer-8c3e7a91
 - Base commit: e74b59a67479a32619a9e3dbef476a65a6ad071f
 - Owner: codex-root
-- Status: Implementation
+- Status: Ready for Integration
 
 ## Scope
 
@@ -87,7 +87,18 @@
   fresh `PiSessionRegistry`: the persisted binding is reused without invoking
   the new-session key generator, while the original first-open path still
   creates exactly one binding.
-- Windows packaging and final artifact verification remain in progress.
+- Committed the reviewed repair as
+  `862d1b6d921f421ff0eaeb2f1df16274445dbc01` and built the Windows x64
+  product from that clean commit.
+- Generated the NSIS installer
+  `release/Makelore-2.0.0-win-x64.exe`. The final unpacked app runs Main from
+  `app.asar`, loads the packaged Pi `0.84.2` production closure, and passes the
+  existing managed extension/subagent/Host-proxy product proof.
+- Ran a task-local, non-retained packaged restart proof against an isolated copy
+  of the exact user Conversation and Pi session reported in the incident. Two
+  separate launches of the final executable each hydrated 18 Conversation
+  nodes with worker `ready`, run `idle`, and no public error. The source
+  project/session and installed application were not modified.
 
 ## Verification
 
@@ -105,11 +116,51 @@
 - `corepack pnpm run test:electron:windows`: 2 files / 4 tests passed.
 - `git diff --check`, task ownership drift, and required project-doc checks:
   passed before packaging.
+- `corepack pnpm run package:win`: passed from clean candidate `862d1b6`;
+  staged 130 Windows x64 Pi production packages and six runtime assets, then
+  produced the NSIS and blockmap.
+- Final installer: 211,888,196 bytes; SHA-256
+  `00B474114B5B398DCA8374238A5C144E69A17E9419B21615143FCD59E4C62658`.
+  Blockmap SHA-256:
+  `AD2F44E242BF0A6C2C9C08FD3E068DBF4E2431D62663A93188E95D3DCA388439`.
+  Final `app.asar` SHA-256:
+  `6F5B95F653ED346DD1616C403584EC61F23A2AE6907DB47D27FE28EE5DA4AF09`.
+- `corepack pnpm run verify:publish-runtime`: passed; bundled npm `11.6.2`.
+- `corepack pnpm run verify:artifact:win`: passed and bound the artifact to
+  commit `862d1b6`; Electron `43.4.0` / Node `24.18.1`, bundled Python/uv/npm,
+  msgpackr, and Canvas native assets loaded from the final product.
+- `corepack pnpm run verify:artifact:pi -- --samples 2`: passed; Pi `0.84.2`,
+  CLI, all 130 expected packages, six runtime assets, five unpacked native
+  assets, managed Skills, extension markers, session persistence, local worker
+  overlap/abort isolation, cleanup, and cold/warm budgets were verified. The
+  nested report correctly remains `partial-pass` for the pre-existing external
+  platform and real-Provider evidence boundaries.
+- `corepack pnpm run test:pi-subagent:packaged`: passed from final
+  `win-unpacked/Makelore.exe`. Main executed from `app.asar`; cold/warm managed
+  turns, a real packaged parent and ephemeral child, 4+4 process pressure,
+  authenticated Host-proxy loopback, failure-safe cleanup/retry, UI
+  interactivity, token non-disclosure, and zero released resource counters all
+  passed with `realTurnVerified=false`.
+- Final persisted-session packaged proof: two independent launches both
+  returned worker `ready`, run `idle`, 18 hydrated nodes, and no error. The
+  temporary verifier and isolated user-data copy were removed after the run.
+- Final Windows process query found zero residual processes from this worktree.
+- The local installer has no Authenticode signature (`NotSigned`); no signed
+  release claim is made and Windows may show a publisher/SmartScreen warning.
 
 ## Follow-ups
 
-- None recorded.
+- The unsupported-thinking-level / indefinite `正在提交…` issue remains a
+  separately diagnosed defect. This package does not claim that unimplemented
+  fix.
+- Real external Provider validation remains explicitly waived accepted risk,
+  with `realTurnVerified=false`; packaged loopback evidence is not a real
+  Provider Pass.
+- macOS and native non-WSL Linux release evidence status is unchanged by this
+  Windows-only repair.
 
 ## Promotion Candidates
 
-- None recorded.
+- Promote the invariant that generation-1 worker open must consume an existing
+  Main Registry binding, plus the packaged restart/re-entry regression, into
+  the Pi release runbook when the cumulative Pi branch is integrated.