All 295 distinct focused tests passed at 8bf7607a3f3b53db0c36364f54f57674c64ea2f1. Three bounded command invocations reused the exact already-listed test executable. This archive contains the closed focused stage only. The concurrently running full stage, its log and preflight capture are excluded; no full-test, strict, GUI-build or native result is claimed here.

Actual result

Batch	Passed	Failed / ignored	Filtered	Libtest duration
focused-batch01	107	0 / 0	982	81.86 s
focused-batch02	101	0 / 0	988	200.03 s
focused-batch03	87	0 / 0	1,002	14.69 s

The three name sets are disjoint and their exact union equals the predetermined 295-name selection. Each process contains all 1,089 desktop tests, so these three filtered counts remain distinct; there is no synthetic single-process summary with 794 filtered tests. focused.log is the byte-exact concatenation of the three raw batch logs. The aggregate receipt retains each actual summary and its batch receipt/log binding.

All five closed receipts (list, three batches, aggregate focused) identify the same source and test binary. Before/after captures retain the identical 611 source records and external inputs. Archival verification also rehashed the current 611 files, environment script and executable, checked exact command flags/name sets, unique actual outcomes, summaries, predecessor chains, every bound input hash, and raw concatenation. Verified results record the scope.

The omitted test executable is arcadia_studio-27db9628b266bf39.exe, 150,483,968 bytes, SHA-256 38b9ff204c9ecc590d0f8e1dee68e5c6b09ee65d189c0c1181e9570d3fe7c9bf. The focused aggregate receipt SHA-256 is 2a1a72b711bfd6e08a4d9d23deec9a2d3da074faabe2ac7b44089c515b031986.

Why recovery was required

The original single-command focused dispatch exceeded the Windows command-line limit before Cargo started. The preserved recovery provenance records parent terminal 35808, exit 1. Its original preflight capture is preserved exactly. No original focused log or receipt existed; their absence is not a failing product-test result. No test assertion or selection was changed to obtain this recovery.

batches.json divides the same selection into commands with conservative character counts 11,934, 11,893 and 10,149, each below the 12,000-character bound. Each uses cargo test -p oa-desktop --bin arcadia-studio --locked --offline -- --exact <that batch's names> --test-threads=1. The receipt records the actual argument array. Binary continuity checks refuse a changed executable before or after any batch.

The successful original LIST receipt SHA-256 is e2d9258afab904c7d0d9f3efbb3c3cc02511a33296c1698b3114b3d6b7a125a1. Its exact receipt/log and required bindings are retained here; the same LIST reference was already published with the comparator evidence at 727d2e0. Unrelated earlier preparation history is not recopied.

Preserved recipe and scope

Archive manifest binds 53 byte-identical copied originals totaling 2,504,310 bytes. This is the closed receipt dependency set, bounded recovery metadata, failed-start capture and local environment recipe. The original RECOVERY.md retains historical preparation wording; the closed observations above supersede only its unexecuted status. No raw record was edited. .gitattributes prevents line-ending normalization; publication must explicitly force-add ignored raw logs.

For a reproduction, fetch exact 8bf, recreate the documented Windows workspace/toolchain layout and matching successful LIST evidence, then use a fresh gate directory with run-batched.ps1 -Stage focused. The exact dispatch, source captures and original helper files are preserved. Do not invoke the old run.ps1 focused route, relabel this run, or overwrite archived receipts. Archived absolute paths identify this host; peers require their own resolved paths, matching inputs and fresh receipts. The retained environment script documents the actual local runtime/toolchain setup, not a global configuration change.

The runner also contains later all, clippy and build commands because they are part of the hash-bound recipe. Their presence is not execution evidence in this archive. No Cargo, test executable, compiler, native UI, source mutation, staging, commit or push was performed during archival.