feat(growth): explain company capture failures - #1015
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
blove
enabled auto-merge (squash)
September 5, 2026 18:38
Contributor
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 acquisition previously returned empty evidence without explaining whether a page was oversized, unavailable, timed out, or rejected by the redirect policy. Add optional bounded per-page diagnostics and retain them in local pilot acquisition reports, including diagnostics emitted before a company capture fails.
The existing evidence return type, fetch limits, redirect rules, SSRF controls, cancellation behavior, and outreach behavior remain unchanged. Diagnostic observers cannot change capture outcomes. Records contain outcome codes, original requested paths, HTTP status, and known byte counts, without raw errors, bodies, or redirect URLs.
Validation: lifecycle and growth-research tests, checks, lint, and builds passed. Focused regression suites passed 71 lifecycle and 4 acquisition tests. A six-company live acquisition reproduced rejected redirects, oversized HTTP 200 pages, and genuine 404s with explicit diagnostics. Independent spec and code reviews passed.
A separate local Firecrawl capture experiment recovered 16/18 requested pages across all six companies, compared with 5 pages across three companies for direct capture. It made no model calls and adds no production provider integration or dependency in this PR.