CI fixes
When a check suite fails on an open PR, Pullfrog reads the failure logs, reproduces the failure with the CI commands, fixes it, and pushes to the PR branch.

The Fix CI failures card under Automations has two toggles:
| Toggle | Default | Applies to |
|---|---|---|
| Fix CI failures on Pullfrog's PRs | On | PRs that Pullfrog opened |
| Fix CI failures on non-Pullfrog PRs under review | Off | Every other open PR in the repository |
To fix a failure on any PR by hand, comment @pullfrog fix the failing check.
Skipped failures
Pullfrog starts no run for a failure in these cases:
- Bot commit. The failing commit was authored or committed by a bot, such as Dependabot or Renovate. This applies to PRs that Pullfrog did not open.
- Failing base branch. The latest completed check suite on the PR's base branch did not pass, so the failure is likely not the PR's.
- Recent attempt. Pullfrog already started a CI fix on the same PR within the last hour.
Unrelated failures
During the run, Pullfrog first confirms that the PR caused the failure. If the cause is unrelated, such as a flaky test, an infrastructure problem, or an existing bug, it makes no change and reports why.
The card's Custom instructions field applies whenever Pullfrog fixes CI:
Do not weaken assertions to make CI pass.
