modular-desktop-mvvm

Apply MVVM boundaries by separating views, view models, and services into reusable seams. Move decisions, labels, and progress logic into view models or services so that core behavior can be validated through focused tests without launching the UI.

Wire cancellable async orchestration directly in view models with duplicate-execution guards and recovery states. This preserves workflow routes and automation IDs while ensuring long-running commands do not block or trigger duplicate executions.

Prefer view-model and service tests that execute independently of the WPF visual tree. Validate critical bindings using narrow WPF test filters and run an MVVM compliance check to verify that logic remains decoupled from the view layer.

Refactor when desktop workstation changes become tightly coupled or resource-heavy. Inventory the nearest WPF artifacts, extract the smallest reusable seam, and shift operator-facing text and workflow state into shared services or view models.

Yes, it applies to both new and changed desktop screens, commands, and shell workflow states. It preserves existing routes, automation IDs, and operator-facing text while introducing behavior-preserving async orchestration and resource-conscious management.

Command orchestration needs explicit duplicate-execution guards wired during view-model construction. Without these guards, rapid operator interactions can trigger multiple overlapping async commands, causing resource contention and inconsistent workflow state.