+ lHj!jRt^RIt^RIHtHt]P !]4t]!4t]Pt ]Pt RRlt RRlt R(Rlt] !R4] R R l44t] !R 4] R R l44t] !R4] RRl44t] !R4] RRl44t] !R4] RRl44t] !R4] RRl44t] !R4] RRl44t] !R4] RRl44t] !R 4] R!R"l44t] !R#4] R$R%l44tR&R'ltR#))uShared-metrics consent JSON-RPC handlers (the Desktop twin of ``hermes setup``'s Shared Metrics section). Both opt-ins live in the focused profile's config.yaml exactly where the wizard writes them — ``telemetry.shared_metrics.enabled`` (local collection) and ``.send`` (daily upload) — so the CLI and the app can never disagree about the answer. ``shared_metrics.set`` enforces the wizard's invariant (sending needs collection) and reconciles the consent windows in the local store on every change, through the same single writer the wizard uses. Bodies are rebound onto server.py's globals (method_ctx.bind_module) and reference them bare. N)HandlerRegistry bind_modulec$V^8dQhR\/#)returndict)formats"G/home/ubuntu/.hermes/hermes-agent/tui_gateway/methods_shared_metrics.py __annotate__r sDc^RIHpV!V4#)z^The one ``{enabled, send, decided, reask}`` reading every surface shares (CLI offer included).) consent_state)/hermes_cli.observability.shared_metrics_consentr)cfgrs& r _shared_metrics_consentrsM  r cV^8dQhRR/#rrN)r s"r r r suu4ur c ^RIHp\V\4'dVP R4MRp\V\4'dVP R4MRpT!R\V\ 4'd V'dTMRR7R#)zDesktop has no setup-finish RPC; this first-run answer is the one backend call made once, right after onboarding settles. A no-op (inside the events API) unless collection is on.)record_setup_completedmodelNproviderdesktop)surfacer).hermes_cli.observability.shared_metrics_eventsr isinstancergetstr)rrrrs& r &_shared_metrics_record_setup_completedrs]V *3 5 5CGGG 4E(25$(?(?uyy$TH9:hX[C\C\aixostr c^RIHpV!WPR4VPR4VPR4VR7R#))record_model_friction session_keyagent profile_home) session_idr$ hermes_hometurnsN)-hermes_cli.observability.shared_metrics_modelr"r)signalsessionr(r"s&&& r _tui_model_frictionr,%s2S;;}5W[[=QKK/u>r zshared_metrics.statusc0V^8dQhR\R\/#rparamsrr)r s"r r r .s''4'D'r c\V\\444# \d!p\ TR\ T44uRp?#Rp?ii;i)z``{enabled, send, decided, reask}`` for the focused profile. A pure read of config.yaml (no defaults merged, so ``decided`` sees only what the user wrote).iN)_okr _load_cfg Exception_errr)ridr/es&& r _r7,s? '3/ <== 'Cs1v&&'s A AA A zshared_metrics.setc0V^8dQhR\R\/#r.r)r s"r r r 9s2242D2r cVPR4RJpT;'dVPR4RJp^RIHp\4pV!WRV4\ V4^RIH pT!TR7T'g'^R I H p^R I H p ^R IHp T!4T !T !44TPR 4RJd \!T4\#T\%T44# \ d!p\ TR\T44uRp?#Rp?ii;i) apWrite both opt-ins at once and reconcile the consent windows. ``send`` is forced off when ``enabled`` is off (the wizard's rule: sending cannot outlive collection, and turning collection off withdraws send consent). ``first_run`` marks the Desktop first-run answer, which also records the setup-completed metric. Answers the stored ``{enabled, send, decided, reask}``.enabledTsend) set_answeriN)_record_send_consent_change)r:)purge_onboarding_latches)purge_pending_receipts)get_hermes_home first_run)rrr< _load_cfg_raw _save_cfgr3r4rhermes_cli.setupr=/hermes_cli.observability.shared_metrics_desktopr>/hermes_cli.observability.shared_metrics_processr?hermes_constantsr@rr1r) r5r/r:r;r<rr6r=r>r?r@s && r r7r77sjj#t+G  1 1vzz&)T1DJ'o3&#=- \Z4 "01 zz+$&.s3 s+C0 11 'Cs1v&&'sC C3C.(C3.C3zshared_metrics.slash_commandc0V^8dQhR\R\/#r.r)r s"r r r X""4"D"r c^RIHpT!\VPR4;'gR4\ 4R7\ VRR/4#)aThe Desktop and Ink TUI dispatchers call this once per user-typed slash command, locally handled ones included; the gateway never counts slash.exec / command.dispatch itself, so each command lands exactly once. Always ``{ok: true}`` (the events API never raises).)record_slash_commandcommand)rLrokT)rrKrr_resolve_session_platformr1)r5r/rKs&& r r7r7Vs= TVZZ %:%@%@b!AKdKfg sT4L !!r zshared_metrics.startup_latencyc0V^8dQhR\R\/#r.r)r s"r r r ds " "4 "D "r c^RIHpT!VPR4;'g \4VPR4VPR4R7\ VRR/4#)a[The Ink TUI (gateway ready) and Desktop (backend attached) each report their own launch -> ready time once per launch; ``launch_id`` latches it here too, so a reconnect to this backend never re-counts. A Desktop on a URL/cloud backend has no ``HERMES_DESKTOP`` here, so the client's declared surface wins over env detection. Always ``{ok: true}``.)record_rpc_startup_latencyr elapsed_ms launch_id)client_surfacerSrTrNT)/hermes_cli.observability.shared_metrics_startuprRrrOr1)r5r/rRs&& r r7r7bsV[zz),KK0I0KX^XbXbcoXp**[) sT4L !!r zshared_metrics.update_runc0V^8dQhR\R\/#r.r)r s"r r r us " "4 "D "r c ^RIHpV!VPR4VPR4VPR4VPR4VPR4R7\VRR /4#) zDesktop reports each packaged self-update once (a pending record survives the restart that applies it and is sent on the next backend attach). Always ``{ok: true}``.)record_desktop_updateoutcome failed_stage duration_ms mechanismfrom_commit_date)rZr[r\r]r^rNT).hermes_cli.observability.shared_metrics_updaterYrr1)r5r/rYs&& r r7r7ss^ U 9%FJJ~4NJJ}-K9P$67 sT4L !!r z"shared_metrics.desktop_feature_usec0V^8dQhR\R\/#r.r)r s"r r r ""4"D"r cZ^RIHpV!VPR4R7\VRR/4#)zDesktop reports each area the user opened, at most once per UTC day (latched on both sides). Always ``{ok: true}``; a no-op unless shared metrics are on.)record_desktop_feature_usearea)rdrNT)rErcrr1)r5r/rcs&& r r7r7s* [FJJv$67 sT4L !!r zshared_metrics.desktop_frictionc0V^8dQhR\R\/#r.r)r s"r r r rar cz^RIHpV!VPR4VPR4R7\VRR/4#)zOne Desktop friction event (dismissed notice, error toast by category, renderer crash, backend disconnect, slow frame), capped per day. Always ``{ok: true}``.)record_desktop_frictionkinddetail)rhrirNT)rErgrr1)r5r/rgs&& r r7r7s5 XF!3FJJxrs4   8 $     **u> '!'22:&'"("() "* "#$ "% ",-".")*"+"+,"-"()"*"&' ,( ,0r