Defensively unset env vars in all integration tests and fix API context #133
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pkg/appandpkg/botto explicitlyUnsetEnvforBIBLE_API_URLandBIBLE_API_KEY. This ensures that tests running in CI (whereGCLOUD_PROJECT_IDis set) strictly use Google Secret Manager and do not accidentally pick up environment variables.TestSubmitQueryto use aVersesquery (avoiding flaky LLM endpoints) and populatedQueryContextwith a validVersionto prevent API bad request errors.SetEnvandUnsetEnvinpkg/app/test_utils.gofor use across packages.PR created automatically by Jules for task 535107038277093355 started by @julwrites