Skip to content

feat(bot): configure production Jev service and API root - #452

Merged
AsperforMias merged 2 commits into
mainfrom
feat/jev-production-config-20261007
Oct 7, 2026
Merged

AsperforMias merged 2 commits into
mainfrom
feat/jev-production-config-20261007

Conversation

@AsperforMias

Copy link
Copy Markdown
Collaborator

Jev previously used a fixed endpoint and the production Bot selected the unconfigured LLM provider. Add an operator-configurable JEV_BASE_URL API root and select Jev in production, using the separately installed OPENROUTER_API_KEY Worker Secret. Local/staging keeps the LLM provider, and repository intent-label opt-ins retain their current values.

The classifier appends /alpha/decisions, requires HTTPS, rejects credentials/query/fragment/ambiguous URL syntax, and rejects redirects. Invalid configuration disables readiness and fails before any request. Update generated bindings, tests and operator documentation. No credentials are committed.

Validation: 274 Bot tests, root typecheck and lint, production Worker dry build, and independent read-only security review passed. A real OpenRouter Jev request with synthetic issue text selected bug at 0.91 using the configured endpoint. No GitHub label writes or repository setting changes were performed.

@ghfind-review ghfind-review Bot added the review: high ghfind author score; see https://ghfind.com label Oct 7, 2026
@AsperforMias
AsperforMias merged commit 7f06c5f into main Oct 7, 2026
13 checks passed

This branch is being deployed

1 in progress deployment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review: high ghfind author score; see https://ghfind.com

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant