fix(strix): trust event repository visibility - #1320
Conversation
📝 WalkthroughWalkthroughStrix는 이벤트 metadata에서 저장소 visibility를 우선 확인합니다. ChangesStrix 계약 정렬
Estimated code review effort: 3 (Moderate) | ~25 minutes Merge Risk: 🟠 High · up to The current routing can treat an internal repository_dispatch as public and send repository content to a public provider, so merge should be blocked until visibility is mapped from the API response correctly. The fallback helper also uses a stale model identifier and should be synchronized to avoid incorrect fallback reporting. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Linked Issues checkExplanation PR은 [ Full details: Docstring CoverageExplanation Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 5 functions across 5 files. (7 skipped: 6 unsupported, 1 too large.) ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
|
Fixed on exact head |
|
Path-policy #13146b06a92 already updates those two contracts. Hosted path-policy |
…ty-20260825 # Conflicts: # CHANGELOG.md
…60825' into codex/strix-event-visibility-20260825
|
Exact head 5f00b76 composes the concurrent internal-visibility privacy repair with the NVIDIA overload fallback repair. Root cause: |
|
Hosted run 32818169695 reached a complete fallback scan with zero vulnerabilities, but the generic report-warning gate rejected two exact scanner notices: the MODEL QUALITY WARNING banner for the configured fallback and the unauthenticated Hugging Face download warning. Commit 8ee7e57 removes only those two exact notice lines before the existing fail-closed scan. General WARNING/Fatal/Denied/Timeout matching and explicit 429/provider-failure detection remain unchanged. |
|
Exact-head 3b9b238 fixes the newly reproduced cross-provider endpoint leak: a direct-OpenAI fallback clears a foreign NVIDIA/OpenRouter API base while a direct-OpenAI primary retains its explicitly configured base. The filtered |
|
Exact-head formal review requested for All 13 substantive commit-associated workflows are terminal GitHub-success and unresolved review threads are 0. The separate Please submit an independent substantive Reviews API verdict on this exact head. Do not treat the green SAST/Trivy labels as exact-head provenance while #1222 remains open, and do not merge without the required independent approvals. |
|
Hosted run 32826128897 proved the NVIDIA fallback completed with zero vulnerabilities, but its exact informational MODEL QUALITY WARNING remained in the per-attempt console log and the generic fail-closed classifier rejected the successful scan. Exact-head a8f6af1 sanitizes only the two already-contracted scanner notices before classification while preserving the raw attempt artifact and every unknown/provider failure. The filtered regression passes. |
|
@opencode-agent Please perform an independent formal review of exact current head |
Take #1320 Strix event-repository visibility trust from main. Keep this PR's NIM-only publisher pool, surfaces split, and live gpt-5.4 pins. Co-authored-by: Seongho Bae <seonghobae@users.noreply.github.com>
Keep the classified-copy box sanitizer so gate-last-attempt stays raw. Take #1320's HF Hub notice filter and event-visibility/fallback contracts. Point OpenCode dispatch-pool harness needles at openai/gpt-5.4 now that opencode-review-dispatch.yml on main lists that model. Co-authored-by: Seongho Bae <seonghobae@users.noreply.github.com>
|
Protected-main consumer acceptance on unchanged ScopeWeave #523 exact head
ScopeWeave #531 acceptance is still running and remains non-passing until terminal evidence. |
|
Additional protected-main consumer acceptance (2026-08-25 UTC):
This is coherent exact-head complete-scan evidence, not a backend-unavailable false green. Together with the separately recorded #523 canary, the protected-main provider-routing repair now has two live ScopeWeave consumer acceptances. |
Closes #1317
Closes #1319
Outcome
gpt-5.4.public -> false,private/internal -> true, and fail closed on missing or unknown visibility.Exact current identity
a8f6af10bbad996c7a741177e364a5180a59494emain@8fd471a31399a914d9cb22a840f4a4c68e010ea69b41d3477b54d046e89d93f5dea8ff7d12b45f3bRED → GREEN evidence
RED exact head
33d5b334267073d43200b403b48db7b00dcbaffc, hosted run32825500449, job97732457908:openai/gpt-5.4inheritedhttps://integrate.api.nvidia.com/v1;https://integrate.api.nvidia.com/v1|https://integrate.api.nvidia.com/v1, and the mock reproduced the live 404 routing boundary.GREEN descendant head
a8f6af10bbad996c7a741177e364a5180a59494e, hosted run 32830223033, job97747008382:a8f6af1…;test_strix_quick_gate.shpassed;Current-head hosted evidence
Thirteen substantive workflow runs are terminal-success: Strix quality, Secret Scan, Security Scan, SAST, SBOM, OSV, Exact Artifact SBOM Attestation, Commercial Readiness, Rust Coverage, Hourly Review, Python Security, Scorecard, and CodeQL. The separate
Repair PR 827 CodeRabbit commentsrun is skipped and is not counted.CodeQL run 32830222942 explicitly checked out exact head
a8f6af1…for detection and compatibility analysis, and checked out the current synthetic merge9b41d347…only for the explicitly named merge-preview jobs.The SAST and head-oriented Security jobs are GitHub-success but remain non-passing exact-head provenance under #1222: their runtime checkout was synthetic merge
7f345aed…, not submitted heada8f6af1…. That evidence is recorded in #1222. No queued, skipped, status-only, predecessor, or head-oriented synthetic-merge evidence is counted as exact-head provenance.Merge only after #1222 provenance is satisfied and live governance has the required independent exact-current-head formal approvals.