AI Can't Fix What It Can't See: How cdk diagnose Enables Autonomous CDK Remediation Current Behavior vs. What We Want Today, when a CDK deployment fails through a pipeline, the remediation loop looks like this: Developer ──▶ Push code ──▶ Pipeline ──▶ CFN deploy ──▶ ❌ Fails │ ┌─────────────────────────────────────────────────────┘ │ ▼ Developer manually: 1. Opens pipeline UI 2. Finds the failed stage 3. Navigates to CloudFormation console 4. Locates the failed change set 5. Reads the CFN error message 6. Mentally translates CFN → CDK 7. Edits code, pushes, waits for pipeline again 🤖 Developer: "AI, fix this deployment for me" 🤖 AI: "Sure! I'll fix the CloudFormation template for you." 🤖 Developer: "...that's not how CDK works." The AI has no access to the error, no construct path, no source location. The best it can do is guess — and it guesses wrong, offering to edit CloudFormation YAML instead of your CDK source code. Totally useless.…