feat(growth): link install and development runtime to founder outreach - #1004
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
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.
Install and development runtime evidence can now qualify a contact for the existing generic founder sequence. A linked, non-CI install with a usable email and its first development runtime observation approves outreach; repeated observations cannot create another enrollment. The new activation switch defaults off.
This includes the observation intake, projection, deletion protections, operator queries, and additive schema required by that path. Collection retains a digest of the package-local installation token and restricted identity evidence. Final send authorization rechecks linked evidence, conflicts, suppression, and deletion. Optional enrichment does not delay the hello. Collectors and package publication follow separately.
Validation: Growth and lifecycle tests, lint, and builds passed; all 62 integration tests passed against the isolated Neon test database; 58 collection/metadata website tests and three Next configuration tests passed. The full website production build passed, and its collection route trace contains all 15 blog MDX files. Staged credential scan and diff checks passed.
Rollout: migrations 0004–0007 have been applied to preview and production, with a second run applying nothing in each environment. Historical deletion initialization completed (zero preview contacts, one production contact). Existing production campaign settings are preserved; install/runtime activation and collection remain disabled. The real preview send and collector release remain subsequent gates.