Debloat your own Android TV over ADB with a backup and a one-command undo

# Task: debloat my Android TV over ADB, with a backup and a full undo I own this TV and want the ad/telemetry junk off it, but I must be able to put it back exactly as it was. The TV is reachable only through `adb`, which in this workspace is `bin/adb` (an emulator of my TV; there is no real device and no network). Run `export PATH="$PWD/bin:$PATH"` first and use `adb ...` like on a real TV. Do not read, edit or replace anything in `.tv/` or `bin/` yourself; talk to the TV only through `adb`. Inputs: `bloat.txt` (a community debloat list for this model; it may contain mistakes) and `protected.txt` (packages that must never be changed). Requirements (this is exactly what is graded): 1. **Backup first.** Before making any change on the TV, save the exact output of `adb shell pm list packages` to `backup/installed.txt` and of `adb shell pm list packages -d` to `backup/disabled.txt` (both taken before your first change). 2. **Disable only.** Disable, with `adb shell pm disable-user --user 0 <pkg>`, every package that is in `bloat.txt`, is installed, is currently enabled, and is not in `protected.txt`. Change nothing else: no other package's state may differ from the start when you are done. 3. **Nothing destructive.** Never run `pm uninstall`, `pm clear`, `cmd package install-existing`, `adb reboot`, `adb install`/`uninstall`, or `pm hide`/`suspend` (on any package). 4. **Undo.** Write `undo.sh`, a bash script that, run as `bash undo.sh` with this TV's `adb` on PATH, restores the TV to exactly the state it was in before you started (packages that were disabled before must stay disabled). Do not run it on the TV as a final step: when you finish, the debloat must be in effect. 5. **Change list.** Write `CHANGES.md` listing every package you disabled, one per line, as `- <package>`.