Summarize work done after `doctor run` and what to do fix

I was testing out some of the recent work on our config/scripts, and had some failures during it. The failures do stick out thanks to color output, but I think it doesn't do enough to call out what failed and what to do next.

The ERROR Action Help does some info, but is lost in the noise of other output.

Should it also be suggested to re-run?

 INFO Check initially failed, fix was successful, group: "postgres", name: "postgres"
ERROR Check failed, no fix provided, group: "nvm", name: "nvm"
ERROR Action Help: Check that ~/.yall/init.sh is in your shell profile, group: "nvm", name: "nvm"
 WARN Check `node` was skipped.
 WARN Check `node` was skipped.
 WARN Check `yarn-install` was skipped.
 INFO Check was successful, group: "rbenv", name: "rbenv"
 INFO Check was successful, group: "ruby-version", name: "ruby-version"
You are replacing the current local value of build.libxml-ruby, which is currently "--use-system-libraries=true --with-xml2-include=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/libxml2"
You are replacing the current local value of build.pg, which is currently "--with-cflags=-Wno-error=implicit-function-declaration --with-pg-config=/opt/homebrew/opt/postgresql@13/bin/pg_config"
 INFO Check initially failed, fix was successful, group: "bundler", name: "bundler"
 INFO Check initially failed, fix was successful, group: "bundle-install", name: "bundle-install"
Deprecation warning: Expected string default value for '--serializer'; got true (boolean).
This will be rejected in the future unless you explicitly pass the options `check_default_type: false` or call `allow_incompatible_default_type!` in your code
You can silence deprecations warning by setting the environment variable THOR_SILENCE_DEPRECATION.
I, [2024-03-27T13:40:08.996550 #8346]  INFO -- ddtrace: [ddtrace] DATADOG CONFIGURATION - PROFILING - {"profiling_enabled":false}
I, [2024-03-27T13:40:08.996831 #8346]  INFO -- ddtrace: [ddtrace] DATADOG CONFIGURATION - CORE - {"date":"2024-03-27T13:40:08-04:00","os_name":"arm64-apple-darwin23","version":"1.18.0","lang":"ruby","lang_version":"3.3.0","env":"development","service":"rails","dd_version":null,"debug":false,"tags":null,"runtime_metrics_enabled":false,"vm":"ruby-3.3.0","health_metrics_enabled":false}
Created database 'myapp_development'
Database 'myapp_development' already exists
Created database 'myapp_test'
 INFO Check initially failed, fix was successful, group: "dev-databases", name: "dev-databases-exist"
Deprecation warning: Expected string default value for '--serializer'; got true (boolean).
This will be rejected in the future unless you explicitly pass the options `check_default_type: false` or call `allow_incompatible_default_type!` in your code
You can silence deprecations warning by setting the environment variable THOR_SILENCE_DEPRECATION.
I, [2024-03-27T13:40:17.300629 #8537]  INFO -- ddtrace: [ddtrace] DATADOG CONFIGURATION - PROFILING - {"profiling_enabled":false}
I, [2024-03-27T13:40:17.300921 #8537]  INFO -- ddtrace: [ddtrace] DATADOG CONFIGURATION - CORE - {"date":"2024-03-27T13:40:17-04:00","os_name":"arm64-apple-darwin23","version":"1.18.0","lang":"ruby","lang_version":"3.3.0","env":"development","service":"rails","dd_version":null,"debug":false,"tags":null,"runtime_metrics_enabled":false,"vm":"ruby-3.3.0","health_metrics_enabled":false}
 INFO Check initially failed, fix was successful, group: "dev-databases", name: "dev-databases-schema"
Deprecation warning: Expected string default value for '--serializer'; got true (boolean).
This will be rejected in the future unless you explicitly pass the options `check_default_type: false` or call `allow_incompatible_default_type!` in your code
You can silence deprecations warning by setting the environment variable THOR_SILENCE_DEPRECATION.
 INFO Check initially failed, fix was successful, group: "dev-databases", name: "dev-databases-migrations"
 INFO More detailed logs at /tmp/scope/scope-root-20240327-TNWg.log

Start by running doctor run and reviewing how the existing ERROR Action Help output is produced for failed checks. Reproduce the mixed output shown in the issue, then determine how a concise summary of failures and next steps, including whether to rerun, should appear. Done means the important failures and recommended action are visible without being lost among command logs.