Everything below comes from the project’s own gap analysis and verification reports. These are intentions and open items — not promises, and not scheduled: no dates are attached to any of them. If it is not in a released changelog, it does not exist yet.
Capabilities reviewed during the 1.3.0 parity analysis and consciously deferred, each for a stated reason — most often that doing them safely needs their own review or a testbed we do not yet have:
| Item | Why it waits |
|---|---|
| Form writing (create/update forms and fields) | Read-only inspector parity shipped in 1.3.0. Write-side form surgery — especially WPForms’ JSON model — needs its own safety review. |
| ACF value writes | Per-field-type validation is a project of its own; reading ships, writing waits. |
| Theme Builder display conditions | Writing Elementor Pro’s condition registry without Elementor Pro in the testbed would be an unverifiable implementation. The project does not ship unverifiable features. |
| Dynamic tags (list / inspect / bind) | Elementor-Pro-centric and unverifiable in the free testbed. |
| Icon library, SVG and Lottie import/inspection | Media-import sanitisation review is its own piece of work. |
| SEO page inventory & internal-link suggestions | Per-page audit and inspection cover the immediate need; site-wide analysis is a later addition. |
| Dedicated WooCommerce page builders (single product, archive, cart, checkout, account) | The generic builder and theme-builder tools can construct such pages today; dedicated builders are a refinement, not a gap in capability. |
| Build-sessions admin screen | Sessions are fully visible through the tools and the audit log; a dedicated wp-admin screen is polish, scheduled behind capability work. |
| Agent-guide tool | Workflow guidance is currently carried by the three MCP prompts and tool descriptions. |
| Elementor add-on (UAEL) inspector family | A third-party niche; its widgets already surface through the live widget registry tools. |
Existing features whose runtime verification is still outstanding. They are implemented; they are not claimed as proven:
_meta, not yet with the shipping client itself.Designs used by other products that LIYANS MCP rejects on principle. These are not gaps and will not be “fixed”: