Native staging attempt 2: exact timestamp comparison
See RECOVERY.md for the closed original failure and the four passing exact-tick checks. This fresh recipe changes only the stage timestamp comparison among stage/launch/verifier code. The previous preparation results below remain historical; current closed GUI build evidence is recorded in timestamp-verification.json, but staging and native execution have not occurred here.
Scenario validation native preparation at b10b28c
Prepared for exact source b10b28cefd1d0794073ba241a0c8de9a83e85f68. This is a new recipe directory; old8bf native preparations and verifier 91b29e336b861d0c59c1c310556d737330871bc54aaed6d5e509bd33dce07945 remain unchanged. No package, working copy, profile, process or native output has been staged here.
The new verifier is SHA256 8306f4d4a1dde1c075a47994cd9d92738803c8b3b255b3e9907f0cb24749d91d. New comparator builds must bind this helper explicitly; an old comparator binding is not relabeled. Its simple read/hash/source-pair helpers remain usable independently of full native admission.
Admission and commands
The b10 gate recipe requires612 unchanged inputs, strict preflight, then the five regular stages. Strict preflight closed successfully with receipt SHA256 90597fab687350816777480daa4bd9649b6b4e550cfe381b2af0eede0f1cadde; this preparation read and verified that record. Regular LIST was still in progress when this recipe was prepared. No new LIST, focused, full, strict, GUI or native pass is claimed here.
Future native admission requires all of the following at the same b10 source:
- Fresh LIST:1095 exact unique names and its actual test executable.
- Focused:301 unique passes in reviewed batches107/101/93; actual per-process filtered988/994/1002. Exact batch receipts, raw byte concatenation, before/after captures and executable continuity are retained. No synthetic794-filtered aggregate process is invented.
- Full:1091 passes, four exact ignored names, no failures and zero filtered, matching the complete fresh1095-name inventory.
- Combined desktop/server all-targets Clippy with -D warnings, after full execution.
- GUI build with exact executable path, size, modification time and SHA256.
The verifier binds the reviewed regular run.ps1 (SHA9f3540a6984858448ad1f9bcf6e3326b6ec2b4b3ee897189876c56ebeaaea6cc), reviewed strict-preflight.ps1 (SHA152621fa4efe0a96adbeea43c4a08be21a63f5d4982846a9ad46de52ddbc725f), strict-preflight predecessor and complete regular receipt/raw-log/source-capture/toolchain/transitive-input chain. Stage copies .json/.ps1/.log/.md gate files, then revalidates the copied evidence. It rehashes current source/config before and after staging.
Only after parent confirms all required gates:
pwsh -NoProfile -File C:/Users/User/Documents/Git/ARCADIA-Studio/.local/scenario-validation-native-b10b28c-attempt2-20260913/stage.ps1 -SourcePin b10b28cefd1d0794073ba241a0c8de9a83e85f68
pwsh -NoProfile -File C:/Users/User/Documents/Git/ARCADIA-Studio/.local/scenario-validation-native-b10b28c-attempt2-20260913/launch.ps1 -Run 1
Stage defaults to the b10 gate and explicit verified toolchain libunwind.dll (SHAaa282fa47bb2c4e210cea5e470cdbdca58568f0be0bc73e404d86ab9cd95ef6a). Stage does not launch. Launch waits for normal close in a persistent shell, redirects logs and changes LOCALAPPDATA/PATH only on child ProcessStartInfo. It uses a private profile and unrelated working directory; Run2 requires the exact successful bound Run1 close and saved working files. No global environment or user profile is edited.
Fixtures and native review
Native run plan is parent-reviewed. Its sole copy correction trims the accidental trailing space in alias reporting_review. Comparator retargeting is copied unchanged from the same reviewed preparation. Stage puts both notes together in baseline and includes both original/copy hashes in the immutable input manifest, keeping their relative link valid. copy-provenance.json records original and copied hashes precisely.
The immutable6206-byte incident fixture and6132-byte typed service fixture are copied separately to baseline/working. Original preparation files are never opened or saved by this recipe. The existing core admission reference is copied unchanged; published service-core evidence supplies independent typed expected Projects. Core and dependency manifests are unchanged; current comparator dependency/runtime/source bindings still need independent preparation and execution, as explained in the linked note. Native form/draft/history observations are separate from core or comparator acceptance.
Preparation checks and changes
validate-scripts.ps1 parsed the four native scripts and passed21 targeted checks: pure source/name/binary guards; actual closed preflight binding; eight mutated preflight refusal controls; current gate copy-extension coverage; exact301-name107/101/93 partition; and frozen verifier hash. preparation-verification.json records these checks, with stage/launch/compiler flags false. These checks do not invoke complete five-stage admission or claim future stages passed.
recipe-changes.patch shows the actual three-script diff from the old8bf attempt2 recipe. Changes are exact source/counts, current static-input contract instead of obsolete finalization fields, fresh-list linkage instead of old recovery-list plan fields, strict predecessor and reviewed recipe binding, and copied/bound comparator note. Child launch mechanics, runtime protection, source rehashing, immutable baseline/working isolation and close/reopen rules remain intact.