Skip to content

v0.24.0 · Project provider capacity

Choose a tag to compare

@hpoenixf hpoenixf released this 06 Nov 23:30

v0.24.0 · Project provider capacity

Provider Admission keeps one original project-local capacity owner for the same normalized endpoint across model, streaming and provider-label changes. An admitted task retains its original configuration and tickets. Missing capacity state fails closed; unknown dispatched requests remain occupied. Legacy projects are not silently migrated.

  • Fixed real cohort: 10/10 mechanical and named Runtime contracts, with ten saved Reports and Publications. 30 original responses reported zero Go balance charge, with no new unknown outcomes.
  • Model content is reviewed separately. C09's persisted report contains a wrong citation; its final reply discloses the error but does not repair the report. Other wording issues and all prior unknowns are retained.
  • Final candidate: 988/988 tests, locked installation and build passed on Node 26.11.1. The declared Node range remains >=26.8.1 <27.
  • Real-provider evidence is serial. Process contention and failure retention have separate provider-free tests. Capacity is project-local, not account-wide or distributed.

English evidence and limits · Usage · Exact candidate CI

中文

v0.24.0 在同一规范化端点的项目配置修订间保留原 Admission 容量 Owner。已准入任务沿用原配置与票据;容量状态缺失时拒绝执行,已派发的 unknown 保留占用,旧项目不会隐式迁移。

真实十题的机械检查与具名 Runtime 合同均为 10/10,形成十份原 Report 与 Publication;30 个完整响应均记录 Go 零余额扣费,无新增 unknown。模型内容另行审查:C09 原报告错引仍未修复,最终回复仅披露问题;其他措辞问题和历史未知结果一并保留。最终候选 988/988、锁定依赖安装和构建通过,实际 Node 为 26.11.1。

中文证据与边界 · 用法