# Recipe Verification Batch 2

This repository-owned consumer sample prepares the second recipe build-verification batch for Nexamas UI documentation.

It covers these recipe IDs in a public-API-only .NET Framework 4.8 WinForms consumer context:

- `Feedback.StatusBanner`
- `Feedback.ValidationMessage`
- `Feedback.EmptyState`
- `Feedback.Progress`
- `Button.Split.Basic`
- `Input.ComboBox.Basic`
- `Input.Slider.Basic`
- `Surface.GroupBox.Basic`
- `Surface.Expander.Basic`
- `Surface.Accordion.Basic`
- `Surface.TileBox.Basic`
- `Navigation.Tabs.Basic`
- `Navigation.Breadcrumb.Basic`
- `Navigation.Pagination.Basic`
- `Navigation.CommandBar.Basic`
- `DataGrid.BasicRows`

The sample deliberately uses `ProjectReference` to the repository source. This is a useful first compile proof, but the stronger proof remains a packed consumer build against the generated `.nupkg`.

## Build from repository root

```powershell
msbuild .\samples\RecipeVerification.Batch2\Nexamas.UI.RecipeVerification.Batch2.vbproj /t:Restore,Build /p:Configuration=Release /p:Platform=x64
```

## Status meaning

A successful build can be recorded as `Project-reference consumer build PASS` in `docs/recipes/build-verification-ledger.md`.

Do not mark these recipes as `Showcase-ready` until each covered recipe also has a matching live Showcase scene and code panel.


## Recorded Windows verification

Maintainer-reported result on 2026-07-08:

```text
196 Warning(s)
0 Error(s)
Passed: 15, Skipped: 0, Failed: 0
```

This promotes the covered recipe IDs to `Build-verified` in `docs/recipes/build-verification-ledger.md`. It does not promote them to `Showcase-ready`.


## Runtime smoke

After a successful Release/x64 build, verify application/window creation, first layout, form display, and disposal:

```powershell
.\samples\RecipeVerification.Batch2\bin\x64\Release\Nexamas.UI.RecipeVerification.Batch2.exe --smoke
```

The smoke mode closes automatically. Use `eng/tests/Run-NexamasUIDocumentationSnippetProof.ps1` to build and smoke all five batches together.

## Visual host layout

The interactive host now separates overview, feedback, inputs, surfaces, navigation, and DataGrid into six `MASApplicationWindow.Pages` routes. Tall surfaces receive dedicated height intent and scroll inside the official application workspace instead of being compressed into one canvas.

The `--smoke` route now traverses every registered page in this batch before the form closes automatically.