# Pre13 Stage0 Gate Decisions

## Scope and Baseline

- DUT repository baseline: `9028b92343ec7f5bbc1b07477b8d4a669c436955`.
- Clean tests-dev baseline: `ce03c283e6e2cb8f1b69c8eff21f7d06098a4fbe`.
- Stage0 was a planning gate. Infrastructure fixes made in tests-dev are not DUT changes.
- The complete Stage0 runner result is `FAIL`, not `PASS`, because the H01 DTrace probe failed.

## Gate A: ROOT-NONDIR

Status: `READY`.

The baseline incorrectly mounts an image whose root NID points to a regular file. Pre13 freezes the expected rejection errno as `EINTEGRITY`. H04 may proceed with the dedicated fixture and its required targeted validation.

## Gate B: ZERO-RUN

Status: `BLOCKED/STOP`.

The analysis covered 1,360 legal states and found no zero-progress state. H07 must be recorded as a no-op and must not be implemented in Pre13.

## Gate C: Map Tuple Oracle

Status: `BLOCKED/STOP`.

The oracle reliably covers only 26 plain, inline, and hole tuples. It does not cover chunk, multidevice, bounds, or overflow behavior. H01a, H01b, and H01c must not be implemented in Pre13.

## Gate D: Comparator

Status: `READY`.

The Python comparator corpus passed all 11,562 cases. The independent C harness passed all 1,048,576 cases. H03 may proceed within the planned boundaries and with its targeted validation.

## Gate E: Device Options

Status: incomplete and non-gating.

The `device.N` runtime probe was not completed. Pre13 makes no runtime behavior claim from this gate.

## Integrity and Cleanup

- Stage0 must not be described as an overall pass.
- Stage0-owned QEMU, SSH, ports, overlays, and temporary runtime resources were cleaned up.
- The guard VM and read-only base image were not modified.
- The pre-existing dirty tests-dev working tree was unchanged.
- Tests-dev runner and infrastructure repairs are evidence support only; they are not EROFS DUT fixes.
