feat(security-agent): move manual workflows into workers#3312
Open
jeanduplessis wants to merge 6 commits into
Open
feat(security-agent): move manual workflows into workers#3312jeanduplessis wants to merge 6 commits into
jeanduplessis wants to merge 6 commits into
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryThe new commit ( Resolved Issues (all fixed)
Files Reviewed (28 files)New in this round:
Previously reviewed (unchanged):
Reviewed by claude-sonnet-4.6 · 1,366,549 tokens Review guidance: REVIEW.md from base branch |
2468bdb to
730492f
Compare
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.
Summary
Security Agent manual sync, dismissal, and analysis work now enter durable Worker-backed command paths, and analysis callbacks stay loosely coupled from Cloud Agent Next.
Why this change is needed
Manual Security Agent actions can trigger multi-step GitHub, queue, Cloud Agent, and callback work. Keeping that orchestration on synchronous web paths makes request latency, retries, ownership checks, and terminal state recovery harder to control. The security callback fast path also made
cloud-agent-nextaware of one product-specific downstream consumer, which blurred service boundaries.How this is addressed
cloud-agent-nextcallback delivery generic: callers provide ordinary HTTP callback targets, while Security Auto Analysis chooses web callback routing by default and can opt into a configured Worker HTTP ingress when needed.cloud-agent-next.Architecture
Human Verification
Reviewer Notes
Human Reviewer Flags
cloud-agent-nextno longer knows about Security Auto Analysis delivery mode or service binding; callback destination ownership moves back to the caller.SECURITY_ANALYSIS_CALLBACK_WORKER_BASE_URLwhenSECURITY_ANALYSIS_CALLBACK_ROUTING_MODE=worker; default config stays on web ingress.Code Reviewer Agent
Code Reviewer Notes
services/security-sync/src/dismiss.tsandservices/security-auto-analysis/src/manual-analysis.ts.services/cloud-agent-next/src/callbacks/delivery.tsplus Security Auto Analysis target construction inservices/security-auto-analysis/src/launch.ts.