# Documentation Recipes Windows PASS — 2026-07-10

## Decision

**PASS.** All five repository-owned documentation recipe consumer projects built and completed their normal runtime smoke on Windows. The Render Verification snapshot route also completed separately with exit code `0`.

## Scope

| Proof | Result |
|---|---:|
| Recipe batches | 5 / 5 PASS |
| Governed recipes | 41 / 41 Build-verified |
| Normal runtime smokes | 5 / 5 PASS |
| Render snapshot smoke | PASS |
| Failed batches remaining | 0 |

The successful full command was:

```powershell
.\eng\tests\Run-NexamasUIDocumentationSnippetProof.ps1
```

The final terminal line was:

```text
Nexamas UI documentation snippet proof PASS. Batches=5; Recipes=41; RuntimeSmokes=5
```

The snapshot route was then executed directly through Batch 5 with `--snapshot-smoke`; it completed with exit code `0` at `2026-07-10T16:19:08.6309305Z`.

## Durable evidence

- [`documentation-snippet-proof-2026-07-10.json`](../_inventory/windows-proof/documentation-snippet-proof-2026-07-10.json)
- [`render-snapshot-smoke-proof-2026-07-10.json`](../_inventory/windows-proof/render-snapshot-smoke-proof-2026-07-10.json)

The generated `.artifacts/documentation-snippet-proof/` directory remains disposable and is not required in a clean source release. The normalized JSON records above preserve the accepted facts in source control.

## Runtime screenshots

These screenshots are supporting visual evidence only; the build/smoke exit results above are the acceptance authority.

- [Batch 1 runtime smoke](assets/documentation-recipe-windows-proof/batch1-runtime-smoke.png)
- [Batch 2 runtime smoke](assets/documentation-recipe-windows-proof/batch2-runtime-smoke.png)
- [Batch 3 runtime smoke](assets/documentation-recipe-windows-proof/batch3-runtime-smoke.png)

## Interpreting the earlier failed attempts

Two harness issues occurred before the final PASS:

1. Windows PowerShell 5.1 rejected JSON serialization of a generic object list after all five build/smoke steps. The runner was corrected to use a native PowerShell array.
2. A later combined `-IncludeSnapshotSmoke` rerun timed out in Batch 1 before reaching the snapshot step. The already-successful full five-batch run remained valid, and the snapshot route was then run directly and passed.

Neither issue represents a known Nexamas UI public API, recipe compilation, or Render Verification failure.

## Boundary

This proof establishes that the 41 governed documentation recipes compile and execute their smoke paths through public consumer routes. It does not claim exhaustive behavioral testing of every one of the 4,482 consumer-visible members or every possible input/state combination.