Patcher: disclaimer, every mod can be unticked, hot cue docs

- A disclaimer (mods and patcher developed with Claude Code, at your own
  risk) must be accepted by typing yes, or with --accept, before a build.
- Unticking a mod unticks what needs it instead of ticking it back, so
  code can be unticked; hotcuekeys needs cuecolours.
- beatjump starts unticked and is marked with its faults on a player.
- README: the hot cue keys (play, gate, set, delete, LEDs).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

README.md

@@ -5,13 +5,20 @@ the mods you choose, for the player's own USB update.
 
 ```sh
 python cdj900nxs_patcher.py C900NXS.UPD                  # choose in a list
-python cdj900nxs_patcher.py C900NXS.UPD --mods beatjump,cuecolours,hotcuekeys
+python cdj900nxs_patcher.py C900NXS.UPD --mods cuecolours,hotcuekeys
 python cdj900nxs_patcher.py C900NXS.UPD --stock          # the original, to go back
 python cdj900nxs_patcher.py --list
 ```
 
 In the list: **arrow keys** move, **space** ticks or unticks, **a** ticks all
-or none, **enter** builds, **q** quits. Terminals that cannot pass single
+or none, **enter** builds, **q** quits. Ticking a mod ticks what it needs;
+unticking one unticks what needs it (`utility` needs `code`, `hotcuekeys`
+needs `cuecolours`). A mod with known faults starts unticked.
+
+Before anything is built the patcher shows a disclaimer that must be
+accepted by typing `yes` (or with `--accept`, where no one can type): the
+mods and the patcher were developed with Claude Code, Anthropic's AI coding
+assistant, and are used at your own risk. Terminals that cannot pass single
 keys (Git Bash's mintty, a pipe) get a numbered list instead. The result goes
 to `out/<date>-<mods>/C900NXS.UPD` with a `report.txt` of every check.
 
@@ -50,9 +57,23 @@ From the emulator checkout `../CDJ900NXSVirtual` (`--repo` for another place):
 | `code` | arnoldasr: BPM with two decimals, two-line phase meter, RGB waveform |
 | `utility` | arnoldasr: UTILITY > PHASE METER switch (needs `code`) |
 | `overview` | arnoldasr: overview waveform colour gradient |
-| `beatjump` | TRACK SEARCH jumps 1/2/4/8 beats, UTILITY > BEAT JUMP |
+| `beatjump` | TRACK SEARCH jumps 1/2/4/8 beats, UTILITY > BEAT JUMP (known faults on a player, see Risk) |
 | `cuecolours` | memory cues in their rekordbox colours, hot cues shown |
-| `hotcuekeys` | UTILITY > HOT CUE KEYS; QUANTIZE short = hot key mode |
+| `hotcuekeys` | hot cues A-E on the BEAT DIVIDE keys (needs `cuecolours`), see below |
+
+`hotcuekeys`: UTILITY > HOT CUE KEYS ON; then QUANTIZE pressed briefly
+switches the hot key mode (HOT KEYS box beside QUANTIZE), held it is
+QUANTIZE. In the mode the BEAT DIVIDE keys 3/4, 1/3, 1/2, 1/4, 1/8 are hot
+cues A-E:
+
+- press: jump to the hot cue and play (from pause too);
+- hold 0.5 s or longer, then let go: back to the hot cue, standing (gate);
+- an empty key held 0.8 s while paused: a hot cue there;
+- DELETE held, a key pressed: its hot cue deleted (DELETE alone is DELETE);
+- LEDs: off without a hot cue, dim with one, two bright blinks when pressed.
+
+Hot cues set or deleted live until the next track load; nothing is written
+to the USB stick. As with CALL, the CUE point moves to the hot cue.
 
 arnoldasr's mods need his repository checked out in
 `../CDJ900NXSVirtual/mods/cdj900nxs/upstream` (it has no licence, so it is
@@ -61,7 +82,10 @@ not copied here); without it they are greyed out.
 ## Risk
 
 Nothing here talks to a player; you copy the file to a FAT32 USB stick and run
-the update yourself. Our mods have only run in the emulator. Recovery from an
+the update yourself. Our mods were developed with Claude Code in an emulator.
+On a player: `beatjump` jumped off the grid and, after a few jumps, reported a
+corrupted file and needed a restart; it is being reworked. `cuecolours` and
+earlier versions of `hotcuekeys` ran on a player. Recovery from an
 application that crashes at start-up has not been tested by anyone. Keep the
 `--stock` file at hand.