AzuTear
1.9 KiB
Native Scanner Current-Build Live Smoke - 2026-07-11
Result
The required current-build, elevated development smoke passed against the
accepted English 16:9 Genshin Artifact inventory with a visible detail card.
The scanner remained read-only and ran with persist=false.
| Contract | Result |
|---|---|
| Run ID | 20260711-154827 |
| Requested / target / captured / clicked / queued | 50 / 50 / 50 / 50 / 50 |
| Processed / parsed / loaded | 50 / 50 / 50 |
| Pages | 2 |
| Review / processing errors | 0 / 0 |
| Store writes / persisted | 0 / false |
| Jobs / non-empty PNGs | 50 / 50 |
| Visual preflight | Genshin found, 16:9, 4x8 grid, visible Artifact inventory |
| Read-only probe | Detail fingerprint changed before the run |
The run wrote a complete native-scanner-run-timing-v1 record. Its
request-to-durable-results duration was 27,916 ms; final reconciliation
completed at 28,022 ms from the request start. That is approximately
1.78 Artifacts/s end-to-end for this exact smoke. Capture and processing are
reported separately; they are not added together.
Scope And Non-Claims
- This is an elevated development runtime smoke, not an elevated packaged executable acceptance.
- It proves the current 50-item functional/safety/reconciliation gate, not the three-Artifacts-per-second product target.
- It did not write to the local Artifact Store and did not modify Genshin.
- The raw run remains local runtime evidence. The generated workspace summary is intentionally disposable after this durable record is updated.
Follow-Up
The required scanner release gate is complete. The next approved actions are workspace cleanup, a coherent repository commit, and push of the current checkpoint. The remaining quality work is visually confirmed corpus growth, source-profile refresh, and a separate elevated packaged-runtime check only if that specific binary-runtime claim is needed.