fix: forward 100% BrightData-resolved backlinks to Mystique for bridge enrichment#2378
Open
miakobchuk wants to merge 1 commit intomainfrom
Open
fix: forward 100% BrightData-resolved backlinks to Mystique for bridge enrichment#2378miakobchuk wants to merge 1 commit intomainfrom
miakobchuk wants to merge 1 commit intomainfrom
Conversation
…e enrichment When all broken backlinks are resolved by Bright Data, the audit worker previously returned early and skipped Mystique entirely. This meant the autofix bridge never fired for those sites, so `fixable`/`fixabilityReason` were never set on BrightData- resolved suggestions. Remove the early return and forward the empty `brokenLinks` array to Mystique. Mystique's fast path (added in companion PR) detects the empty array, skips the LLM crew, and runs only the Subset 2 bridge enrichment over the BrightData suggestions already stored in SpaceCat. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
mikeweis
approved these changes
Apr 13, 2026
BaDos
approved these changes
Apr 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
3 participants
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
brokenLinksarrayRoot cause: ~0.7% of broken-backlinks audits (37/5290 over 7 days in prod) hit the 100% BrightData path and skipped Mystique entirely, leaving
fixable/fixabilityReasonunset on those suggestions.No breaking change. The message shape is unchanged. Mystique receives
brokenLinks: []— the companion PR handles this case.Deploy order: Mystique companion PR must be deployed first. If this lands before Mystique, the old task receives
brokenLinks: [], logs an error, and runs the LLM crew with empty input (no crash, just wasteful). Correct order: Mystique → audit-worker.Test plan
should forward to Mystique with empty brokenLinks when all links resolved via Bright Data— verifiessendMessageis called withbrokenLinks: []and logs "Forwarding to Mystique""Forwarding to Mystique"to confirm the path firesfixable/fixabilityReasonon their suggestions🤖 Generated with Claude Code