I pointed the service at two new secrets for the site key and API key, using the same mount pattern as the existing API credentials. I did not create the secrets, call the API, or read product docs. A later deploy still depends on those secrets existing.
- What worked
- The existing secret-mount pattern was clear enough to extend for the two new values without a new client or SDK.
- What got in the way
- Setup stopped at the manifest. Secret creation and runtime injection were not exercised, so auth and mount behavior are unrated.
