@@ -32,11 +32,11 @@ Pull requests should include a brief description, the data structures or tests c
 
 Several data structures have an interactive terminal UI built with [Textual](https://textual.textualize.io). There are two implementation patterns in use.
 
-### Standalone TUI (`stack_demo_tui.py`)
+### Standalone TUI (`stack_app.py`)
 
-`stack_demo_tui.py` is self-contained: it defines its own `StackDemo` model, panel widget, and full command dispatcher without inheriting from any shared base class. All future shared-base improvements do not automatically reach the stack TUI unless it is later refactored to inherit from `BaseLinearStructureTUI`.
+`stack_app.py` is self-contained: it defines its own `StackDemo` model, panel widget, and full command dispatcher without inheriting from any shared base class. All future shared-base improvements do not automatically reach the stack TUI unless it is later refactored to inherit from `BaseLinearStructureTUI`.
 
-### Base-class TUIs (`tui_common.py`)
+### Base-class TUIs (`common.py`)
 
 All other linear-structure TUIs inherit from `BaseLinearStructureTUI` in `data_structures/tui/common.py`. The base class provides:
 
 
@@ -26,15 +26,24 @@ make test-stack
 make run-stack
 ```
 
-The repo now includes interactive Textual TUIs for:
-- `stack_demo_tui`
-- `queue_demo_tui`
-- `deque_demo_tui`
-- `list_demo_tui`
-- `singly_linked_list_tui`
-- `doubly_linked_list_tui`
+The repo includes interactive Textual TUIs for six data structures. Launch any of them with a dedicated `make run-*-app` target:
 
-Use targets such as `make run-stack-app`, `make run-queue-app`, or `make run-dll-app`. Other demo modules do not yet have a `__main__` block, so their `run-*` targets verify a clean import but produce no output.
+```bash
+make run-stack-app
+make run-queue-app
+make run-deque-app
+make run-list-app
+make run-sll-app
+make run-dll-app
+```
+
+You can also run a TUI directly:
+
+```bash
+.venv/bin/python -m data_structures.tui.stack_app
+```
+
+Non-TUI demo modules contain only class definitions, so their `make run-<name>` targets verify a clean import but produce no output.
 
 For walkthroughs of the interactive apps, see:
 - `docs/StackTUI.md`
@@ -44,14 +53,40 @@ For walkthroughs of the interactive apps, see:
 - `docs/SinglyLinkedListTUI.md`
 - `docs/DoublyLinkedListTUI.md`
 
+## Producing Demo Videos
+
+Demo tapes live in `demos/`. Each TUI has a dark-theme tape and a light-theme tape. Generating the videos requires [vhs](https://github.com/charmbracelet/vhs).
+
+Produce videos for one TUI (dark + light):
+
+```bash
+make demo-stack
+make demo-queue
+make demo-deque
+make demo-list
+make demo-sll
+make demo-dll
+```
+
+Produce all videos at once:
+
+```bash
+make demo-all
+```
+
+Individual tape variants are also available, for example `make demo-stack-dark` or `make demo-dll-light`. Generated `.mp4` files are written to `demos/`.
+
 ## All Valid Targets
 
 | Target | Description |
 |---|---|
 | `make install` | Create `.venv` and install dependencies |
 | `make test` | Run the full test suite |
-| `make run-<name>` | Import a single demo module |
+| `make run-<name>` | Import a single non-TUI demo module |
+| `make run-<name>-app` | Launch a TUI app interactively |
 | `make test-<name>` | Run a single test module with verbose output |
+| `make demo-<name>` | Produce dark+light demo videos for one TUI (requires [vhs](https://github.com/charmbracelet/vhs)) |
+| `make demo-all` | Produce demo videos for all six TUIs |
 
 Valid `<name>` values (short alias or full name both work):
 
@@ -66,13 +101,13 @@ Valid `<name>` values (short alias or full name both work):
 | `list` | `list_demo` | `data_structures/list_demo.py` | `tests/test_list_demo.py` |
 | `networkx` | `networkx_graph_demo` | `data_structures/networkx_graph_demo.py` | `tests/test_networkx_graph_demo.py` |
 | `queue` | `queue_demo` | `data_structures/queue_demo.py` | `tests/test_queue_demo.py` |
-| `queue-tui` | `queue_demo_tui` | `data_structures/tui/queue_app.py` | `tests/test_queue_demo_tui.py` |
+| `queue-app` | `queue_app` | `data_structures/tui/queue_app.py` | `tests/test_queue_app.py` |
 | `set` | `set_demo` | `data_structures/set_demo.py` | `tests/test_set_demo.py` |
 | `sll` | `singly_linked_list` | `data_structures/singly_linked_list.py` | `tests/test_singly_linked_list.py` |
-| `sll-tui` | `singly_linked_list_tui` | `data_structures/tui/singly_linked_list_app.py` | `tests/test_singly_linked_list_tui.py` |
+| `sll-app` | `singly_linked_list_app` | `data_structures/tui/singly_linked_list_app.py` | `tests/test_singly_linked_list_app.py` |
 | `stack` | `stack_demo` | `data_structures/stack_demo.py` | `tests/test_stack_demo.py` |
-| `stack-tui` | `stack_demo_tui` | `data_structures/tui/stack_app.py` | `tests/test_stack_demo_tui.py` |
-| `deque-tui` | `deque_demo_tui` | `data_structures/tui/deque_app.py` | `tests/test_deque_demo_tui.py` |
-| `list-tui` | `list_demo_tui` | `data_structures/tui/list_app.py` | `tests/test_list_demo_tui.py` |
-| `dll-tui` | `doubly_linked_list_tui` | `data_structures/tui/doubly_linked_list_app.py` | `tests/test_doubly_linked_list_tui.py` |
+| `stack-app` | `stack_app` | `data_structures/tui/stack_app.py` | `tests/test_stack_app.py` |
+| `deque-app` | `deque_app` | `data_structures/tui/deque_app.py` | `tests/test_deque_app.py` |
+| `list-app` | `list_app` | `data_structures/tui/list_app.py` | `tests/test_list_app.py` |
+| `dll-app` | `doubly_linked_list_app` | `data_structures/tui/doubly_linked_list_app.py` | `tests/test_doubly_linked_list_app.py` |
 | `trie` | `trie_demo` | `data_structures/trie_demo.py` | `tests/test_trie_demo.py` |
@@ -512,6 +512,6 @@ Expected behavior:
 
 ## Verification Notes
 
-The viewport-selection and argument-parsing logic are covered by `tests/test_stack_demo_tui.py`.
+The viewport-selection and argument-parsing logic are covered by `tests/test_stack_app.py`.
 
 The app also runs under the local project virtual environment created by `make install`.