Navigation/rename a49: strict, build and targeted Windows gates
Tested source: a49b0ec7ac4538a372139175386a881645c1a59e.
The actual receipts and logs confirm successful strict Clippy (--all-targets -- -D warnings), desktop binary build, 31 usage regressions, and the separately selected ignored rename timing test (1 passed, 0 failed, 0 ignored). The complete 577-input before/after manifests retained identical path membership, sizes and hashes. Archive verification also checked every one of those 577 files against the still-frozen source checkout. Raw gate/capture scripts, logs and receipts are preserved; verification.json records these checks and report.json inventories the evidence.
The full 951-pass suite belongs to 10bd711 and its existing report, not this a49 gate. The latter fixes test-only strict-lint findings; these targeted results do not relabel the earlier full suite or duplicate it.
Timing used the actual release1 bundle (30 reachable files, 78,414 source bytes), one warmup and five measured trials. Median synchronous app_sync was 1,161.9446ms (950.0872–1,594.9852ms); median Confirm update was 43.0291ms, worker Document preparation 377.0975ms and guarded commit 0.0067ms. The parent reports concurrent core compilation during this run; that contention is contextual information, not independently established by the isolated timing log. This is not an uncontended benchmark or evidence that the synchronous work is responsive. The fixture explicitly does not poll returned tasks or render; the short Confirm measurement is not end-to-end rename latency. Preserve the approximately 1.16-second synchronous phase as a performance limitation for subsequent native evaluation.
native-binary.json binds the current root debug executable for native handoff: 115,379,712 bytes, SHA256 D169A42692D2822A6E9DCD1E6181766F4A178E15AE2610763200DA9BBB814DDF. Its last-write timestamp falls inside the successful a49 build window; repeated archive-time hash reads were equal. This is a binding of the frozen build output to its checked build context, not native execution, release packaging or a cryptographic source attestation embedded in the binary. Recheck this hash immediately before native launch.
For reproduction, use an isolated checkout of a49 and the recorded commands/toolchain environment. Raw scripts retain the original local paths and refuse replacing their logs; substitute fresh local gate paths. Windows only. Native modal/focus/scroll/history workflows and Linux acceptance are not supplied by these logs. No compiler, test or native rerun occurred during this archive operation.