fix: name adoption in two refusals an adopted session gets (release review)

The Edit history panel told an adopted session it needed to be a Claude
session outside Docker, and a stop wait blamed the missing Claude Code hooks
on the mode. Both refusals are right, only the words misled. Each now says
Codeman did not start the session, with a zh-CN entry for the panel.

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

test/session-wait-registry.test.ts

@@ -170,6 +170,17 @@ describe('resolveWaitSignals', () => {
     expect(resolveWaitSignals('blocked', { mode: 'gemini' as SessionMode }).error).toBeTruthy();
   });
 
+  it('names adoption, not the mode, when an adopted session refuses `stop`', () => {
+    // An adopted session can be `mode: claude` with no hooks installed, and "no Claude
+    // Code hooks for claude sessions" sent the caller looking for a bug in the wrong place.
+    const refusal = resolveWaitSignals('stop', { ...claude, adopted: true });
+
+    expect(refusal.until).toEqual([]);
+    expect(refusal.error).toContain('adopted session');
+    expect(refusal.error).toContain('idle or exit');
+    expect(refusal.error).not.toContain('claude sessions');
+  });
+
   it('accepts `blocked` on codex, whose dialogs are read off the screen, but still not `stop`', () => {
     // capabilities.workDetect.blockedLine gives codex a source for `blocked`; nothing on a
     // screen says a turn ended, so `stop` keeps its 400.