failed, soft_locked, locked), on every audit-log row and on every file-integrity finding, asking the Forge AI what that one event means — a severity, a few sentences of plain English, and two to five ordered steps.
How to access: GuardForge > Login log, > Audit log, > File integrity.
Free/PRO: Free. What Pro adds is the automation — the hourly batch that reads everything unasked — not the ability to make the call.
Notes:
- 1 Forge credit per press. The price is read from
GUARDFORGE_Forge_API::CREDIT_COSTS(threat_analyze=> 1) and interpolated into the button label and the confirmation, never typed as a literal — a readme quoting a price the Worker does not charge is a mistake this suite has already made once. - The answer is stored against the content of the event rather than the row that carried it, so asking twice is free and tomorrow’s scan of the same unrepaired file does not charge again. A failed or unpaid call stores nothing.
- On a site with no licence the first press opens the free trial so there is a balance to spend; that one call sends the site address and the administrator e-mail from Settings → General, once, and never again.
- Each press sends the log row plus the site address, the WordPress version, the active-plugin count and the theme name, so the answer can be about this site. The prompt is rebuilt from the database, never from the form.