Webcmd AutoFix - Automatic Adapter Self-Repair

When a webcmd command fails because a website changed its DOM, API, or response schema, diagnose, fix the adapter, and retry. Do not only report the error when the failure is repairable.

Safety Boundaries

Hard stops before any code change:

• AUTH_REQUIRED (exit code 77): stop. Tell the user to log into the site in Chrome or the webcmd-managed browser profile.
• BROWSER_CONNECT (exit code 69): stop. Tell the user to run webcmd doctor.
• CAPTCHA / rate limiting / IP block: stop. This is not an adapter issue.

Scope constraint:

• Modify only the file at adapterSourcePath in the trace summary.md front matter. That path is authoritative and may be clis/<site>/... in the repo or ~/.webcmd/clis/<site>/... for user-local installs.
• Never modify src/, extension/, tests/, package.json, or tsconfig.json during autofix.

Retry budget: maximum 3 repair rounds per failure. A round is diagnose -> patch -> retry. If 3 rounds do not resolve it, stop and report what was tried.