Skip to content

Clarify capability-filter availability signals#46

Merged
dorukardahan merged 1 commit into
mainfrom
dorry/loop-issue-39-202607181251
Jul 23, 2026
Merged

Clarify capability-filter availability signals#46
dorukardahan merged 1 commit into
mainfrom
dorry/loop-issue-39-202607181251

Conversation

@dorukardahan

Copy link
Copy Markdown
Owner

Summary

  • Replace the ambiguous rate limit capability-filter label with the inputs the filter actually evaluates.
  • Clarify that live routing has no provider-response or cooldown input and does not inspect live quota telemetry.

Verification

  • npm --workspace zeroapi test -- __tests__/filter.test.ts __tests__/route-state.test.ts __tests__/decision.test.ts
  • npm test

Closes #39

@dorukardahan dorukardahan added repolooper:managed RepoLooper has managed this issue or pull request. repolooper:state-active RepoLooper is actively progressing or verifying this item. labels Jul 18, 2026
@dorukardahan
dorukardahan merged commit 89e3f96 into main Jul 23, 2026
3 checks passed
@dorukardahan
dorukardahan deleted the dorry/loop-issue-39-202607181251 branch July 23, 2026 21:59
@dorukardahan dorukardahan removed the repolooper:state-active RepoLooper is actively progressing or verifying this item. label Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

repolooper:managed RepoLooper has managed this issue or pull request.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify what “rate limit” means in the capability filter

1 participant