fix: align Heart score and repairs with all monitored checks - #268
Merged
Merged
Conversation
This was referenced Oct 2, 2026
Jammy2211
marked this pull request as ready for review
October 2, 2026 09:07
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
A Heart dashboard with advisory failures and missing observations could show 100 and its systematic repair workflow could stop at release GREEN. The headline now shows a complete monitoring score, and the existing repair button uses the same inventory to cover every check family and configured repository, including findings beyond display limits.
Each family deducts its worst unresolved status (red 10, yellow 5, missing/expired evidence 2). A perfect score requires fresh green evidence for every applicable check; explicit permanent exclusions remain visible as N/A. Readiness and its release gate stay separately labelled. On captured published evidence, monitoring reads RED/42 while release readiness stays GREEN/100.
Collector timestamps, full local publication, private-finding placeholders, and baseline coverage prevent gaps from disappearing or old measurements being refreshed by aggregation. This does not repair the underlying advisory issues or run expensive checks; the expanded action now identifies and routes them.
Closes #267. Companion PyAutoLabs/PyAutoBrain#446 is required first because the repair prompt invokes its new dashboard scope.
API Changes
Adds
board.monitoringschema 1: score, status, complete, counts, full checks/findings, and penalty breakdown. Legacyboard.verdict,score, andpenaltiesretain release meanings; headline HTML/terminal/Markdown/badges use monitoring. Cockpitstate.statusremains the release verdict; its headline/items also report monitoring. No scientific library/workspace migration.Test Plan
Full API Changes (for automation & release notes)
Removed
None. The retired workspace-testmode collector is excluded from expected coverage; existing observations still remain visible.
Added
heart.monitoring.assessand additive collector observation timestamps; complete monitoring data in published local sections and sanitized local repository evidence.Migration
Read
monitoring.scorefor whole-dashboard health andscore/verdictfor release readiness. Read the fullmonitoring.findingsfor repair coverage. Refresh older undated collector evidence and republish the dev-box inventory; these remain explicit gaps until measured. All changes are additive for machine consumers except intentionally relabelled human-readable monitoring headlines/badges.