post-ship-mcp-verify

Automated post-deployment binary verification is handled by deploying, launching, and testing the application on a remote Windows test VM via WinRM. It executes CI gate checks, automated UI interaction, feature-specific checklists, and log analysis to validate the release candidate.

Verifying a VPNRouter release candidate involves a multi-phase validation process that checks CI gates, drives the UI using UIA, and scans application logs for errors. This ensures features like Zapret or TgProxy are fully operational before the release is finalized.

Yes, WinRM access to the target test machine and the availability of the GitHub CLI are required for asset retrieval to automatically test Windows binaries. These dependencies enable the automated deployment and validation of the release candidate.

Automated UI verification uses UIA to drive the deployed application, take screenshots, and confirm the interface renders correctly without exceptions. This process ensures the UI functions properly on the remote test VM.

Yes, you can automatically scan application logs for errors, crashes, or known failure patterns after deployment. The process automatically tails and analyzes logs on the remote test machine to prevent the release of broken binaries.

Limitations include the strict requirement for WinRM access to the remote Windows test VM and functional dependencies on PowerShell and GitHub CLI. Testing fails if the target machine is unreachable or if asset retrieval via GitHub CLI encounters network issues.