The duplicate-hook warning during migration is worth turning into an executable smoke test. A formatter or dependency hook can run twice even when both the standalone setup and the packaged plugin validate independently.
I would load the package from a directory containing spaces, run one harmless matching tool action, and have the hook write a single invocation record. Repeat after reload and after removing the standalone copy. That exercises quoting, resource resolution, and registration together, which a manifest-only check cannot establish before someone installs the published package.
Ahmet Özel
The duplicate-hook warning during migration is worth turning into an executable smoke test. A formatter or dependency hook can run twice even when both the standalone setup and the packaged plugin validate independently.
I would load the package from a directory containing spaces, run one harmless matching tool action, and have the hook write a single invocation record. Repeat after reload and after removing the standalone copy. That exercises quoting, resource resolution, and registration together, which a manifest-only check cannot establish before someone installs the published package.