You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Fixed
Require evaluatorq 1.30.0 or newer for the Responses helper API, check the minimum in CI, and type-check SDK/HTTP examples directly from markdown to catch scope and schema regressions.
Show paired orq/OpenAI Responses examples for models, agents and comparison jobs. Prefer orq for new code and existing orq imports; reuse OpenAI if it is already imported and orq is not. Document async and response-parsing differences.
Replace the generated CLI command inventory, group listing and inventory-generation script with progressive --help discovery. Retain task-specific examples, behavior caveats and invocation regression checks.
Use openai/gpt-6-luna in direct model invocation examples and model command defaults instead of older GPT models.
Model and agent invocation guidance now defaults to POST /v3/router/responses and orq responses create, using provider/model-id for models and agent/<key> for managed agents. Prefer Responses over Chat Completions and avoid v2 inference. Other inference interfaces require an explicit user request and must never be automatic error fallbacks.
Update invocation, observability, simulation and comparison examples to Responses request/output shapes, including streaming, structured output and previous_response_id continuation. Framework guidance explicitly selects Responses (including LangChain use_responses_api=True). Configuration, deployment, evaluator and telemetry APIs retain their own contracts.
Route evaluator-alignment recommendation/rewrite helpers and reconstructed judge calls through Responses, preserving structured verdicts and pricing input/output tokens.
Add a CI guard against non-Responses inference examples and runtime calls and local synthetic CLI routing probes for both models and agents. Document the CLI SSE decoding limitation and use SDK/curl for consuming streams on the same route. Contract checked against current Orq documentation, LangChain's Responses reference and installed CLI help on 2026-10-22; the reported EU-model failure has not been reproduced against a live agent.