feat(bots): regenerate registry with WebDecoyBot (companion to app #691) - #21
Merged
Conversation
Generated from pkg/agents via export-agent-registry — do not hand-edit. Adds WebDecoyBot (first-party monitoring crawler, base score 5) so the SDK classifies WebDecoy's own verify/readiness fetches as a known crawler instead of an unknown bot. Parity vectors + the 169-agent count assertion updated to match; parity test replays every vector through the TS matcher.
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.
What
Companion to WebDecoy/app#719. Regenerates the SDK's bot registry from
pkg/agentsviaexport-agent-registry— generated files, not hand-edited.Adds WebDecoyBot (first-party monitoring crawler, base score 5, respects robots) so the SDK classifies WebDecoy's own verify/readiness fetches as a known crawler instead of an unknown bot when they hit a customer site running
@webdecoy/node.Changes
registry.generated.ts— WebDecoyBot inserted in match order (monitoring section), count comment 168 → 169.parity-vectors.generated.json— two new vectors (webdecoybotand the embedded-in-full-UA form), both classifying asmonitoring.bots.test.ts— the registry-integrity count assertion bumped to 169.Testing
parity.test.tsgreen: the TS matcher agrees with Go on every recorded vector, and still never classifies a real browser as a bot.Merge alongside WebDecoy/app#719 — the vectors are generated from that PR's registry.