🧭 Guided tour

1. Start with the Standard Ten

Every live plugin received the same ten capability probes: six Core factual questions, multi-select, true/false, fill-in, and ordering. The six-question Core page is also the controlled runtime surface.

Read every canonical question and acceptance rule.

2. Visit an isolated demo

Each subsite runs Twenty Twenty-Five and exactly one roster plugin. Open its benchmark, Core Six measurement surface, and signature demo from the home table. A successful row means a browser completed a native attempt and observed the plugin’s result—not merely that a shortcode rendered.

3. Read the matrix literally

• ok: demonstrated in the installed free tier.
• unsupported: unavailable or not demonstrable in that free build.
• pro-gated: explicitly exposed or documented as paid.

Unsupported does not mean the vendor has never shipped the feature; it means this benchmark does not credit it to the installed free package.

4. Compare runtime weight

The Core Six pages were measured logged out in cache-disabled Chromium after network idle. Requests, JavaScript, CSS, transfer bytes, jQuery presence, and top-document DOM nodes come from the browser Performance API.

5. Enter the coexistence lab

The lab keeps all ten plugins active on one subsite and embeds the ten isolated Core Six surfaces in one browser load. It records console, PHP log, admin-menu, and plugin-attribution findings rather than declaring “compatible” from activation alone.

6. Follow the evidence

The evidence index exposes the JSON snapshots behind every mutable number. Documentation-tier commercial and SaaS products are discussed separately because no paid or nulled code was installed.