[Epic] Expand automated validation for the control-plane product #21

Problem

The planned product surface is much larger than the current test suite, so dotPilot needs a tracked validation epic before implementation starts landing.

Scope

• Track unit, integration, Orleans, UI, local-runtime, CI, and packaging validation growth
• Keep the repo on the existing real validation path instead of adding fake smoke checks

Out of scope

• Replacing the current validation workflow with non-repo commands
• Weakening quality gates to make the backlog easier to ship

Planned child issues

• Add unit and integration tests for contracts, adapters, and persistence
• Add Orleans integration tests for orchestration and checkpoint-resume
• Expand Uno.UITests for the workbench and operator flows
• Add local runtime smoke tests
• Update CI and packaging validation for the expanded desktop product surface

Definition of Done

• The validation issues exist and reference this epic
• The epic preserves the current repo policy of real automated verification

Verification

• Child issues reference this epic
• The epic is concrete enough to drive test growth alongside implementation