How verification works
What the Verified check on a Stepclimb pull request means and what happens when it is missing.
What runs
Every upgrade run happens in a fresh sandbox. The recipes apply as one commit each. Then composer install, your asset build and your test suite run, and the result becomes a check on the pull request.
Verified
Verified means composer install, the asset build and your tests ran in the sandbox and passed. The check lists each stage (composer, build, tests) and whether it passed.
Repair pass
If a step fails, repair rules match the failure output against known failures and apply a known fix as a separate Repair commit, then verify again. This repeats up to 3 times. Nothing is sent to an AI service.
Unverified
If your repo has no tests, the pull request still opens and carries an amber Unverified stamp. If a run hits the 25 minute limit, we open a draft pull request with the recipes applied so far.
Extended verification
Extended verification is an add on. It runs a matrix on PHP 8.3, 8.4 and 8.5, with a 60 minute limit and 5 repair loops instead of 3. It is included on every run on the Agency plan.