qiaomu-opencli-autofix

To fix OpenCLI adapter failures from DOM or API changes, run OPENCLI_DIAGNOSTIC=1 to diagnose the issue. The tool identifies whether the failure is caused by selector changes, API schema shifts, or auth timeouts, then applies bounded patches directly to the authoritative adapter source path.

Diagnosing a broken OpenCLI command involves running the command with OPENCLI_DIAGNOSTIC enabled and reading the RepairContext. This mechanism identifies the specific failure type—DOM selectors, API responses, or auth issues—before attempting any bounded patching.

OpenCLI adapter patching allows up to three safe, bounded repair rounds. After each patch modifies the authoritative adapter location, it requires a subsequent re-test of the command to verify the fix before proceeding or stopping at explicit stop conditions.

You should avoid patching an OpenCLI adapter when the failure falls outside the scope of selector, API schema, or auth issues. The diagnostic workflow includes explicit stop conditions and guidance on when not to patch if the error is unresolvable within three repair rounds.

No, OpenCLI adapter repair enforces that patches modify only the authoritative adapter location specified in RepairContext.adapter.sourcePath. This strict boundary ensures minimal, safe changes without affecting external files or system configurations.