feat(growth): cut over company enrichment to Dawn - #1041
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 6, 2026 21:58
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 enrichment now uses the Dawn company agent and shared browser capture. The previous lifecycle generator and baseline execution path are removed; historical artifacts remain readable and the generic email sequence stays independent of enrichment. Disabling new research still allows existing attempts and cleanup to reconcile.
Recovery uses the existing durable job ledger and single-submission fence. Unresolved attempts fail after a five-minute grace period. Cleanup attempts cancellation, verifies thread absence on separate ticks, and checks trace deletion independently. A seven-day cleanup limit ends visibly failed and discards captured job input while retaining published artifacts and correlation metadata.
Validation: scoped lifecycle, Growth, and research tests, lint, type checks and builds; disposable PostgreSQL tests cover concurrent submission, stale leases, stops/deletion, repeated cleanup observations, and atomic input removal. Production verification uses an isolated non-deliverable fixture with no campaign approval activity.