From 92f4c91088e79252aca76af3279b184da68e1eb7 Mon Sep 17 00:00:00 2001
From: brother7 <7brother7@gmail.com>
Date: Tue, 25 Aug 2026 18:06:01 +0800
Subject: [PATCH] docs(project): complete Pi user-entry fork task

---
 .../20260825-pi-user-entry-fork-4a7d9c21.md   | 46 +++++++++++++++++--
 1 file changed, 43 insertions(+), 3 deletions(-)

diff --git a/.project-docs/30-worklog/tasks/20260825-pi-user-entry-fork-4a7d9c21.md b/.project-docs/30-worklog/tasks/20260825-pi-user-entry-fork-4a7d9c21.md
index feadd73..f1a5c19 100644
--- a/.project-docs/30-worklog/tasks/20260825-pi-user-entry-fork-4a7d9c21.md
+++ b/.project-docs/30-worklog/tasks/20260825-pi-user-entry-fork-4a7d9c21.md
@@ -8,7 +8,7 @@
 - Worktree: D:\Datas\OthersProjects\makelore-pi-user-entry-fork-4a7d9c21
 - Base commit: 941b015330206af648f944183846ac2857468847
 - Owner: codex-root
-- Status: Verifying
+- Status: Done
 
 ## Scope
 
@@ -176,8 +176,48 @@ Gate result:
 - Focused Windows Electron Playwright — passed: `2` tests, including the
   same-Agent user-entry branch flow and source isolation.
 - `corepack pnpm run test:electron:windows` — passed: `2` files / `4` tests.
-- Formal Windows package, artifact closure, packaged UI/Main fork proof,
-  signing, fingerprint, and zero-residue evidence remain the active gate.
+- `corepack pnpm run package:win` — passed from clean code/proof candidate
+  `5031979ca9c46ed00597a36f6412e321f6fdcdcf`. Three earlier attempts stopped
+  only at GitHub's fixed uv download with `UND_ERR_CONNECT_TIMEOUT`; the
+  successful formal run downloaded both Windows architectures, rebuilt Vite,
+  staged `130` Pi production packages and `6` assets, and generated a new x64
+  NSIS without reusing an old installer.
+- `corepack pnpm run verify:publish-runtime` — passed with npm `11.6.2`.
+- `corepack pnpm run verify:artifact:win` — passed and bound the artifact to
+  clean verification HEAD `5031979`; Electron `43.4.0`, Node `24.18.1`,
+  Python/pip/sqlite/SSL, uv `0.10.0`, npm, msgpackr, Canvas native assets, and
+  Unicode copy all loaded from the final product. The repository does not
+  embed the optional `buildCommit` package field, so binding uses the
+  verifier's clean `verificationHead` contract rather than a fabricated
+  packaged field.
+- `corepack pnpm run verify:artifact:pi -- --samples 2` — passed: final
+  `app.asar`, Pi `0.84.2` CLI, all expected production packages/assets, five
+  unpacked native assets, four managed Skills, extension/subagent markers,
+  session persistence, local isolation, exit, and performance budgets were
+  verified. Its nested matrix correctly remains `partial-pass` for waived
+  real Provider and deferred non-Windows evidence.
+- `corepack pnpm run test:pi-subagent:packaged` — passed against the real final
+  app.asar Main and Renderer. The first proof attempt correctly found no fork
+  action on the just-settled live projection because it did not yet have a
+  durable source id; the harness now restarts the isolated product and
+  rehydrates the persisted binding before the installed-history action.
+  Final evidence: source + target count `2`, same Agent, distinct target
+  `piSessionId/sessionKey`, target worker `ready` / run `idle`, target hydrate
+  before the selected user entry, source unchanged, no prompt replay, one user
+  fork action, no assistant action, selected target, no runtime-unavailable or
+  permanent-recovering UI, and all worker/process/resource counters released.
+  The broader existing crash/protocol/resilience proof also remained green.
+- Pre-documentation installer evidence from `5031979`: `211891212` bytes,
+  SHA-256 `DE51AABA5A0F36810CE451328B45ACB7A03469E634DCBCCF52A8FA0608AA01BC`;
+  app.asar SHA-256
+  `4488C8C0F8653CE61438012A47BFCB9C7B8282967735AFA70C03EC45DE04674C`.
+  The post-documentation clean-HEAD artifact is rebuilt and fingerprinted in
+  the final handoff so generated evidence is not recursively embedded into
+  the artifact-producing commit.
+- Authenticode status is `NotSigned`; no signed publisher claim is made.
+- Final packaged proof tracked process residue was empty, and an independent
+  Windows process query found no Electron/Pi process associated with this
+  worktree.
 
 ## Follow-ups