Skip to content

feat(routing): free-first price preference among equal-capability agents - #131

Closed
seonghobae wants to merge 3 commits into
mainfrom
feat/free-first-price-main
Closed

feat(routing): free-first price preference among equal-capability agents#131
seonghobae wants to merge 3 commits into
mainfrom
feat/free-first-price-main

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Summary

Buyer-facing routing honesty on a clean main base: among equally capable agents, prefer an explicit free rate (price_per_million[model] == 0) over paid, then cheaper known paid rates; unpriced is never free.

  • Capability-tag match + operator priority still dominate (Fugu-style)
  • Live _score_agent now includes free-first / known-price / cheapness tie-breaks
  • Paper contracts + architecture docs updated for the policy
  • Includes the same verified Semgrep FP suppressions needed for main-base PRs (cost_ledger bound placeholders, intentional TLS opt-out, validated urllib)

Test plan

  • python -m pytest tests/test_paper_contracts.py -q (7 passed)
  • CI Security + unit jobs

Merge note

Still blocked on independent APPROVE under require_last_push_approval (#123). Auto-merge armed when green.

Prefer explicit zero price_per_million over paid rates; never treat missing
price entries as free. Capability and priority still dominate (Fugu-style).
Also suppress verified main Semgrep FPs so the required gate can pass.
@seonghobae
seonghobae enabled auto-merge (squash) August 12, 2026 23:13
@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 37 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e84e4688-965e-4b12-8b14-7f237b5eac07

📥 Commits

Reviewing files that changed from the base of the PR and between 6841b71 and 90732a3.

📒 Files selected for processing (7)
  • README.md
  • contextual_orchestrator/__main__.py
  • contextual_orchestrator/cost_ledger.py
  • contextual_orchestrator/orchestrator.py
  • docs/architecture.md
  • tests/test_paper_contracts.py
  • tests/test_price_cli_validation.py

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Fail-closed JSON validation rejects NaN/inf/boolean/negative prices so
untrusted operator input never enters routing or cost evidence.
@seonghobae

Copy link
Copy Markdown
Contributor Author

Follow-up on head 6cd8bd1:

  • --price-per-million CLI JSON table wired into live free-first routing
  • Fail-closed validation rejects NaN/inf/boolean/negative prices (tests/test_price_cli_validation.py)
  • Paper contracts cover free-over-paid, priced-over-unpriced, priority-dominates-price

Auto-merge armed; merge waits on independent APPROVE (#123).

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 90732a3b7680a7d553c5fe9a33cafbc1b422e3c8.

  • Head SHA: 90732a3b7680a7d553c5fe9a33cafbc1b422e3c8

  • Workflow run: 31702394947

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (4 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (4 files)"]
  R1 --> V1["required checks"]
  Evidence --> S2["Docs: architecture.md"]
  S2 --> I2["operator or user guidance"]
  I2 --> R2["Review risk: Docs: architecture.md"]
  R2 --> V2["docs review"]
  Evidence --> S3["Test (2 files)"]
  S3 --> I3["regression suite"]
  I3 --> R3["Review risk: Test (2 files)"]
  R3 --> V3["targeted test run"]
Loading

@opencode-agent

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: 90732a3b7680a7d553c5fe9a33cafbc1b422e3c8
  • Workflow run: 31702394947
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 90732a3b7680a7d553c5fe9a33cafbc1b422e3c8.

  • Head SHA: 90732a3b7680a7d553c5fe9a33cafbc1b422e3c8

  • Workflow run: 31702394947

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (4 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (4 files)"]
  R1 --> V1["required checks"]
  Evidence --> S2["Docs: architecture.md"]
  S2 --> I2["operator or user guidance"]
  I2 --> R2["Review risk: Docs: architecture.md"]
  R2 --> V2["docs review"]
  Evidence --> S3["Test (2 files)"]
  S3 --> I3["regression suite"]
  I3 --> R3["Review risk: Test (2 files)"]
  R3 --> V3["targeted test run"]
Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant