| name | no-code-repair-loop |
| description | Iterate deployment visibility failures using only no-code-safe actions and stop when source-code changes are required. |
No-Code Repair Loop
Use when
- Deployment exists but site is not visible.
- 404, build error, stale deployment, wrong project link, or protection wall is detected.
Safe action order
- Verify latest deployment URL.
- Inspect logs.
- Confirm Vercel scope/project match.
- Relink if mapping is wrong and exact project is known.
- Redeploy current main.
- Redeploy once with
--force.
- Verify URL again.
- Stop and report if code or env mutation is required.
Attempt limit
Maximum two production deploy attempts per run.