Exercise 1: Surviving a Simulated Disconnection — Possible Solution
=====================================================================

  $ screen -S migrate -L
  $ while true; do date; sleep 10; done       # stand-in for the import
  Ctrl-a c                                    # second window
  $ watch df -h
  Ctrl-a 0
  Ctrl-a _                                    # silence monitoring

Now close the terminal window (don't detach first).

Open a new terminal:

  $ screen -ls
  There is a screen on:
          42110.migrate   (Detached)
  1 Socket in /run/screen/S-philip.

On a local machine, closing the window usually lets screen notice the
client has gone, so the session shows as Detached and plain
`screen -r migrate` works. Over a real SSH connection that dropped
unexpectedly, it often still shows as (Attached), because the server
hasn't noticed yet — then use:

  $ screen -d -r migrate

Either way, the date loop is still running, and screenlog.0 in the
directory you started from contains every line it printed.

WHY THIS WORKS AS AN ANSWER
------------------------------
It reproduces the capstone's key moment and explains why the session
may appear as either Detached or Attached, with the right command for
each. The exact wording of screen's messages varies by version.