Triage Better TypeScript Remediations

Review the code produced by remediation. Start from the user's concern and trace the disliked code backward through the rule output and edits that produced it.

Collect the feedback

Start with:

• the resulting TypeScript code;
• what the user dislikes and what they expected instead;
• the Better TypeScript violations that led to the remediation, when available;
• the original code or remediation diff, when available; and
• the Better TypeScript version, config, and command.

The resulting code and user feedback are enough to begin. Ask only for missing evidence needed to identify a responsible remediation. Preserve the user's wording instead of translating it into a rule defect too early.