Refuse stale installed owner packages despite matching version metadata

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc

workplans/SAND-WP-0015-bwrap-runtime-and-private-state.md

@@ -268,7 +268,7 @@ with non-editable installation and recorded lock/source/package pins. Sand-boxer
 wheels now carry their profile and extension definitions, fixing a bwrap owner
 failure that source-checkout tests could hide. The trusted Messages binding can
 select the digest-pinned runtime without adding an API or profile override.
-`make check`: lint clean, 201 passed. Existing standalone workload builds remain
+`make check`: lint clean, 205 passed. Existing standalone workload builds remain
 supported. See docs/bwrap-runtime.md and rein's docs/owner-bootstrap.md.
 
 The project's `evidence/2026-09-09-owner-bootstrap.json` records the actual candidate
@@ -276,3 +276,8 @@ build and isolated installed-interpreter/CLI proof. T04 remains wait for accepte
 credential-to-owner delivery, current protected installation and Railiance placement,
 provider compatibility and G0. Source packaging does not reopen completed T01-T03,
 T05-T06, broaden the old CCRs or activate the previously installed 2.1.263 artifact.
+
+The first standalone candidate exposed a stale cached local wheel despite current
+Git metadata. Owner builds now refresh all local distributions and compare every
+installed package source/definition file with its tracked source; stale, missing or
+extra files refuse the build. Four content-conformance regressions cover that gap.