docs(o11y): record production verification results in ADR-0041

[demtario]

Context

Records the production verification done 2026-09-29 to 2026-10-01 (DEV-3093, DEV-3178) in ADR-0041 §L: criteria 5, 9 and 11 now carry production evidence, criterion 8 gets the production export comparison, and criterion 13 notes the production lifecycle rules read back. ADR-0041 and ADR-0042 stay Proposed on purpose, pending two readings from Mateusz (inbox retention on or after 2026-10-06, monthly exported-logs count around 2026-10-03/04); the flip to Accepted is a follow-up docs change.

Types of changes

• README / documentation change
• New example
• Update to an existing example
• Demo runner (runner/) change
• CI / tooling change

How was this verified?

Docs only. Every figure was checked against the DEV-3093 and DEV-3178 task text, which holds the evidence (alarm CPU p99.9 22.6 ms, 25 ms in the tail, Worker memory 9.04 MB, idle stop 14.3 to 15.3 min, the criterion 11 trigger and Ray id). No code touched.

Checklist

• Not a new or renamed example, so no frameworks.json or README table change
• No example or server-example touched, so no build needed

Related issue(s):

1. DEV-3093
2. DEV-3178

---

Note

Low Risk
Documentation-only updates to ADRs and the launch runbook; no runtime, deploy, or observability code paths are modified.

Overview
Documentation update for the first production o11y verification pass (2026-09-29–2026-10-01). No application code changes.

ADR-0041 status and §L exit-criteria table now record production evidence for symbolication (5), idle Grafana tab (9), and worker errors → Loki (11); volume (8) adds a same-hour Loki vs Analytics Engine check and notes the monthly o11y-logs count is still pending; retention (13) documents production lifecycle rules read back and keeps calendar expiry as the open item. The ADR remains Proposed until two dated production readings: inbox objects older than 7 days (on/after 2026-10-06) and monthly exported-logs count (~2026-10-03/04), tracked in DEV-3178. The blocker for criterion 5 shifts from “no isolate profiling” to documented CPU/memory readings (DO memory still not measured).

ADR-0042, the ADR index, and run-and-deploy.md Launch plan are aligned: pending items are the same two readings; post-deploy smoke items 3 (idle tab) and 7 (symbolication) are marked Done with dates pointing at §L.

^{Reviewed by Cursor Bugbot for commit f4ec919. Bugbot is set up for automated code reviews on this repo. Configure here.}