Setting the file. One moment.
Subchapter 24.55
scaffold/references/scaffold-healing-rules.mdMarkdown3 KBView on GitHub
Self-healing loop for scaffold validation failures. Contains error classification (FIXABLE vs BLOCKING) and scaffold-specific escalation and plan-change rules.
Also bundled
PHASEdeploy| Error Type | Class | Auto-Fix Strategy |
|---|
| Invalid property name | FIXABLE | Fix from schema |
| Syntax error (HCL/Bicep) | FIXABLE | Regenerate from references |
| Missing required property | FIXABLE | Call mcp_bicep_build_bicep for structured error, fix from diagnostics output |
| Wrong API version | FIXABLE | Call mcp_bicep_list_az_resource_types_for_provider with { providerNamespace: "..." } for latest GA. Fallback: reference file examples |
| Provider version conflict | FIXABLE | Update required_providers |
| Undeclared variable | FIXABLE | Add to variables.tf |
| Policy-blocked SKU | FIXABLE | Next-best from rejectedAlternatives[] |
| Circular dependency | FIXABLE | Break cycle — refactor module refs |
| Permission/RBAC insufficient | BLOCKING | Surface role + az role assignment create |
| State backend inaccessible | BLOCKING | Surface az storage account create |
| Region unsupported | BLOCKING | Suggest alternate regions (user decision) |
| Quota exhaustion (all tiers+regions) | PLAN_LEVEL_CHANGE | ⛔ See § PLAN_LEVEL_CHANGE |
| Quota exhaustion (single region) | PLAN_LEVEL_CHANGE | ⛔ Region pivot — skip quotaValidation.checkedRegions failures |
| Policy blocks service entirely | PLAN_LEVEL_CHANGE | ⛔ Map to rejectedAlternatives[] |
Classify Step 11 failures using the table above. FIXABLE: edit IaC → re-validate (max 3 before asking). Each attempt must be a different fix. BLOCKING: surface to user, halt.
⛔ After each FIXABLE auto-fix: call
mcp_bicep_build_bicepwith{ filePath: "infra/main.bicep" }to quick-check before re-dispatching the validate sub-agent. If errors remain, fix again — saves a sub-agent dispatch. Fallback:az bicep build.
⛔ After 3 attempts: summarize error pattern, propose specific next fix (never “I’ll try again” without naming the change), present options: “Yes, try that” (5 more) | “I have a suggestion” (apply user fix) | “Stop” (write
validationResult.status: "Failed"). Ask again every 5 thereafter.
⛔ Same error 3×: read iac-resources.md for docs. Present to user; stop auto-healing that pattern.
⛔ Service type or region changes require user re-approval — never silently rewrite IaC.
| Step | Action |
|---|---|
| 1. STOP | Never silently change service/region |
| 2. Update plan | prepare-plan.json: services[], naming.resources[], costEstimate, deployStrategy per prepare-schemas.ts |
| 3. Re-approve | “⚠️ Plan change: {old} → {new} (~${new}/mo). Approve? (Yes / Edit / Cancel)” |
| 4. Regenerate | New module files with correct names, delete stale, re-run self-review + validation |
| 5. Log | ScaffoldHealingAttempt with planLevelChange: true. Counts toward healing cap |
⛔ Artifact consistency: After any service/region/SKU change, update ALL upstream artifacts (
prepare-plan.json,scaffold-manifest.json,context.json, IaC files) — the plan MUST match deployed reality.