4.7 KiB
Details full and strict gate: closed 8bf evidence
The full desktop suite passed 1085 tests, zero failed, four ignored, with all 1089 exact listed names represented and no filtering. Libtest reported 939.74 seconds. The subsequent strict Clippy stage failed with seven diagnostics: Cargo exited 101; the outer PowerShell runner (parent terminal35767) exited 1. This is a closed failed combined gate. No GUI build or native acceptance follows.
Tested source: 8bf7607a3f3b53db0c36364f54f57674c64ea2f1. The published focused closure at7122f91 supplies the preceding list/295-test batch results and unchanged runner dependencies; they are linked rather than recopied here.
| Stage | Actual command | Result |
|---|---|---|
| all | cargo test -p oa-desktop --all-targets --locked --offline -- --test-threads=1 |
Cargo0;1085 passed/0 failed/4 ignored/0 filtered |
| clippy | cargo clippy -p oa-desktop -p oa-server --all-targets --locked --offline -- -D warnings |
Cargo101;seven diagnostics;wrapper1 |
Full execution ran from 12:37:09.9034836Z to12:53:04.9619280Z on2026-09-13; the939.74-second number is libtest duration, not the entire wrapper interval. Strict ran from13:02:54.4328749Z to13:06:43.6482921Z. Both stages retain identical before/after 611 source/config records, matching the published focused initial capture, with unchanged captured external inputs and no postflight failure.
Raw result and failure
Full log, full receipt, strict log, strict receipt, and all four before/after captures are byte-identical copies. Strict reports two collapsible-if findings, two manual-range-contains findings, two literal-Some unwrap findings, and one large-enum-variant finding. Exact messages and source locations are recorded in the raw strict log and verified results. No diagnostic was suppressed or replaced by a later passing run. The strict receipt's selectionValid flag concerns its runner checks; cargoExitCode101 still makes this stage fail.
The same test executable is bound before/after both stages:150483968 bytes, SHA-256 38b9ff204c9ecc590d0f8e1dee68e5c6b09ee65d189c0c1181e9570d3fe7c9bf. The executable is not copied into this archive. Archival verification compared closed manifests and receipt bindings; it did not rerun tests or rehash a subsequently changing product checkout.
Exact prerequisite mapping and reproduction scope
Source/reference mapping resolves all56 transitive gate-file dependencies: the eight originals included here and48 files at exact focused commit 7122f91671b56a5f23f1495ff2e78dcaec3661ed. Each linked file was compared against its current gate bytes, SHA-256 and that commit's Git blob. The separately linked environment script also matches its receipt hash and pinned Git blob. This preserves the full→focused→list and strict→full receipt/log chain without duplicating the earlier archive. The original all receipt SHA-256 is a31a32e6104fe5fd84d9e203ff3739fd9462923739a616d90729fd8994d3491d; strict raw-log SHA-256 is 02fe584d5fa87310e42738df91ae5f3494c4be966afe98d0ac300f3548af0f7f.
For offline inspection, combine the eight files under original/ with the mapped files from the pinned focused archive, preserving names and bytes. The referenced run-batched.ps1 contains the actual all/clippy commands. For new execution on another machine, fetch exact8bf, establish the matching Windows toolchain/dependency graph and fresh successful list/focused binary binding, then run all and clippy in separate stages into fresh evidence. Archived absolute paths identify this host; they do not assert that peers share its filesystem or executable. No archived receipt may be overwritten or relabelled as a new run.
Archive manifest binds eight copied originals totaling830629 bytes. .gitattributes prevents line-ending normalization. Raw .log files are Git-ignored by the repository and must be explicitly force-added by the publication owner. This preparation performed no Git mutation, compilation, test execution, native action or publication.
The prepared native8bf attempt2 recipe is superseded pending a corrected source and fresh matching acceptance gate; it must not be staged from this failed chain. Seven lint corrections and the separate arrangement-route correction are being handled outside this archive. No result for that new source is claimed here.