aboutsummaryrefslogtreecommitdiff
path: root/scripts/testing/tests/test_hardening.py
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-10 23:07:14 -0500
committerCraig Jennings <c@cjennings.net>2026-07-10 23:07:14 -0500
commitd3f5874d89cbaf3190132a510df098d12bbd9358 (patch)
tree1059d75796b3fc179b5d25ab93ee8a4bf40db80d /scripts/testing/tests/test_hardening.py
parent4ca80d788246aeab024bb2f5d18a1819ddfb1d15 (diff)
downloadarchsetup-d3f5874d89cbaf3190132a510df098d12bbd9358.tar.gz
archsetup-d3f5874d89cbaf3190132a510df098d12bbd9358.zip
docs: triage the audio failure catalogue into remedy classes
I sorted both directions into nine symptom clusters each, every entry tagged Auto, Privileged, Reboot-tail, or Guide under the privilege model. The clusters mirror the doctor's probe ladder, so the boundary between what it fixes and what it can only guide falls along the tiers it already probes. Two findings are worth keeping. The buildable core reduces to five primitives on both sides (set-default, set-card-profile, unmute, restart-services, config-drop-in), so the breadth is in the diagnosis, not the remedies. And the clusters imply three new read-only probes: dmesg-pattern hints, an unmute-doesn't-stick signature, and a re-probe-after-idle.
Diffstat (limited to 'scripts/testing/tests/test_hardening.py')
0 files changed, 0 insertions, 0 deletions