1# Demo and sandbox scripts
2
3- `run.sh`, `demo.tape`, `smoke.tape`: VHS demo recording.
4- `sandbox-run.sh`: automated acceptance. Client and two remotes all run in
5  containers on an internal network.
6- `test-remotes.sh`: two containerised remotes for manual testing from your own
7  terminal.
8
9All of them build `build/vev` and bake it into the `scripts/demo/Dockerfile`
10image, so local and remote vev are the same binary. Docker must be rootless.
11
12## Manual remote testing
13
14```sh
15scripts/demo/test-remotes.sh up       # build, start remote-a/remote-b, register both hosts
16scripts/demo/test-remotes.sh shell    # print the client command
17scripts/demo/test-remotes.sh status   # containers, ports, vev host list, vev ls --all
18scripts/demo/test-remotes.sh broker-restart  # stop only the test broker; the next vev call respawns it
19scripts/demo/test-remotes.sh down     # stop the test broker/daemon, remove containers and keys
20```
21
22Run the printed command from a real terminal, or `scripts/demo/test-remotes.sh
23shell --exec [vev args]`. It sets:
24
25- `VEV_ENV=test` and `VEV_ENV_ROOT=<checkout>/.dev`: all vev state lives in
26  `.dev/test/`, apart from your installed vev.
27- `PATH=.dev/test/bin:$PATH`: vev runs `ssh` from `PATH` and has no ssh config
28  option, so `.dev/test/bin/ssh` wraps the real client with
29  `-F .dev/test/ssh/config`. The key, `known_hosts` and config are generated in
30  `.dev/test/ssh/`. `~/.ssh` and your agent are never used.
31- `VEV_REMOTE_TRANSPORT=stdio`: hosts are registered with the SSH-only carriage.
32  QUIC cannot work here. The remote proxy listens on a random UDP port, and
33  the client dials that port on the SSH target name (`remote-a`), which does
34  not resolve to the loopback port mapping.
35- `-u VEV`: a client started from a pane of your real vev is not treated as
36  nested.
37
38sshd is published on `127.0.0.1:2222` (remote-a) and `127.0.0.1:2223`
39(remote-b). Override the ports with `VEV_TEST_SSH_PORT_A` and
40`VEV_TEST_SSH_PORT_B`, and the environment name with `VEV_TEST_ENV`. Plain
41shell access: `.dev/test/bin/ssh remote-a`.
42
43`up` is idempotent: it recreates the containers, reinstalls the key and
44skips hosts that are already registered. A `VEV_ENV=test` broker started by an
45older build keeps running until it is stopped, and `up` warns when it finds
46one. Run `down` then `up` after a rebuild. `down` stops **every**
47`VEV_ENV=test` daemon of this checkout, including sessions you opened
48there by hand.
49
50Remote sessions live in the containers and disappear on `down`.
51
52### Checklist
53
54Open a few sessions first, with at least two tabs in one of them, local and on
55each remote: `vev new work`, `vev new ra remote-a`, `vev new rb remote-b`
56(each run with the environment above).
57
58- [ ] Picker over a session (`Alt+Space`, `SSP`): opens over the live
59      session; `Esc` returns to the same session, tab and pane.
60- [ ] Move pane (`MFP`) and move tab (`MAT`): the destination picker lists
61      local and remote sessions and tabs; the move lands where you chose.
62- [ ] `x` in the picker kills the selected session (local and remote); the
63      row disappears and `vev ls --all` agrees.
64- [ ] Tab rows: expand a session and see one row per tab, with the right names
65      and active marker. Selecting a tab row lands on that tab.
66- [ ] MRU order: switch A → B → C, reopen the picker, and check the order is
67      C, B, A.
68- [ ] Bell icons: in a background tab or session run `sleep 2; printf '\a'`,
69      switch away, and check that the bell icon shows on that session and tab
70      row. It clears once you visit it. Try it on a remote session too.
71- [ ] Live preview: moving the cursor over a local session, then over a remote
72      one, shows its current screen. Run `ticker` there to check that the
73      preview updates live.
74- [ ] Remote attach and switch: `vev attach demo@remote-a:<session>` from
75      the shell (this also adds the learned target `demo@remote-a`), then
76      switch between local, remote-a and remote-b sessions from the picker
77      without dropping input or output.
78- [ ] Broker restart: `scripts/demo/test-remotes.sh broker-restart` stops only
79      the test broker. Reopen the picker from a running client and check that
80      hosts and sessions come back.