No org-level view of symbolication failures, and no bulk path to reprocess once symbols are fixed

Problem Statement When symbolication fails, the failure is only visible by opening an individual issue and reading the Images Loaded section. There is no way to answer "which of my issues have unsymbolicated or partially symbolicated frames", and therefore no way to know how much of the crash dashboard is currently unreliable. The recovery path has the same shape. Reprocessing is a per-issue button inside the issue view. After uploading a missing or corrected debug file, there is no way to reprocess everything that was blocked on it. For native teams that upload symbols per build, a missed or late upload can affect thousands of issues, and each one has to be found and reprocessed by hand. The result is that: • Failures are discoverable only one issue at a time, so most are never discovered. • Teams have no measure of symbolication health, so a broken symbol upload in CI can go unnoticed for an entire release. • Fixing the cause does not fix the data, …