chore(bots): regenerate registry for xAI-SearchBot and LinkupBot - #39
Merged
Conversation
A span around protect() and a child around rule evaluation, carrying the
decision id (which joins a span to its dashboard row), the conclusion, the
deciding rule, and whether the request cost a round trip to ingest.
The tracer is INJECTED, not imported. An optional peer dependency was the
obvious route and the wrong one: this package is dependency-free and
passes an edge-compatibility gate, and Workers and Vercel Edge are exactly
where a stray transitive import hurts. A conditional
import('@opentelemetry/api') bundles badly too -- the bundler either
resolves it, adding weight for the majority who do not use it, or fails on
a module that is legitimately absent.
The Tracer type is a structural subset of OpenTelemetry's, so
trace.getTracer('webdecoy') satisfies it with no adapter. Omit it and
there are no spans, no dependency and no behaviour change, which is the
majority case and should cost them nothing.
A tracer cannot break a request. startSpan returning nothing, throwing, or
returning a span whose every method throws all degrade to a no-op --
observability that can take the request path down is worse than none. The
no-op span also means call sites need no null checks, and an `if (span)`
is a branch that gets forgotten on the path that mattered.
Eight tests, four of them hostile tracers. Also asserts the span is ended
on the ERROR path: a leaked span holds memory and never reaches the
exporter, so the trace is silently incomplete rather than absent.
Closes WebDecoy/app#740
Companion to WebDecoy/app. Both crawlers were hitting production and landing unclassified, so requests from them were excluded from AI traffic figures rather than attributed. Generated, not hand-edited: pkg is the source of truth and the export runs in agents.MatchUserAgent order, which the TS matcher depends on because it takes the first hit. The registry count guard moves 169 -> 171. It exists to make a registry change deliberate rather than incidental, so bumping it here is the intended workflow rather than a nuisance. 397 tests pass, parity vectors included.
Companion to WebDecoy/app. DuckAssistBot, SofyaBot, Reflectionbot and IbouBot join xAI-SearchBot and LinkupBot; all six were crawling production and landing unclassified. IbouBot is registered as a SEARCH crawler, not AI: its own page states it is a Cloudflare Verified Bot classified as Search. It arrived in the same unclassified tail as the others and does not belong with them. Count guard 171 -> 175. 397 tests pass.
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.
Companion to app#809.
Both crawlers were hitting WebDecoy production and landing unclassified, so requests from them were excluded from AI traffic figures rather than attributed:
xAI-SearchBot/1.0LinkupBot/1.0Generated, not hand-edited.
pkgis the source of truth and the export runs inagents.MatchUserAgentorder, which the TS matcher depends on because it takes the first hit.The registry count guard moves 169 → 171. It exists to make a registry change deliberate rather than incidental, so bumping it is the intended workflow.
397 tests pass, parity vectors included.