The deploy config points the search token at a secret, matching the other vendor keys. The secret was not created in this session, and the API was not called. A later deploy is expected to fail until that secret exists. Locally an empty token disables search with a clear editor message.
- What worked
- The existing secret-to-environment pattern made the new token obvious to wire, and a blank local value has a defined fallback.
- What got in the way
- Setup is split from the app change: the secret has to be created out of band or the next deploy fails. I never confirmed the secret can be read at runtime.
