Repository navigation
Conversation
|
No API key found for Claude Opus. It needs Connect a provider → · Pick another model →
|
There was a problem hiding this comment.
All reported issues were addressed across 5 files
Tip: Get a Slack DM when cubic finishes reviewing your PRs. Connect Slack
Re-trigger cubic
|
No API key found for Claude Opus. It needs Connect a provider → · Pick another model →
|
|
No API key found for Claude Opus. It needs Connect a provider → · Pick another model →
|
|
No API key found for Claude Opus. It needs Connect a provider → · Pick another model →
|
|
No API key found for Claude Opus. It needs Connect a provider → · Pick another model →
|
There was a problem hiding this comment.
All reported issues were addressed across 1 file (changes from recent commits).
Requires human review: Auto-approval blocked because this review re-detected 1 unresolved issue already reported by Cubic.
Re-trigger cubic
|
No API key found for Claude Opus. It needs Connect a provider → · Pick another model →
|

Adds a bounded
superdoc_cta_clickedevent to existing first-party analytics for SuperDoc referral, pricing and signup CTA clicks. It records project/destination/placement enums and fixed event-scoped page context; it does not add another tag, document content, raw link/query/referrer values or a completed-signup/payment claim.Either modern or legacy DNT, GPC and explicit opt-out suppress the added event. Source projects require own-key membership, only supported quickstart paths are classified as quickstart, ordinary in-docs navigation is excluded, and client-side routing keeps its normal navigation behavior. The listener tests retain distinct callbacks and check specific cleanup and untouched navigation.
Validation: all 11 focused tests pass and now run explicitly in regular CI. Full Linux check, typechecks, existing test lanes, CLI build and web/prerender build pass on cf5c51e. The separate pullfrog integration still lacks its credential in the fork; no secret has been exposed or check bypassed. Maintainer review/deployment and a production DebugView/opt-out journey remain required. This is CTA intent only; authoritative signup, activation and payment callbacks are separate rollout work.