fix: preserve quality reports in scheduled audit completion - #6809
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
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.
Summary
Scheduled audits could finish without saving dashboard quality: the issue-only completion workflow asked for a one-line summary despite the audit mission requiring a structured report. Preserve required reports in that workflow and add an explicit, category-specific sentinel handoff for both TUI and CLI audit agents.
Explain why completed maintenance may have no saved assessment, and distinguish saved but excluded evidence from an app that has never been assessed. Existing scoring thresholds remain unchanged; historical runs without reports cannot supply a score.
Test plan