Build and verification

Source and portable checks

dotnet run --project tools/SourceMaintenance -c Release -- --check .
dotnet run --project tools/SourceMaintenance -c Release -- --check-format .
python3 tests/metadata/test_xaml_sources.py
python3 tools/generate-property-adapters.py
git diff --exit-code -- src/
dotnet run --project tests/UnoDock.Core.Tests -c Release -- artifacts/core-tests

Formatting uses a pinned Roslyn tool and verifies executable-token preservation across supported parse configurations. Generated adapters and frozen original reference inventories must not be rewritten to make a regression pass.

Actual desktop hosts

dotnet build samples/UnoDock.Gallery -c Release -f net10.0-desktop \
  -p:UnoDockTargetFrameworks=net10.0-desktop \
  -p:UnoDockLibraryFrameworks=net10.0 -warnaserror

python3 tools/run-desktop-tests.py \
  --app samples/UnoDock.Gallery/bin/Release/net10.0-desktop/UnoDock.Gallery.dll \
  --output artifacts/runtime --selector fluent-navigator

To reproduce a CI desktop job (every group and its evidence gate, then all remaining suites), run the orchestrator; --only limits it to named groups:

python3 tools/run-ci-desktop.py \
  --app samples/UnoDock.Gallery/bin/Release/net10.0-desktop/UnoDock.Gallery.dll \
  --output artifacts/desktop --only fluent-navigator,docking-sizing

Use a fresh output directory. Linux headless runs require Xvfb; physical-input suites must run on a dedicated display with their explicit opt-in. A passing assertion list alone is insufficient when a native process subsequently fails or never completes.

Review scenes

UNODOCK_GALLERY_THEME=VS2010 UNODOCK_SCENARIO=float-both \
  dotnet samples/UnoDock.Gallery/bin/Release/net10.0-desktop/UnoDock.Gallery.dll

The Gallery opens a 1280×800 window at (40, 40) with a fixed layout and runs the scenario action after the first layout: docked, active-doc, active-tool, floating, float-tool, float-doc, float-both, autohide, context-doc, dropdown, tool-menu or navigator. Capture the window to compare platforms and themes side by side.

Browser protocol and runtime

node --test tests/browser/session.test.mjs
cd tests/browser
npm install --ignore-scripts --no-audit --no-fund
npx playwright install chromium
npx playwright test

The default runtime-test URL is http://127.0.0.1:8765/UnoDock/playground/. Build/serve the site first using getting started. Set UNODOCK_BASE_URL to exercise the same suite against a deployed site. Browser tests use fresh browser contexts and no automatic retries.

The suite requires an actual Uno adapter report and model-backed editors; a successful HTML-shell load is not counted as application startup. It exercises real popup windows, the native editor, return-on-close, popup-to-popup movement, stale leases, blocked-popup guidance, reload, and the drag-transfer protocol. Protocol unit tests independently exercise owner/lease invariants without a DOM.

The deployment pipeline retains screenshots, traces on failure, JSON/JUnit results, and a source revision. Browser-specific results do not replace desktop docking, chrome, XAML, or original compatibility acceptance.

Continuous integration

A single workflow, .github/workflows/ci.yml, runs on every pull request and on main:

Job	Runner	Contents
Checks	Linux	Source organization and formatting, generated adapters, evidence-gate unit tests, portable core tests, API scan and metadata comparison
Changes	Linux	For pull requests, detects documentation-only changes; those skip the desktop and package jobs
Desktop	Linux, Windows, macOS	One Gallery build per job. Linux and Windows run their focused suite groups (with evidence gates) and their remaining suites as two parallel jobs; Linux runs every remaining registered suite, Windows its acceptance set (Linux: Xvfb, XTEST, Openbox for floating chrome). Hosted macOS runners have a small virtual display, so macOS runs the focused groups. A suite that times out records its managed stacks when `dotnet-stack` is installed
NuGet packages	Windows	Uno and native WinUI package targets with symbols; builds and smoke-tests the native WinUI sample and uploads it, self-contained for x64 and ARM64, as `native-winui-sample`
Native WinUI Gallery	Windows	The Gallery's native WinUI head (Windows App SDK, built with MSBuild) running every registered self-test suite, split into two parallel shards (`run-desktop-tests.py --shard 1/2`, `2/2`). Each shard uploads `winui-gallery-<n>` with JUnit XML, logs and, per suite, the first-chance exceptions it raised (`exceptions-<suite>.log`), because WinUI ends the process on an exception in a dispatcher callback without reporting it
Browser	Linux	WebAssembly publish, documentation site and a minimal Playwright smoke set (`rendering`, `local-edit`; `UNODOCK_BROWSER_MINIMAL=1`). Pull requests publish without AOT; main publishes the AOT build it deploys. Run `npx playwright test` locally for every browser spec
Deploy/Verify Pages	Linux	`main` only: deploys the tested site and re-runs the browser smoke set against it

Run the CI workflow manually with full set (gh workflow run CI -f full=true) to execute every desktop suite on Windows (with a 1920x1080 display), macOS and Linux, and every browser spec. Do this before a release.

Each desktop job uploads one desktop-<OS>-<part> artifact with per-group JUnit XML, logs, captures, the runner's execution records and ci-desktop-summary.json. Reference-observation workflows run only when their probes change or on demand.