feat(lifecycle): add optional bounded Firecrawl company capture - #1017
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
blove
enabled auto-merge (squash)
September 5, 2026 19:49
Contributor
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
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.
Company enrichment can lose homepage evidence to redirects or response size limits. Add an explicitly configured Firecrawl homepage capture that returns the existing bounded evidence schema, while keeping direct capture as the default and email delivery independent of enrichment.
The adapter makes one request with a 15-second total deadline, a 2 MiB response cap, code-only failures, and bounded capture diagnostics. It validates requested/final provenance and public hostnames; Firecrawl owns remote DNS and intermediate redirect safety. No new agent workflow, fallback chain, or SDK dependency.
Validation: lifecycle and growth-research test, check, lint, and build targets passed; 52 new adapter/selector tests passed. Six fresh public homepage responses replayed through the actual adapter produced schema-valid evidence. Those experiments used keyless access and do not verify an authenticated account. Production remains default-direct until an account key is configured and authenticated capture is verified.