fix: say how the git and Edit history routes answer an adopted session (release review)

The adoption section said every git route answers unsupported, but git-diff
and git-fetch-settings answer 400, and the Git status section listed only
remote and docker. Edit history's `adopted` reason was documented nowhere.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/wiki/The-Dashboard.md

@@ -306,7 +306,7 @@ button, and **Rescan** runs it again.
   kill. Opening one types nothing into it.
 - **Codeman did not start it,** so it will not drive it: respawn, Ralph, auto-clear,
   auto-compact, auto-resume, custom model endpoints, prompt uploads and the image watcher are
-  refused, and the git panel shows nothing.
+  refused, the git panel shows nothing, and Edit history says it is not available.
 - **The tab opens on the session's first window,** and the row describes that same window.
 - **It joins like a second tmux client.** While the tab is open it can resize a session
   someone else is viewing, the way any second client does, and that reverses when it closes.

docs/wiki/Working-With-Files.md

@@ -326,7 +326,8 @@ Click it for a draggable window listing the active session's edits, newest first
   first catches up on the ones it had not read yet. **Load older** then goes back within the new
   conversation.
 
-It works for Claude sessions, local and remote (SSH). Docker and other CLIs' sessions say so instead.
+It works for Claude sessions, local and remote (SSH). Docker sessions, other CLIs' sessions and
+tmux sessions opened outside Codeman say so instead.
 A remote session's images show no thumbnail (each would be one more SSH read); click one to
 preview it. A remote host that is asleep is never woken for the history: the window shows the
 stored edits with the SSH error on top.