fix(admin): distinguish unavailable diagnostic archives - #8
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Admin reports could advertise an attached diagnostic ZIP whose private object was missing, then return a misleading report-not-found error. Keep attachment history, expose archive availability separately, show unavailable or unknown storage states, and return a specific 503 response when the report exists but its archive is missing.
Update the API contract and storage deployment guidance. Existing clients retain the
hasDiagnosticsfield, and the UI remains compatible with servers that omit the additive availability field.Advances #7. This does not recover missing archives or establish why production storage lost them.
Validation: all Go tests passed; all 10 frontend tests passed, including real admin-view availability states; the production TypeScript/Vite build passed. No customer messages were sent and no deployment was performed.