fix: verify packaged PI ownership boundaries

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

@@ -101,6 +101,23 @@
   exposed that pnpm `10.33.4` forwards the conventional `--` separator to the
   script; the parser is being corrected and the artifact will be rebuilt from
   the corrected commit before evidence is accepted.
+- The rebuilt `13efe84` Windows artifact passed the existing verifier. The new
+  verifier then found OpenCode-named files only inside the exact pinned
+  `@earendil-works/pi-ai/dist/providers` production package. Pi statically
+  imports those provider modules from `providers/all.js` and
+  `models.generated.js`; deleting them would corrupt the pinned closure. The
+  verifier is being narrowed to reject product-owned/legacy OpenCode resource
+  paths while reporting this upstream Pi package exception explicitly.
+- A one-sample verifier probe then showed the source filename
+  `makelore-runtime-v3.mjs` is not retained literally by the production bundle.
+  The final verifier now checks four stable extension contract markers inside
+  `app.asar`; executable extension/subagent behavior remains owned by
+  `smoke:pi:real`. With both corrections applied, the final-product verifier
+  probe passed against the existing unpacked Windows artifact, including exact
+  Pi `0.84.2`, Node `24.18.1`, 130 expected production packages, six assets,
+  four Skills, empty product-owned OpenCode paths, the explicit upstream Pi
+  exception list, empty development-path residue, and actual `get_state`/
+  lifecycle execution.
 
 ## Follow-ups