archie-core bead 7zu3 was mitigated, not fixed: the chat turn and MCP sampling paths now omit the max-token bound for models the catalog marks as reasoning-class, because the pinned ai-sdk release sends max_tokens and those models reject it. ai-sdk now has the real fix (select max_completion_tokens from the resolved reasoning flag). Once that is released and archie-core's pin is bumped, revert the mitigation so a reasoning model is bounded again, and prove it with the test added for 7zu3 still passing in its new form (bound present, correct parameter name). Leaving the mitigation in place silently loses the output cap on exactly the models where an unbounded completion is most expensive.
Acceptance criteria
a reasoning-class model receives a max-token bound again, carried as max_completion_tokens, and the mitigation's tests are updated rather than deleted
Close reason
Mitigation reverted in c660857a; ai-sdk pinned at v0.1.42 (d5eefcc5).
Imported from beads archie-core-4hcu · GitHub #1335 · type task · priority P2 · created 2026-10-02 · closed 2026-10-05
archie-core bead 7zu3 was mitigated, not fixed: the chat turn and MCP sampling paths now omit the max-token bound for models the catalog marks as reasoning-class, because the pinned ai-sdk release sends max_tokens and those models reject it. ai-sdk now has the real fix (select max_completion_tokens from the resolved reasoning flag). Once that is released and archie-core's pin is bumped, revert the mitigation so a reasoning model is bounded again, and prove it with the test added for 7zu3 still passing in its new form (bound present, correct parameter name). Leaving the mitigation in place silently loses the output cap on exactly the models where an unbounded completion is most expensive.
### Acceptance criteria
a reasoning-class model receives a max-token bound again, carried as max_completion_tokens, and the mitigation's tests are updated rather than deleted
### Close reason
Mitigation reverted in c660857a; ai-sdk pinned at v0.1.42 (d5eefcc5).
---
_Imported from beads `archie-core-4hcu` · GitHub #1335 · type task · priority P2 · created 2026-10-02 · closed 2026-10-05_
sam
added the mediumtask labels 2026-10-27 13:38:50 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
archie-core bead 7zu3 was mitigated, not fixed: the chat turn and MCP sampling paths now omit the max-token bound for models the catalog marks as reasoning-class, because the pinned ai-sdk release sends max_tokens and those models reject it. ai-sdk now has the real fix (select max_completion_tokens from the resolved reasoning flag). Once that is released and archie-core's pin is bumped, revert the mitigation so a reasoning model is bounded again, and prove it with the test added for 7zu3 still passing in its new form (bound present, correct parameter name). Leaving the mitigation in place silently loses the output cap on exactly the models where an unbounded completion is most expensive.
Acceptance criteria
a reasoning-class model receives a max-token bound again, carried as max_completion_tokens, and the mitigation's tests are updated rather than deleted
Close reason
Mitigation reverted in c660857a; ai-sdk pinned at v0.1.42 (
d5eefcc5).Imported from beads
archie-core-4hcu· GitHub #1335 · type task · priority P2 · created 2026-10-02 · closed 2026-10-05