[Epic] Keep CI, release, telemetry, compliance, and engineering systems healthy

## Problem statement

Build, validation, evaluation, release, telemetry, dashboards, repository governance, and dogfood cleanup operate as internal services. Failures create release risk and recurring maintenance toil.

## Outcome

Engineering systems remain reliable, observable, compliant, and capable of supporting predictable releases.

## Goals

- Maintain CI, evaluation, release, sync, and marketplace reliability
- Keep dashboards and telemetry useful and privacy-conscious
- Address repository governance, attestations, and test-resource residue
- Automate recurring operational work safely

## Non-goals

- Product feature development unrelated to engineering health
- Collecting telemetry without a defined operational question

## Success criteria

- [ ] Critical pipelines meet agreed reliability targets
- [ ] Failures have ownership and actionable diagnostics
- [ ] Compliance and cleanup obligations are completed on schedule

## Dependencies

GitHub Actions, release and marketplace systems, telemetry, storage, dashboards, and repository governance.

No file, test, or entry point is identified. Start by breaking the epic into the stated CI, release, telemetry, compliance, and cleanup goals, then inspect the referenced GitHub Actions, release and marketplace systems, dashboards, and repository governance processes. Done requires assigned ownership, actionable diagnostics, reliability targets, and scheduled compliance and cleanup work.

Written by the indexing model from the issue text.