Skip to content

chore: update coordinator branch from protected main - #1127

Merged
seonghobae merged 5 commits into
feat/organization-commercial-readiness-coordinatorfrom
main
Aug 18, 2026
Merged

chore: update coordinator branch from protected main#1127
seonghobae merged 5 commits into
feat/organization-commercial-readiness-coordinatorfrom
main

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Merge the current protected main tip into feat/organization-commercial-readiness-coordinator without rewriting feature history. This temporary ancestry-update PR contains no independent product scope and exists only to regenerate the exact integration candidate after protected main advanced. Do not squash or rebase.

cursor Bot and others added 5 commits August 18, 2026 10:25
releases.astral.sh now returns HTTP 403 for the pinned archive and blocks
org-wide OpenCode coverage-evidence. Keep the same SHA-256 pin and allow
only one hop onto GitHub's official release-asset hosts.

Closes #1109

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Seongho Bae <seonghobae@users.noreply.github.com>
* ⚡ Bolt: 성능 향상 - 대용량 로그 스캔 시 정규표현식 실행 전 O(N) 서브스트링 검증 선행

대용량 CI 로그(최대 2MB)를 스캔할 때 테스트 실패를 포함하지 않는 경우,
불필요한 정규표현식(`FAIL_SUMMARY_RE.findall`) 탐색을 방지하여 스캔 속도를 개선했습니다.
단순 문자열 존재 여부 검사(`"Error: Test failures" not in text`)를 정규표현식보다 앞서 실행하도록 순서를 변경하였습니다.

* docs(changelog): preserve existing release history

* ⚡ Bolt: 성능 향상 - 대용량 로그 스캔 시 정규표현식 실행 전 O(N) 서브스트링 검증 선행

대용량 CI 로그(최대 2MB)를 스캔할 때 테스트 실패를 포함하지 않는 경우,
불필요한 정규표현식(`FAIL_SUMMARY_RE.findall`) 탐색을 방지하여 스캔 속도를 개선했습니다.
단순 문자열 존재 여부 검사(`"Error: Test failures" not in text`)를 정규표현식보다 앞서 실행하도록 순서를 변경하였습니다.

* fix(perf): preserve changelog history

* docs(perf): record the actual optimization date

* test(perf): prove marker-absent regex short circuit

* refactor(perf): document the bounded fast path

* docs(r-coverage): cite Crochemore–Perrin marker short-circuit

Keep installer tests on the documented linux x86_64 path, record the
control-plane classification architecture, and cite two-way matching plus
CWE-407 so the marker-absent path is not treated as a grammar change.

* fix(coverage): accept only bounded relative requirement includes

Materialize a base Python lock only when every package line is an exact
SHA-256 pin or a two-token relative -r/--requirement include of a
candidate lock path. A lone --require-hashes directive, ./dotted paths,
and -r other-hashes.txt no longer enter the trusted build context.

* ⚡ Bolt: 성능 향상 - 대용량 로그 스캔 시 정규표현식 실행 전 O(N) 서브스트링 검증 선행

대용량 CI 로그(최대 2MB)를 스캔할 때 테스트 실패를 포함하지 않는 경우,
불필요한 정규표현식(`FAIL_SUMMARY_RE.findall`) 탐색을 방지하여 스캔 속도를 개선했습니다.
단순 문자열 존재 여부 검사(`"Error: Test failures" not in text`)를 정규표현식보다 앞서 실행하도록 순서를 변경하였습니다.

* test(r-coverage): restore cold-path regression contract

---------

Co-authored-by: seonghobae <8172694+seonghobae@users.noreply.github.com>
Co-authored-by: opencode-agent[bot] <219766164+opencode-agent[bot]@users.noreply.github.com>
#1119)

Adds a "contextual-orchestrator" entry to opencode.jsonc's provider block,
an OpenAI-compatible gateway that auto-discovers models across
Bytez/NVIDIA NIM (x2 keys)/OpenRouter/OpenAI from KV-registered credentials
and auto-optimizes routing by cost (contextual-orchestrator repo,
model_discovery.py). Pointing OpenCode at one model id here delegates
upstream provider/model selection to the gateway.

Deliberately additive and inert:
- model/small_model are NOT switched to this provider yet -- that requires
  CONTEXTUAL_ORCHESTRATOR_BASE_URL and CONTEXTUAL_ORCHESTRATOR_TOKEN to be
  provisioned as repo/org Actions variables first. Until then this provider
  is defined but unused, so the Required OpenCode Review pipeline keeps
  working unchanged.
- No workflow YAML touched; the bootstrap/dispatch secret-isolation split
  in opencode-review.yml / opencode-review-dispatch.yml is untouched.
- Noema and Strix are intentionally out of scope for this change: their
  review logic lives in scripts/ci/noema_review_gate.py and
  scripts/ci/strix_quick_gate.sh (fetched from a SHA-pinned trusted-source
  archive at run time), which have not been reviewed and have their own
  fail-closed credential/test harnesses.

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
opencode.jsonc gained its first `//` comment (PR #1119, the
contextual-orchestrator provider block), which broke
assert_opencode_reasoning_effort.py's plain json.loads with
"Expecting property name enclosed in double quotes: line 3 column
3" -- and the same strict json.loads in three test_opencode_agent_contract.py
contract tests that read the file directly.

Add a small comment-stripping pass (strip_jsonc_comments) that only
recognizes // and /* */ outside JSON string literals, so a string
value containing // (the $schema URL) is left untouched. The
integration/contract tests now share this helper instead of calling
json.loads on the raw file.

Refs #1119.

Co-authored-by: Claude <noreply@anthropic.com>
)

Add a thin minute-10 caller for ContextualWisdomLab/OriginWeave on
protected main. The caller maps only established scheduler credentials,
grants job-scoped OIDC, and leaves NVIDIA_NIM_API_KEY on the reusable
worker.
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

1 similar comment
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@coderabbitai

coderabbitai Bot commented Aug 18, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 946b934a-b6e1-480c-92cf-e333c9047244

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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.

@seonghobae
seonghobae merged commit 3e46618 into feat/organization-commercial-readiness-coordinator Aug 18, 2026
196 of 262 checks passed
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