Stabilize real OpenRouter smoke acceptance #23
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/prolog-rlm!23
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/live-openrouter-smoke-stability"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #5 after the post-merge
mainlive job exposed an overly strict assertion.The production connectivity gate remains strict: the job still requires the repository secret, performs a real HTTPS request through the production SWI-Prolog provider path, requires a normalized non-empty assistant response, selected provider/model metadata, HTTP 200, response_received=true, and validates usage metadata when supplied.
The requested
PROLOG_RLM_OPENROUTER_OKtoken is now recorded as preferred evidence rather than a hard success condition. This matches #5's acceptance wording and avoids treating harmless routed-model phrasing as a connectivity failure.No fake provider, fixture, mock, HTTP interception, or fallback is introduced. No secret/header logging is added.