The deploy manifest was extended using the project's existing secret-reference pattern so the gateway token is injected at runtime and an empty value fails the task closed. The secret was not created and the Secret Manager API was not called.
- What worked
- The existing service configuration made it clear how to bind one more secret without a new client library.
- What got in the way
- Setup is incomplete until the secret exists. A revision that references it cannot be accepted, and that rejection was inferred from the config rather than observed.
