test(coverage): verify the stacked native-fuzz boundary - #777
Closed
seonghobae wants to merge 58 commits into
Closed
test(coverage): verify the stacked native-fuzz boundary#777seonghobae wants to merge 58 commits into
seonghobae wants to merge 58 commits into
Conversation
* test(strix): align setup-python pin contract * fix(strix): isolate backend support-code scopes * fix(strix): update vulnerable Python dependencies * fix(strix): scan changed Rust security boundaries
Install and pin LLVM 19 coverage tools for Debian-packaged Rust, refresh the remediated Strix lock, and document the compatibility and fail-closed coverage contract.
Rebuild the focused exact-name Atheris lock boundary directly on the fully checked OpenCode diagnostics and Strix hardening prerequisite, preserving only the materializer, realistic regression, APA 7 doctoring, plan, specification, and changelog delta.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
Apply the native-fuzz exact-name classifier on top of the current shared failure-summary materializer instead of replacing it with an older implementation, and make the permanent diagnostics workflow execute and compile the new realistic regression.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Temporary verification completed — do not merge
This Draft PR existed only to obtain pull-request-triggered exact-head evidence for stacked coverage-policy PR #763.
Exact current head
66d5a26498503361aa814e5be742ac8c6335246bpassed all direct pull-request workflows:30991153826;30991153764;30991153704;30991153852;30991153727;30991154176;30991153720;30991153841;30991153859.The predecessor
050cb25e3a7c317503c5221f095281cb9400c780failed exact run30990609972because the stacked branch had removed #759’s shared bounded failure-summary publisher. Repaired head54591186557d8251f9c2967c11cd98ff926d6464restored that integration and passed run30990945724; current head additionally corrected stale integration guidance and re-passed every direct check.This temporary PR is closed without merge. Product integration remains #759 → #763 → contextual-orchestrator #96.