plugin-core-builtin-migration

To migrate a renderer plugin to a core built-in capability, you transition it from an optional plugin to a stable, default internal feature by enforcing a single client root registration, setting manifest builtin/core flags, and cleaning up old entry points.

A core built-in migration for plugins is a process that upgrades optional renderer plugins into stable, default application capabilities, ensuring historical data migration, UI consistency, and a single root entry point across plugin pages.

To ensure historical data compatibility when upgrading a plugin to built-in, the migration process enforces backward-compatibility measures and idempotent migration, preventing legacy entry points from causing data loss or UI registration issues.

Yes, plugin core built-in migration supports idempotent operations and backward compatibility, ensuring that applying the migration multiple times yields the same result without breaking existing data or legacy plugin behaviors.

You should transition a plugin to a core built-in feature when it needs to become an non-disableable, stable default capability, requiring the consolidation of legacy entry points into a unified main workflow.

To deprecate old plugin entry points during a core built-in migration, you enforce a single client root registration and clean up legacy access paths, ensuring plugin panels and built-in capabilities do not display duplicate behaviors.