{ "title": "Fix the status-downgrade bug so a warning can never mask an error", "objective": "Stop a later check's status=\"warning\" from overwriting an earlier check's status=\"error\" in check_and_enable_services, which made genuinely broken services report as warnings and then never get repaired. Found while writing the split's tests and deferred out of 9085a4e5 because it changes live enforcement; the user asked for it to be fixed.", "acceptance_criteria": [ "No bare `status=\"warning\"` assignment remains in any check lib; every one is guarded by `if [[ $status != \"error\" ]]`, matching the idiom already used in services_apps.sh and services_browser.sh.", "A timer that is BOTH disabled and inactive records \"error\" and triggers its setup script, demonstrated by an A/B run against a simulated broken machine rather than only by assertion.", "The regression is covered by tests that FAILED before the fix and pass after it.", "lib/tests/run_all.sh passes with no failures.", "services_units.sh keeps 100% line coverage.", "Every file including the test files stays at or under 250 lines.", "shellcheck reports zero findings and no suppression is added." ], "out_of_scope": [ "The 5 sites that were already correctly guarded.", "Changing which statuses report_and_fix acts on: the fix makes the status correct rather than widening the repair gate.", "The kcov attribution artifact on services_hosts.sh, diagnosed in the previous commit's evidence." ], "verifier": "lib/tests/run_all.sh (222 assertions), an A/B of check_midnight_shutdown against a disabled+inactive timer with and without the guards, bash meta/scripts/shell_coverage.sh lib/tests/run_all.sh services_units.sh 100, grep for unguarded sites, shellcheck, and check_file_length.sh --all." }