Exercise 1: Two Terminals, One Panel — Possible Solution
====================================================================

STEPS
------------------------------
1. Press Ctrl+` to open the terminal panel (first terminal appears
   automatically, already inside your project's folder, per this
   chapter's own point about the integrated terminal inheriting the
   working directory).
2. Type "echo hello" and press Enter — it prints "hello".
3. Click the "+" icon at the top-right of the terminal panel. A
   SECOND, separate terminal opens (also starting in the project
   folder), and a dropdown appears showing something like
   "1: bash" and "2: bash" (or your shell's name).
4. In this new terminal, type "dir" (Windows) or "ls" (macOS/Linux)
   and press Enter — it lists the project folder's contents.
5. Click the dropdown at the top of the terminal panel and switch back
   to the first terminal. Its "hello" output from step 2 is still
   there, completely unaffected by anything typed in the second one.

WHY THIS WORKS AS AN ANSWER
------------------------------
Clicking "+" rather than just running a second command in the same
terminal reuses the exact distinction the chapter draws — each
terminal is a genuinely SEPARATE shell session with its own command
history and running state, not just a second command in the same
session. Switching between them via the dropdown, rather than closing
and reopening one, is what proves both stay alive and independent
simultaneously.

Running two DIFFERENT commands (one per terminal) makes each
terminal's independent state directly visible — going back to terminal
1 and seeing "hello" still sitting there, unaffected by the "dir"/"ls"
run in terminal 2, is the concrete proof that these are separate,
concurrently-running sessions rather than one terminal being reused.