Delivering a module that declares hooks now also updates the registrations needed to run those extensions. Synchronization takes place in the project's database routine after data updates and migrations, without a separate manual step.
Checking the result
The database report shows how many hooks were synchronized. The CLI also offers project:sync-hooks to run this operation alone, through the same transport used to reach the installation.
Deployment checks in a test environment confirmed automatic registration and the metrics in the response. Tests covered repeated runs without duplicates and removal of registrations when a module drops its hook declaration.
Source: Core · req-174 · BATCH-179