aboutsummaryrefslogtreecommitdiff
path: root/assets/outbox/2026-01-19-remove-zfs-scripts-request.md
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-10 17:54:51 -0500
committerCraig Jennings <c@cjennings.net>2026-07-10 17:54:51 -0500
commitf4123bb61cf7a080dbda7a1c6c6a2eca4d533efa (patch)
tree609b3e621900b09add9294ae25b2c4212ff5e3be /assets/outbox/2026-01-19-remove-zfs-scripts-request.md
parent0dfd713b356374e424afce27fe839c2e86094ac0 (diff)
downloadarchsetup-f4123bb61cf7a080dbda7a1c6c6a2eca4d533efa.tar.gz
archsetup-f4123bb61cf7a080dbda7a1c6c6a2eca4d533efa.zip
docs: fold Craig's spec notes and a review finding into the input-side spec
Craig left four notes on the draft. This closes all of them. He ratified two open decisions: don't rebuild push-to-talk, since the source-mute is the safety property, and read /proc/asound directly for the kernel tier. Both close DONE. He flagged a naming collision. The doctor keys can't be OUTPUT/INPUT, because the CONTROLS section already carries INPUT/OUTPUT mute toggles. They become SPEAKERS and MICROPHONE, with a distinct diagnostic style held consistent across every panel. I recorded it as a new decision and left the visual treatment open for his eye. He asked for a failure-modes map, so the spec gains a table of every fault by probe tier with its verdict and remedy, output and input together. A spec-review had also left two blocking findings. The kernel-to-graph one was real: ALSA card ids and PipeWire node names are different namespaces, so "compare the sets" was undefined. I took the reviewer's coarse rule as the v1 definition. mic-unrecognized fires when the kernel capture set is non-empty and the graph has zero non-monitor hardware sources. Per-device correlation is logged as vNext. That finding closes. The open-decisions one stays until the last three land.
Diffstat (limited to 'assets/outbox/2026-01-19-remove-zfs-scripts-request.md')
0 files changed, 0 insertions, 0 deletions