Repository navigation
feat(bot-middleware): label every bot hit with who the bot is; declared agents via Web Bot Auth (1.6.0) - #19
Merged
Conversation
…ed agents via Web Bot Auth (1.6.0) Step 1 (Measure) of the bot-swarm lane, web channel, in the shared middleware every fleet site imports. Lockstep with isimplifyme-site's inlined copy (#216) and stored by apex-portal (#498). - detectDeclaredAgent reads Signature-Agent (+ Signature-Input/Signature => signed); botKind = crawler | agent_fetch | declared_agent | unknown_bot; AGENT_FETCHERS = ChatGPT-User, meta-externalfetcher, Claude-User, Perplexity-User, MistralAI-User, DuckAssistBot. - 5 new AI fetcher patterns (48 -> 53). Every bot-hit payload adds kind, signed, agentDirectory; a signing agent with a browser UA is tracked as agent:<directory host>; the AI-referrer path skips signing agents. - version 1.5.0 -> 1.6.0 (additive fields; no API change). vitest 77 pass (+14). tsc clean. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Why
Step 1 (Measure) of the bot-swarm lane, web channel, in the shared middleware every fleet site imports. Lockstep with isimplifyme-site's inlined copy (iSimplifyMe/isimplifyme-site#216); apex-portal stores the new fields (iSimplifyMe/apex-portal#498).
What
detectDeclaredAgentreadsSignature-Agent(plusSignature-Input/Signature⇒signed);botKind=crawler | agent_fetch | declared_agent | unknown_bot;AGENT_FETCHERS= ChatGPT-User, meta-externalfetcher, Claude-User, Perplexity-User, MistralAI-User, DuckAssistBot.kind,signed,agentDirectory; a signing agent with a browser UA is tracked asagent:<directory host>; the AI-referrer path skips signing agents.1.5.0 → 1.6.0: additive payload fields and new exports, no API change.Evidence
vitest run: 77 pass (63 + 14 new, incl. trackBot payload tests with a stubbed fetch).tsc --noEmitclean.Rollout
Publish is tag-driven (
v1.6.0⇒npm publish). Sites pick it up onpnpm update @isimplifyme/ui+ deploy — the same rollout 1.5.0 is still waiting for (lockfiles pin 1.2.1). Rollback: don't tag, or pin.🤖 Generated with Claude Code