ci logs are a good starting point, but they're noisy and don't give you data you can filter or join across runs. structured test results let you ask which tests fail most, which are slow, and what's getting worse org-wide. now ga in depot.
- tar is sequential and gzip is stream-oriented, so to read one file in a container layer you unpack everything before it. soci adds metadata that lets the runtime seek directly to the bytes it needs.
- deleting from a content-addressable store is trickier than writing to one. you can't re-check s3 and delete in one step, so we record the version gc inspected and delete only that, staying safe even against a concurrent re-push.
- usage events tell you people are using your ai assistant. to see what they're trying to accomplish, you need traces: the user's question, the response, latency, session grouping, and where the conversation started.
- test results are now ga in depot ci and github actions. ingest junit xml from your ci to get pass/fail/error/skip counts on every job, plus org-wide analytics for flaky, slow, and recurring failures.
