# Provisional fixture check with a pre-existing CLI

The identified CLI executed both inputs without writing them. Missing include
returned 3 (disk refusal), and the complete fixture returned 0 with five warnings.
Each included SA function has overlapping allocation and behavior-context
warnings at its actual raw declaration range: 171..489 and 491..701.

This is fixture preparation using CLI SHA bad169f8be78dcfa74b32714569c886dd2132727080684fc2ba618d5822e3559;
this record does not bind that binary to the current diagnostic implementation.
The current identified CLI/build and native GUI still need verification.

The private helper incorrectly expected missing-include exit 1, so it returned
failure despite collecting the correct disk-refusal result. Its expectation was
corrected to 3 for future runs; these original receipts remain unchanged.
The preceding historical-cli-fixture-preflight failed to load its Windows DLL
dependencies before producing output (0xC0000135). Attempt 2 used the established
toolchain environment. No application failure or native acceptance is inferred.