fix(doctor): restore compact eleven-row System Doctor - #280
Merged
Conversation
3 tasks
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
System Doctor now reads as one compact status board: every selected subsystem has one green check, red X, or warning, while degraded rows explain the problem and the next useful action. This replaces the repeated
PASS/FAILtranscript and restores the eleven-row Memory Stack Doctor roster, including separate GBrain core and semantic-coverage rows.This corrects the presentation introduced by #277. Private snapshot generation and Telegram delivery remain in SUP-3899; the separate Desktop rendering remains in SUP-3900.
Before and after
Before:
After:
Contract boundary
The structured
jarvos-system-doctor-report/v1receipt and its reason codes remain intact. The exact eleven-row producer roster is nowjarvos-system-doctor-facts/v2; obsolete ten-row v1 snapshots fail closed. A complete v2 roster is authoritative, so the legacy Memory aggregate is not rendered or counted twice.Validation
npm testsuite passed on commit71d79fd.Related: SUP-3896