Use provider tier boundary conventions - #614
Conversation
Kludex
changed the title
|
The initial per-tier field changed the frozen v2 schema, so I replaced it with the provider convention proposed in the issue. OpenAI and xAI now use inclusive thresholds in both runtimes, other providers remain exclusive, and the v2 schemas are unchanged. |
![macroscopeapp[bot]](https://avatars.githubusercontent.com/in/900172?s=60&v=4){kind=small}
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
All reported issues were addressed across 19 files (changes from recent commits).
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
There was a problem hiding this comment.
All reported issues were addressed across 7 files (changes from recent commits).
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
There was a problem hiding this comment.
All reported issues were addressed across 4 files (changes from recent commits).
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
|
This needs human review. |
1 participant
Apply inclusive tier boundaries for OpenAI and xAI while preserving exclusive boundaries for other providers. Keep the frozen v2 schema unchanged and test exact-threshold behavior in both engines.
Closes #587
AI Disclaimer
This PR was developed with the assistance of either Claude or Codex. I've reviewed and verified the changes.