Skip to content

fix: align Heart score and repairs with all monitored checks - #268

Merged
Jammy2211 merged 1 commit into
mainfrom
feature/heart-monitoring-coverage
Oct 2, 2026
Merged

Jammy2211 merged 1 commit into
mainfrom
feature/heart-monitoring-coverage

Conversation

@Jammy2211

Copy link
Copy Markdown
Contributor

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.monitoring schema 1: score, status, complete, counts, full checks/findings, and penalty breakdown. Legacy board.verdict, score, and penalties retain release meanings; headline HTML/terminal/Markdown/badges use monitoring. Cockpit state.status remains the release verdict; its headline/items also report monitoring. No scientific library/workspace migration.

Test Plan

  • Full Heart suite: 1168 passed; collector timestamp tests: 34 passed.
  • Full Brain suite: 1141 passed; real Heart JSON consumed by dashboard scope stays incomplete despite release GREEN.
  • Tests cover complete green, adverse/missing/expired evidence, partial baselines, zero comparisons, nested optional CI, rows beyond display caps, stable identities, private publication, and complete published evidence.
  • Existing release readiness tests pass; authoritative vitals GREEN at ship time.
  • Tenant firewall and whitespace checks pass; independent bounded review has no remaining blockers.
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.assess and additive collector observation timestamps; complete monitoring data in published local sections and sanitized local repository evidence.

Migration

Read monitoring.score for whole-dashboard health and score/verdict for release readiness. Read the full monitoring.findings for 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.

@Jammy2211 Jammy2211 added the pending-release Awaiting a published release label Oct 2, 2026
@Jammy2211
Jammy2211 marked this pull request as ready for review October 2, 2026 09:07
@Jammy2211
Jammy2211 merged commit aa358d3 into main Oct 2, 2026
2 checks passed
@Jammy2211
Jammy2211 deleted the feature/heart-monitoring-coverage branch October 2, 2026 09:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pending-release Awaiting a published release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: cover all Heart monitoring in score and systematic repairs

1 participant