Diagnosis and AI

When a run ends restored, failed to restore or regressed, Update Doctor builds an evidence bundle: the fatal error, new log lines, failing pages, changed files, data changes, version jump, requirements and the active plugins.

• Rules always run. They pick a likely cause (an update bug, a PHP version problem, a plugin conflict, a theme conflict, a missing asset, a data migration, the environment, or unknown), name the suspect and suggest actions. No account or network access is needed.
• AI runs only if you set it up, and only on those regressions. It uses WordPress’s AI Client with the provider you add under Settings > Connectors. If none is connected, you get the rules diagnosis alone.
• The AI never executes anything. It returns JSON checked against a fixed schema. It can only suggest actions from a fixed list, for items that exist on your site, and everything it suggests waits in the approval queue.
• A monthly token budget applies (default 200,000, 0 for no limit). Token use is recorded per call.
• Evidence is redacted first. Secrets and personal data are removed: database credentials, keys and salts, email addresses, login cookies, nonces, bearer tokens, API-key-like strings and IP addresses. Absolute paths are shortened. Page bodies are never sent. A finding may quote a short string such as a raw shortcode, a marker you configured, or a missing file URL.

Two more AI features run only when you press a button: a changelog summary in the risk view, and a summary paragraph on a client report.