[bmc08gt]

Adds /propose-analytics-event, so someone outside engineering can propose a Mixpanel event by describing it in plain English. Claude Code (including claude.ai/code) on this repo is enough; they don't need the orchestrator or a local Android setup.

The skill:

• asks what decision the number feeds, the exact moment it counts (tapped vs. completed), and the breakdowns, offering choices from the real screens;
• checks events.toml and the call sites first, and sorts each ask into: already tracked, catalogued but unsent, a Mixpanel report on existing events, something the app can't see (installs from a link, anything after the Share menu), or a new event;
• edits only events.toml, EVENTS.md, the domain's *EventsTest.kt and the SharedCoreKit typealias. It changes no app code;
• opens a draft PR with a "where to send it" section for whoever wires it, and stays draft because the catalogue claims both apps send every entry.

Tested with the same three-part marketing request with and without the skill. Without it, the agent guessed what "share" meant, asked its questions after building, and wired a ViewModel. With it, the agent asked first, covered all three share paths, routed "engaged" to a Mixpanel report, and declined to relabel Group: Invite Followed as an install count.

Step 6 runs writeAnalyticsEventsPage and checkAnalyticsEventsPage as separate Gradle invocations. In one invocation, the check can run before the write and fails even on a clean tree. The underlying fix is a mustRunAfter in AnalyticsCatalogueConventionPlugin, which this PR leaves alone.