diff --git a/work/projects/cpm-m3-telemetry-privacy-triage.md b/work/projects/cpm-m3-telemetry-privacy-triage.md index 8a352b39..f6d04a9d 100644 --- a/work/projects/cpm-m3-telemetry-privacy-triage.md +++ b/work/projects/cpm-m3-telemetry-privacy-triage.md @@ -57,7 +57,7 @@ Unavailable optional facts are omitted. Boolean values are `true` / `false`. The recorder keeps 40 events in memory; the pixel includes at most the last 12 and 255 characters, dropping oldest entries first. Format: `event_name@-seconds`, relative to snapshot time. -Events: `load`, `view`, `dealloc`, `unresponsive`, `responsive`, `proxy_on`, `proxy_off`, `died_`, `error_`. Termination reasons: `memory_limit`, `cpu_limit`, `requested_by_client`, `crash`, `shared_crash_limit`, `unknown`. Error events represent background-load failures. Event labels are lowercased, character-filtered and capped at 64 characters. +Events: `load`, `view`, `dealloc`, `unresponsive`, `responsive`, `proxy_on`, `proxy_off`, `died_`, `error_`, `context_unload_failed_`, `extension_files_remove_failed_`. Termination reasons: `memory_limit`, `cpu_limit`, `requested_by_client`, `crash`, `shared_crash_limit`, `unknown`. The `error_` events represent background-load failures. Unload failures during reload, data clearing or uninstall, and file-removal failures during uninstall, are also recorded for the tracked CPM extension. A failed unload preserves the tracked context; file-removal failures can still be recorded after successful unload. Existing standalone error pixels are unchanged; these timeline entries only travel with a later failure/stuck snapshot. Event labels are lowercased, character-filtered and capped at 64 characters. Example: `view@-60,died_crash@-42,error_background_failed_to_load@-41`.