No Migration Needed

1{
2  "schemaVersion": 1,
3  "description": "Nothing-to-move verdicts, in two tiers.\n\n`hints[]` — a flat slug lookup for plugins that need no data migration at all, where a full profile would be dead weight. A hit here is strong evidence the agent confirms at classification, never the answer by itself. Without this list, a caching or SMTP plugin whose data we cannot read is reported as potential data loss — which is both wrong and alarming. Keyed by plugin directory slug; a slug with a full profile may not appear here.\n\n`capabilities[]` — the human-signed per-capability register, for PROFILED plugins the slug list cannot reach. This is the only way a profiled capability reaches the no-need-to-migrate status (basis: decision); without it a decided capability re-lands as pending on every run. It is not an impossibility verdict (that is requires-development.json) — it says the outcome exists in Wix or was never data — but it is still a decision about what the customer does not get, so it carries decidedBy + decidedOn and validation rejects an unsigned entry. Mutually exclusive with requires-development.json and capabilities-pending-decision.json, and rejected once a Wix target entity claims the capability.\n\n`coreCovered[]` — plugins whose data the adapter's core reader already moves (WooCommerce via wc/v3). The per-plugin row is migration-planned with basis core-reader only when this run read one of `coreNamespaces`; otherwise the plugin stays pending. It adds no capability decision: the core entities are their own census rows.\n\n`toolkitPlugins[]` — this skill's own plugins on the source site. Left out of the plugin report and counted in statusInvariant.toolkitExcluded. Signed.",