Skip to content

feat(api): opt-in CORS allowlist for browser clients - #136

Open
seonghobae wants to merge 4 commits into
mainfrom
feat/cors-allowlist
Open

feat(api): opt-in CORS allowlist for browser clients#136
seonghobae wants to merge 4 commits into
mainfrom
feat/cors-allowlist

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Summary

Buyer browser SDKs need CORS without opening the gateway by default.

  • SecurityConfig.cors_allow_origins exact-match allowlist (CLI --cors-allow-origin)
  • OPTIONS preflight with methods/headers max-age
  • Response Access-Control-Allow-Origin + credentials for non-*
  • Empty allowlist = no CORS headers

Test plan

  • pytest tests/test_cors_allowlist.py (3 passed)
  • CI unit + Semgrep

Auto-merge armed; still needs independent APPROVE (#123).

CORS is disabled by default. Exact --cors-allow-origin entries enable
Access-Control-Allow-Origin, credentials for non-*, and OPTIONS preflight.
@seonghobae
seonghobae enabled auto-merge (squash) August 12, 2026 23:57
@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: 21 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: cdeb1594-e669-4aa0-bb84-9477283b88ad

📥 Commits

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

📒 Files selected for processing (7)
  • .github/workflows/one-shot-pr136-cors-header-hardening.yml
  • contextual_orchestrator/__main__.py
  • contextual_orchestrator/cost_ledger.py
  • contextual_orchestrator/orchestrator.py
  • contextual_orchestrator/server.py
  • docs/architecture.md
  • tests/test_cors_allowlist.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.

origin = (self.headers.get("origin") or "").strip()
allowed = security.cors_origin_allowed(origin)
if allowed:
self.send_header("access-control-allow-origin", allowed)
- feat/cors-allowlist

permissions:
contents: write

@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 9717128aa437714ce39de5aae0592be2f2c0d7e4.

  • Head SHA: 9717128aa437714ce39de5aae0592be2f2c0d7e4

  • Workflow run: 32014582802

  • 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["Workflow: one-shot-pr136-cors-header-hardening.yml"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow: one-shot-pr136-cors-header-hardening.yml"]
  R1 --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (4 files)"]
  S2 --> I2["repository behavior"]
  I2 --> R2["Review risk: Changed file (4 files)"]
  R2 --> V2["required checks"]
  Evidence --> S3["Docs: architecture.md"]
  S3 --> I3["operator or user guidance"]
  I3 --> R3["Review risk: Docs: architecture.md"]
  R3 --> V3["docs review"]
  Evidence --> S4["Test: test_cors_allowlist.py"]
  S4 --> I4["regression suite"]
  I4 --> R4["Review risk: Test: test_cors_allowlist.py"]
  R4 --> V4["targeted test run"]
Loading

@opencode-agent

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: 9717128aa437714ce39de5aae0592be2f2c0d7e4
  • Workflow run: 32014582802
  • 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 9717128aa437714ce39de5aae0592be2f2c0d7e4.

  • Head SHA: 9717128aa437714ce39de5aae0592be2f2c0d7e4

  • Workflow run: 32014582802

  • 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["Workflow: one-shot-pr136-cors-header-hardening.yml"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow: one-shot-pr136-cors-header-hardening.yml"]
  R1 --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (4 files)"]
  S2 --> I2["repository behavior"]
  I2 --> R2["Review risk: Changed file (4 files)"]
  R2 --> V2["required checks"]
  Evidence --> S3["Docs: architecture.md"]
  S3 --> I3["operator or user guidance"]
  I3 --> R3["Review risk: Docs: architecture.md"]
  R3 --> V3["docs review"]
  Evidence --> S4["Test: test_cors_allowlist.py"]
  S4 --> I4["regression suite"]
  I4 --> R4["Review risk: Test: test_cors_allowlist.py"]
  R4 --> V4["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.

2 participants