[rahul-sinha1908]

Part 4 of 5. Unblocked — idivarts/shared-constants#11, idivarts/shared-libs#83 and idivarts/shared-uis#84 are merged, and the pointers here now sit on their dev commits (f9bc03b, 4d64fb4, e294276). Typecheck re-run against the merged submodules: clean. Only idivarts/backend-sls#421 is still open, and it is independent of this one.

Implements the reviewed funnel spec. 60 files.

Why this is mostly structure, not sixty track() calls

The audit found several events that already existed but fired from paths production never takes — brand_created fires only on the legacy landing screen, and before the API call, so a failed creation counted as a brand. Rather than add more of those, the navigation and the choke points do the reporting:

New file	What it owns
utils/billing-navigation.ts	goToBilling(source) — all 14 upgrade CTAs
utils/social-navigation.ts	the 5 doors into Connected Accounts
utils/social-connect-attempt.ts	the attempt, parked across the OAuth round trip
utils/strategy-funnel.ts	start→formed timing, across a navigation
utils/follower-bucket.ts	bucketing, so no raw follower count is reported
constants/PlanPricing.ts	one price number for the table and the event

goToBilling is the main one. Fourteen sites called router.push("/billing") and none recorded the click — and fourteen hand-written calls would rot the moment a fifteenth door shipped. It also carries ?from=, so paywall_viewed.trigger finally names the door; it had two possible values for fourteen doors, so it could not say why anyone was looking at pricing.

The menu is two calls, not forty. DrawerMenuItem and components/menu each funnel every entry through one handler. Both report before the lock check — a tap on a plan-gated row is the highest-intent signal the menu produces, and the early return meant it produced nothing at all.

AIModelSelector gains surface / task props (5 call sites). All five chat surfaces mount the same component, so without them every model action reported identically. task matters because one stored preference is resolved per task.

Two defects fixed, both found while instrumenting

• calendar_item_rescheduled was over-counting. It fired in MonthView before calling the move, but the screen silently rejects scheduled/posted content — so every rejected drag counted as a successful reschedule. Reporting moved to handleMoveItem, the only place that knows the outcome. The rejection also now explains itself rather than the chip springing back in silence.
• The analytics empty state was a dead end — it told the user to connect an account and gave them no button. It has one now.

subscription_started finally carries revenue

The registry has always declared value / currency; the watcher never passed them, so the primary conversion event reported no revenue and nothing downstream could bid or report on value. Prices moved to constants/PlanPricing.ts so the pricing table and the event read one number. The file says plainly that the real fix is server-side emission from the webhook — only that sees proration, coupons and tax.

Verification

• tsc --noEmit clean.
• jest: 163 passing. Three suites in shared-libs/firestore/crowdy-chat/tests fail to load on a missing @firebase/rules-unit-testing dev dependency — pre-existing, in files this PR does not touch, and the package is not in package.json.
• Registry cross-check: 82 declared, 78 fire here, 3 from backend-sls, 1 deliberately deferred.

Not verified in a simulator — per the repo's standing note, local iOS builds are unusable on this machine, so CI is the first real build.

🤖 Generated with Claude Code