[2026-11-03] eagle: work/projects/cpm-project-summary-2026-11-03.md

work/projects/cpm-project-summary-2026-11-03.md

@@ -78,11 +78,20 @@ This week, cleanup:
   - Keep the fix and the flag as a kill-switch for now (remove after 2-3 releases without issues): [cpmNetworkProcessRecovery](https://app.asana.com/1/137249556945/task/1219701603183695?focus=true), [cpmStableBaseURL](https://app.asana.com/1/137249556945/task/1219728649844711?focus=true), [webExtensionStateRestorationGate](https://app.asana.com/1/137249556945/task/1218931841045393?focus=true), [cpmBackgroundLoadRestart](https://app.asana.com/1/137249556945/task/1219970564251181?focus=true).
 - [Pixel data cleanup](https://app.asana.com/1/137249556945/task/1220159402040630?focus=true): remove the temporary pixels and episode parameters that only served the investigation.
 
-Next, metrics:
+Next, metrics (tasks to create):
 
-- Permanent breakage metrics: a small fixed set, rates against DAU, added to the health indicators dashboard. Task to create.
-- Extension lifecycle metrics: find where the startup message stops, to diagnose the wake failures. Needs privacy review and releases, data in 1-2 release cycles. Task to create.
-- Data check of the Nov/9 fixes: [Analyze attribution data after stage 3](https://app.asana.com/1/137249556945/task/1220159402040627?focus=true).
+- Permanent breakage metrics, replace the temporary pixels. Goal: track the permanent failure rate against DAU after the project closes.
+  - Episode report, trimmed to: outcome, tabs affected, repeat count, reload state, cause group (wake, load, update, error 6, tab not connected, other), platform and OS. Same shape on iOS and macOS.
+  - Healthy-navigation baseline: a 1% sample of navigations reports whether the extension answered and in which time bucket. Gives failures per navigation, not only per user.
+  - Health indicators dashboard: permanent failures, any failures, one-tab and browser-wide, per platform and version, against the 1% target.
+  - Old and new reports published together for one release, so the trend is not lost. Then the old ones go.
+- Extension lifecycle metrics, to find where init on wake breaks. Goal: for init on wake failures, say at which step the chain stops.
+  - Stage ledger: the extension reports the last step reached for each navigation. Steps: page script injected, init sent by the page, init received by the background, config read from storage, app checks done (autoconsent on, feature on), dashboard update sent to the app, answer sent to the page, answer received by the page, response received by the app.
+  - Added to the failure report: last step reached and time spent in it.
+  - Background probe at failure time: is the background alive, does it answer a ping, how fast. Needs a spike first: does the probe see the background's state, and does it keep the background awake.
+  - Background lifecycle counters in the report: why it started (wake or load), age bucket, number of wakes in the session.
+  - Work: extension JS changes to send the steps, app changes to collect them, privacy review, extension and app releases. Data in 1-2 release cycles.
+- Data check of the Nov/9 fixes: [Analyze attribution data after stage 3].
 
 Open: