What’s fixed

• Re-running nibble:install no longer makes a site’s own edits look like Nibble’s. Install recorded the site’s current commit as the baseline nibble:upgrade and nibble:check compare against, so every file the site had touched since its last upgrade read as ours and changed in place. Only an upgrade moves that baseline now.
• nibble:build no longer asks a build for secrets it cannot have. It checked the master key, the mail credentials and the backup bucket — none of which exist while an image is being built — so the build failed on settings that only mean anything where the site runs. Those are checked at boot, where they can be true.

Changed

• Deploying scaffolds with kamal init, and Nibble changes only what is its own. A site is a Rails application, so it gets Kamal’s own config, secrets and hooks rather than copies Nibble maintained — the hooks in particular are Kamal’s examples and were going stale in our tree. What Nibble writes over the top is what a Nibble site cannot do without: the storage volume its database lives in, asset_path covering the images published from content/, SOLID_QUEUE_IN_PUMA, and SITE_URL.