Attribute every telemetry event to the deployment it concerns (#811)

Author: fiskus

Cargo.lock

@@ -9,6 +9,12 @@
 <!-- markdownlint-disable MD013 -->
 # Changelog
 
+## [v0.20.0-alpha4] - 2026-07-30
+
+### Changed
+
+- Usage analytics and crash reports now record which Quilt deployment an action concerned, so activity can be read per stack, and opening a folder is reported as three distinct actions (a package's directory, the sync home, the app data directory) instead of one event that could not tell them apart; actions that concern no deployment record none rather than an inherited one
+
 ## [v0.20.0-alpha3] - 2026-07-29
 
 ### Changed

quilt-sync/CHANGELOG.md

@@ -1,6 +1,6 @@
 [package]
 name = "quilt-sync"
-version = "0.20.0-alpha3"
+version = "0.20.0-alpha4"
 authors = ["Quilt Data, Inc."]
 description = "Cross-platform desktop application for editing Quilt data packages"
 documentation = "https://docs.quiltdata.com"

quilt-sync/src-tauri/Cargo.toml

@@ -1,6 +1,18 @@
 //! Tauri IPC commands, grouped by domain. Everything is re-exported at
 //! `commands::*` so `main.rs`'s `generate_handler!` list and other callers
 //! keep the flat `commands::<name>` paths.
+//!
+//! # The `uri` argument some commands take but never use
+//!
+//! A package operation is addressed by its `namespace`; several also accept the
+//! package `uri` the calling surface rendered from, and do nothing with it but
+//! read its catalog into the event's payload for
+//! [telemetry attribution](crate::telemetry::Telemetry::track).
+//! It is passed rather than resolved from local lineage on purpose: the catalog
+//! the user acted on is what the analytics question asks about, and deriving it
+//! here would add I/O and a failure path to every tracked action — including one
+//! that would have to run *before* an uninstall destroys the lineage it reads.
+//! See [`crate::telemetry::event::PackageEvent::for_uri`] and its siblings.
 
 mod auth;
 mod commit_data;