repo-harness-check

To verify workflow readiness before a merge or release, you can run a verification entrypoint that executes workflow gates, task syncs, contract checks, and migration dry-runs. This ensures all necessary tasks are completed and the harness is ready for deployment.

Tasks-first contract validation is a process that ensures all predefined task contracts are checked and validated. Running these checks guarantees that your repository meets all required conditions and is fully ready for a merge or release.

Yes, you need repo-harness properly configured to run deployment readiness checks. The verification process depends on the harness environment to execute workflow gates, task validation, and migration dry-runs effectively.

A migration dry-run works by simulating migration tasks without applying actual changes to verify workflow readiness. It helps identify potential deployment issues and ensures all necessary contracts are validated before the final release.

The best way to validate task contracts for deployment readiness is to run a dedicated verification script that executes workflow gates and inspector checks. This validates all tasks-first contracts and confirms the repository is ready for deployment.

Repository workflow verification fails before a merge when necessary tasks are incomplete or tasks-first contracts are not validated. Running the verification checks identifies which specific workflow gates or contract validations are blocking deployment readiness.