Declared hooks could end up shipping the `#!/bin/true` placeholder even when a part had already generated a real hook in `snap/hooks/<name>`. The regression came from creating fallback hook files before built hooks were materialized into `meta/hooks`. - **What changed** - `Package.write_metadata()` now provisions built hooks into each prime directory before `setup_assets(..., copy_hooks_and_gui=False)` runs. - This keeps declared hook metadata intact while ensuring `_ensure_hook()` sees the real hook file and does not create a stub over that path. - **Why this fixes the bug** - The previous order was: 1. declare hooks 2. create stub in `meta/hooks/<name>` 3. try to provision built hook with `overwrite=False` - Because the stub already existed, the built hook was skipped. - The new order makes the real built hook exist first, so the fallback stub path is never taken for that hook. - **Regression coverage** - Added service-level coverage for the `write_metadata()` ordering in both snap and component flows. - Added a hook-level regression showing that a provisioned built hook prevents placeholder creation for a declared hook. ```python # Before setup_assets(..., copy_hooks_and_gui=False) provision_hooks(prime_dir, overwrite=False) # After provision_hooks(prime_dir, overwrite=False) setup_assets(..., copy_hooks_and_gui=False) ```