Use pre-scan first
If the source looks parser-hostile or performance-heavy, scan first instead of guessing blind.
Keep inputs clean
Avoid pitting extra wrappers or unstable edits on top of messy code when you do not need them.
Watch hot-path waste
Repeated scans or polling loops are signs that cleanup may be worth doing before runs.