How IrmaWP verifies WordPress changes

A chat reply is not proof that WordPress changed. IrmaWP keeps the requested work, operation status and available verification evidence separate. This page explains the checks we test and the limits that remain.

The evidence below comes from automated regression tests run on October 7, 2026: 24 tests passed, with 224 assertions. These are application tests using controlled fixtures and mocked connections. They are not live hosting benchmarks, customer results or a guarantee that every site will behave the same way.

Updates: verify the installed version

An update offer disappearing does not prove the requested version is installed. Our update checks distinguish an exact installed version from an unavailable offer. A completed no-op is different from a write that failed or never started. The regression checks cover current-version outcomes so a retry does not needlessly repeat completed work.

For your site, review the target plugin or theme, version and operation result. If execution or verification is uncertain, inspect the site before retrying. A successful HTTP response by itself is insufficient evidence. See update management.

Design: review the rendered result

The design-review tests cover review requests and their recorded findings. Visual review needs the page, viewport and reference; generating an artifact or completing an operation does not establish a pixel-perfect match. A page may need another revision, and forms, responsive behavior and application logic require their own checks.

Use a clear screenshot or design reference, name the page builder and specify what must stay unchanged. Review desktop and mobile. Give the operation time to finish, then check its verification result instead of relying on the wording of the reply. Write a useful design brief.

Recovery: undo the affected files, not unrelated data

The scoped-recovery tests cover plugin and theme file journals, unavailable independent endpoints, refusal handling and unverified writes. A required recovery guard is not the same as a completed receipt. Disabled or conflicting recovery evidence must not be presented as a working Undo.

Supported scoped recovery restores the affected files. It does not import a full-site database and overwrite new posts, orders or unrelated work. Database restore is a separate, explicit decision. File recovery also cannot reverse a plugin’s database migrations. Read the file-versus-database guide.

Approval and access

Approval requirements depend on your role, the site’s policy and the operation. Some supported work may proceed under an approved automation policy; other work waits for a person or is refused. MCP is the connection protocol, not a blanket safety promise. Review team approvals before authorizing writes.

What this evidence does not establish

Passing these tests does not certify every host, plugin combination, recovery artifact or AI answer. Demo screenshots use labeled sample data. Our agency’s experience is separate from SaaS customer adoption. For a rollout, test the workflow on an isolated site and verify the actual result. Contact us if you need help interpreting an operation’s evidence.