Repository navigation
Complete local research platform and deployment workflows - #4
Merged
Merged
Conversation
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
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.
The default branch still contains the earlier research prototype with permissive CI, non-durable workflows, and simulated response success. Merge the completed research-platform branch into
masterso the default checkout contains the current implementation and documented acceptance evidence.This adds durable triage and response recovery, identity and independent review workflows, evidence-based response verification, the disposable Wazuh enforcement lab, consistent container deployment, stricter tests and CI, and updated operating documentation.
Pre-merge verification found that the advisory feed now reports three already-reviewed Chroma CVEs under PYSEC IDs. The audit now matches advisory aliases as well as primary IDs, retaining exact package/version and expiry restrictions. Six regression cases cover recognized IDs, aliases, unreviewed advisories, version mismatches, and expired exceptions. No dependency exceptions were added or extended. CI also refreshes its Python packaging tools and retains dependency audit diagnostics.
Validation on the final branch commit:
The branch includes earlier native/container/browser/lab acceptance reports; those are historical evidence, not a new live acceptance run for this merge. Production vendor integration and external research validation remain documented limitations.