feat(telemetry): ship install and development progress collectors - #1007
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Contributor
Contributor
Contributor
blove
force-pushed
the
blove/growth-hello-collectors
branch
from
September 5, 2026 04:56
91490e3 to
396e28d
Compare
blove
enabled auto-merge (squash)
September 5, 2026 04:56
Contributor
auto-merge was automatically disabled
September 5, 2026 04:57
Pull request was closed
blove
enabled auto-merge (squash)
September 5, 2026 04:57
Contributor
Contributor
blove
force-pushed
the
blove/growth-hello-collectors
branch
from
September 5, 2026 05:41
c6d56cb to
06af0aa
Compare
Contributor
blove
disabled auto-merge
September 5, 2026 06:05
blove
enabled auto-merge
September 5, 2026 06:05
Contributor
…llectors # Conflicts: # libs/ag-ui/package.json # libs/langgraph/package.json # libs/telemetry/README.md
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
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.
The shipped packages now capture install context and development browser progress for the install-to-founder-hello journey. A package-local random token links the install to runtime announcements without a claim click. Non-CI linked evidence can qualify the install email through the separately gated backend in #1004.
The four package hooks honor opt-out and skipped scripts, distinguish CI, and fail open. Contributor workspace installs use explicit inert stubs; ng-packagr supplies the real shared hooks in published packages. Runtime collection starts only on supported development use; production, SSR, imports, unused construction, automated browsers, and explicit opt-out stay silent. Actual Angular production builds remove installer token literals. Website signals, privacy disclosures, package documentation, and generated public context describe the behavior. Existing Chat CSS/theme exports are preserved.
Validation: ordinary root
npm cipassed; lint, tests, and builds passed for telemetry, LangGraph, AG-UI, Chat, Render, and Growth; 60 website tests and the full website build passed. All four actual npm tarballs passed install/CI/opt-out/skipped-script checks and contain the real hooks rather than contributor stubs. Real Angular consumer builds passed development forwarding, same-version reinstall coverage, production token removal, SSR, opt-out, and import-only checks. The publish workflow now runs package and bundle gates before publication. Credential and diff checks passed. Linux/Node 24 library and package gates passed; dry publishing correctly refused the already-published 0.0.65 version. The release version bump follows separately. A live preview package journey accepted four distinct observations and recognized both duplicate runtime requests.The backend in #1004 is merged and deployed. Publication and production activation follow this PR; the controlled real-email and unsubscribe test is deferred to production. Copied, cached, read-only, or script-skipped package directories can retain a token, so correlation does not verify identity or employment.
Clean-checkout verification: source packages include inert null-token modules before any build preparation. Fresh scoped validation passed 429 LangGraph tests, 151 telemetry tests, 268 AG-UI tests, the representative AG-UI cockpit build, and both initial-render and send/receive browser replays. Scoped lint passed with existing warnings. The browser automation regression verifies zero network requests and zero storage reads.