A project needs the API for the service its deployment will use. An API enabled in another project doesn't satisfy that requirement. Read the selected context and enable the named service, rather than copying an unrelated setup command from a previous environment.
The local adapter records which APIs are enabled and checks that record directly. It doesn't contact Google Cloud or establish production permissions. The surrounding account setup still needs an authorized operator and the appropriate billing association. Budget alerts also remain a separate concern: they report configured conditions and don't automatically implement a universal shutdown policy. Keep those responsibilities distinct in your handoff.
Enable the required API in the selected project.