Reorganize the repo so it can rebuild the audio hub on any Pi, not just
the live `adac` box:
- README.md: now a project landing page (overview, repo map, deploy
summary) instead of the adac-specific maintenance guide.
- MAINTENANCE.md: the "how it's wired / day-to-day upkeep" guide,
genericized with <pi-host>/<pi-ip>/<lan-cidr>/<desktop-host> placeholders.
- config/: the actual PipeWire/WirePlumber drop-ins as deploy-ready
templates (<VOLT_SOURCE>/<VOLT_SINK>/<LAN_CIDR> placeholders, with the
commands to resolve them in each file's header comment).
- systemd/bt-agent.service, firmware/config.txt.snippet: the remaining
deployable artifacts.
- instances/adac.md: the live deployment's real values (host, IP, Volt
serial, paired phones, history) — the one place machine-specific data
lives.
- RUNBOOK.md: replace the hardcoded LAN subnet with <lan-cidr>.
- root-README.md: genericized; .gitignore keeps local harness settings out.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
README.md: maintenance guide describing how the adac PipeWire audio
hub is wired together — the four audio paths, the five config drop-ins,
services, firmware, and common maintenance tasks. Written as a mental
model for upkeep rather than install/troubleshooting commands.
root-README.md: short redirect telling anyone on the root account to
log in as the `user` account (PipeWire is a per-user service), pointing
to the maintenance guide.
These mirror the files deployed at /home/user/README.md and
/root/README.md on the Pi.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
