docs: warn that aoe send races with launch

docs/driver-prompt.md

@@ -63,10 +63,36 @@ that settled it.
    The worktree path derives from `--title`, not the branch, so every title must
    be distinct.
 
-   Then send the session its task with `aoe send`. Tell it: the issue number,
-   to read `DESIGN.md` and `CLAUDE.md` first, to implement only what the issue
-   scopes, that `just ci` must pass locally, and to open a pull request against
-   `main` referencing the issue.
+   Then send the session its task. Tell it: the issue number, to read
+   `DESIGN.md` and `CLAUDE.md` first, to implement only what the issue scopes,
+   that `just ci` must pass locally, and to open a pull request against `main`
+   referencing the issue.
+
+   **`aoe send` races with `--launch` and fails silently.** It reports
+   "Sent message to ..." even when the agent process was not yet up to receive
+   it, and the session then sits idle forever looking healthy. This was hit
+   while bootstrapping and it is the single most likely way for you to stall.
+
+   So: after sending, **verify the prompt actually landed** before treating the
+   session as working.
+
+   ```sh
+   tmux capture-pane -p -t "aoe_<title>_<id-prefix>" | tail -20
+   ```
+
+   An idle session shows an empty pane and `$0.00`. A working one shows token
+   usage and activity. If it is idle, send again — directly to the pane, which
+   does not race:
+
+   ```sh
+   tmux send-keys -t "aoe_<title>_<id-prefix>" "<the prompt>"
+   sleep 1
+   tmux send-keys -t "aoe_<title>_<id-prefix>" Enter
+   ```
+
+   Note there are two tmux sessions per `aoe` session: `aoe_<title>_<id>` is
+   the agent, `aoe_term_<title>_<id>` is a plain terminal. Send to the former.
+   `tmux ls` lists them.
 
 4. **Wait.** Once a pull request opens, the PR daemon automatically spawns a
    `land` session (fixes CI, addresses review comments) and a `rev-<n>-…`