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:

• Human-action handoff: if a failure returns handoff.status === action_required, stop before trace collection or AutoFix. Give the user handoff.action and any Webcmd browser: or handoff.viewUrl link, then wait. Never request or enter credentials, passwords, or CAPTCHA answers. After the user reports done, run handoff.verifyCommand when present; verification must succeed before retrying. Without a verifier, inspect fresh browser state and verify the intended post-action state before any retry, especially for write commands.
• AUTH_REQUIRED (exit code 77): if a site login command exists, run webcmd <site> login, give its action_required instructions and any returned action_url or view_url to the user, and wait. Run the returned verify_command (normally webcmd <site> whoami); verification must succeed before retrying the original command. If no site login command exists, stop browser writes, hand the visible browser to the user, and wait. After they report done, take fresh browser state and use an available identity check or verify the intended post-action state before retrying. Their report alone is not verification. Never request, type, echo, store, or automate passwords, OTPs, recovery codes, cookies, or session secrets.
• BROWSER_CONNECT (exit code 69): stop. Tell the user to run webcmd doctor.
• CAPTCHA / raw-browser user takeover: stop automation. Follow the human-action handoff above when one is returned; otherwise let the user act in the visible browser. Verification must succeed before retrying. With no verifier, take fresh browser state and verify the intended post-action state before any retry. The user's report alone is not verification. CAPTCHA is not an adapter issue.
• 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 plugins/<site>/... in a plugin repo or ~/.webcmd/clis/<site>/... for user-local installs.
• Never modify src/, extension/, tests/, package.json, or tsconfig.json during autofix.