When I copy my configs in a new machine i.e. building it from scratch, at the very beginning, I get prompted to install all plugins, regardless of their enabled status. If I press N, then I get asked to install zpack. I press Y, Then it correctly detects the enabled plugins, and only asks to install those.

It's probably a bug in the loading order for plugins.

Also, I get asked to install all (not ALL, the enabled ones) plugins whenever I push a lockfile to a new machine. Can the behavior be changed to what Lazy does i.e. only ask for the new ones?

Also, just a silent bug, if I have a plugin spec that combines simple and complex plugins like

return {
    "repo1/plugin1",
    {
        "repo2/plugin2",
        opts = { ... },
    },
}

the whole file is ignored. If I wrap all in {} it works. I'm fine by that since it sort of normalizes configs, but ignoring silently is not nice.

Sorry for all these issues, I just migrated to zpack from lazy.nvim, and wanted to make it easier for future migrators. My migrated config can be found at https://github.com/SinTan1729/my-nvim-config in case it makes it easier for you to test. Look at the migration branch.