Fix detection-only reflect endpoint#115
Merged
Merged
Conversation
Copilot
AI
changed the title
Add detection-only workflow
Add detection-only workflow for faster detector iteration
May 14, 2026
Copilot created this pull request from a session on behalf of
davidslater
May 14, 2026 22:10
View session
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a lightweight, manual GitHub Actions workflow to run the repository’s generated detection job against local fixture artifacts, enabling faster iteration on detector behavior without running the full activation/agent pipeline.
Changes:
- Added a
workflow_dispatch“detection-only” workflow that stubsactivation/agentand runs the containerized detection job using uploaded fixture artifacts. - Added
safeandpatchfixtures undertestdata/detection-only/(prompt +agent_output.json, plus a sampleaw-*.patchfor the patch case). - Documented the new workflow and fixture mapping in
README.md.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/detection-only.yml |
New manual workflow that uploads fixture data as an agent artifact and runs the copied detection job against it. |
README.md |
Documents the purpose and mechanics of the new detection-only workflow. |
testdata/detection-only/safe/aw-prompts/prompt.txt |
Adds “safe” prompt fixture content. |
testdata/detection-only/safe/agent_output.json |
Adds “safe” agent output fixture. |
testdata/detection-only/patch/aw-prompts/prompt.txt |
Adds “patch” prompt fixture content. |
testdata/detection-only/patch/agent_output.json |
Adds “patch” agent output fixture. |
testdata/detection-only/patch/aw-docs.patch |
Adds a sample aw-*.patch fixture to exercise patch-handling paths. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 7/7 changed files
- Comments generated: 2
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Copilot
AI
changed the title
Add detection-only workflow for faster detector iteration
Fix detection-only reflect endpoint
May 14, 2026
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.
Bug Fix
What was the bug?
The detection-only workflow pointed
threat-detectat a host-side/reflectURL with no listener. The detector runs inside AWF and needs to call the internal api-proxy endpoint instead.How did you fix it?
THREAT_DETECTION_REFLECT_URLto the AWF api-proxy service.safefixture directory.patchthe only/default detection-only fixture.