# Build and test ## Prerequisites - Windows x64, .NET SDK 10.0.402 with its approved .NET 10 patch roll-forward. - Windows SDK target 10.0.26100.0 and MAUI Windows workload manifest 10.0.110. - Microsoft Edge WebView2 Runtime to launch the native Blazor Hybrid Client. Step-02/Step-02A verification used .NET runtime 10.0.13, workload version 10.0.403 as listed by the installed SDK, and WebView2 Runtime 155.0.4283.62. The Client targets `net10.0-windows10.0.26100.0` and `win-x64`. Core, Application, UI, Components and both test projects target portable `net10.0`; unit/integration tests do not require MAUI or WebView2. ## Restore, build and launch From the repository root in PowerShell: ```powershell dotnet restore .\src\AutoForge.slnx dotnet build .\src\AutoForge.slnx --configuration Release --no-restore dotnet test .\src\AutoForge.slnx --configuration Release --no-build dotnet run --project .\src\AutoForge.Client\AutoForge.Client.csproj --configuration Release --framework net10.0-windows10.0.26100.0 ``` For an explicit Windows runtime pack restore or a direct native build: ```powershell dotnet restore .\src\AutoForge.Client\AutoForge.Client.csproj --runtime win-x64 dotnet build .\src\AutoForge.Client\AutoForge.Client.csproj --configuration Release --framework net10.0-windows10.0.26100.0 --no-restore ``` The Client is a native MAUI window containing the actual `AutoForge.UI` routes in a BlazorWebView. Profiles are imported explicitly into an in-memory catalog for the current Client process. No automotive driver, actual vehicle, database, backend, model or cloud account is required. ## Automated verification Run focused suites while developing: ```powershell dotnet test .\src\tests\AutoForge.UnitTests\AutoForge.UnitTests.csproj --configuration Release dotnet test .\src\tests\AutoForge.IntegrationTests\AutoForge.IntegrationTests.csproj --configuration Release ``` The unit suite covers existing Core/Application behavior, rendered generic components, profile invariants and strict codec behavior. The integration suite loads source-controlled synthetic fixtures through the real DI service/catalog, selects exact revisions, verifies semantic JSON round-trip and atomic failure, retains target-selection behavior, and renders the real profile UI. The project-graph test continues to enforce the seven-project reference boundaries. Fixtures are copied from `src/tests/AutoForge.IntegrationTests/Fixtures` and are never treated as real vehicle definitions. Step-02 worker verification covered 59 unit and 34 integration cases (93 total). Those historical runs did not include the two defects later assigned to Step-02A. Step-02A added focused pre-fix reproductions, then verified the corrected timestamp and applicability paths along with the full regression suites: 103 unit and 37 integration tests passed (140 total, zero failed/skipped). The seven-project Release build completed with zero warnings/errors. See the [Step-02 report](../prompts/Step-02-Report.md) for the original evidence and the [Step-02A report](../prompts/Step-02A-Report.md) for exact corrective commands and separate native observations. Manual orchestrator acceptance remains pending. ## Native profile smoke procedure Run the actual Windows Client and open `/vehicle-profiles`: 1. Paste `synthetic-truck-baseline.json` from the integration-test `Fixtures` folder and import it. Confirm the revision appears but is not auto-selected. 2. Select revision 1. Inspect module identities, the five declared capability states, `null`/unknown values, SYNTHETIC provenance and limitations. Export the selected revision and verify schema version/identity remain intact. 3. Paste/import `synthetic-truck-variant.json`; select revision 2 explicitly and verify its calibration identity differs while revision 1 remains unchanged. 4. Attempt duplicate import and malformed JSON; observe an error, unchanged catalog and unchanged selected profile. 5. Verify the alternate vehicle/custom role fixture can be imported and selected. 6. Confirm `/`, `/execution-targets` and an unmatched route still work, and that profile import/selection did not create or alter execution-target providers. 7. Verify a complete timestamp with `Z` or a signed offset imports and round-trips; a time-only timestamp shows its exact evidence JSON path and is not registered. 8. Verify module-scoped evidence with null hardware/software/firmware/calibration constraints stays null after export even when the module identities are known. A supplied conflicting identity must show an error without replacing the catalog entry or selected profile. Native route/interaction evidence is distinct from headless rendered tests. Worker evidence records the launch method and actual observed outcomes in the Step-02 and Step-02A reports. ## Schema and safety boundaries See the [schema-v1 guide](vehicle-profile-schema-v1.md) for all field, identity, unknown-value, capability, provenance and strict JSON rules. In brief: - Every v1 field is required; unknown optional facts are explicit JSON `null`. Unknown fields and duplicate/case-ambiguous properties are rejected. - Catalog selection requires exact `(profileIdentifier, revision)`. Duplicate imports do not replace entries, and failed parsing cannot partially register. - `publishedAt`/`retrievedAt` accept null or complete `YYYY-MM-DDTHH:mm:ss[.fraction](Z|+HH:mm|-HH:mm)` timestamps only. The exact fractional and offset limits and no-default policy are in the schema guide. - A null optional module identity in evidence is an absent constraint. Any supplied identity must match a known module value; an unknown target or mismatch is rejected without identity inference. - Imported profiles and capability/provenance statements are immutable metadata, not connection, compatibility, a working service or authorization. - Data remains in memory for the process only. JSON import/export does not write files or timestamps implicitly. - There is no simulation engine, diagnostic transport, calibration data editor, firmware image, operation executor, AI, persistent store or hardware adapter.