feat(question-card): click the session row to focus the asking terminal

[mutoe]

Problem

The question card offers no way back to the conversation that asked the question.

When an AskUserQuestion / plan-mode prompt pops up, the only exits are answering an option or Skip. Skip is not "hide this for now" — it denies the request and drops it from the queue (as explained in #210), so there is no safe way to say "let me go read the terminal first."

The approval card already solves exactly this: clicking it focuses the owning terminal. The question card just never got wired up. QuestionBar receives only session?.source and session?.cwd as plain strings, even though the construction site one screen away already has the full SessionSnapshot:

case .questionCard(let sid):
    let session = appState.sessions[sid]   // ← the session is right here
    QuestionBar(
        sessionSource: session?.source,    // ← but only two strings go down
        sessionContext: session?.cwd,
        ...

So TerminalActivator.activate had exactly two call sites: ApprovalBar and SessionCard.

Change

1. Extract the shared jump driver. ApprovalBar.handleCardClick() held ~60 lines — activate terminal, poll 3× with increasing delays to see whether the jump landed, collapse on success, error sound + shake on failure. Rather than paste a third copy, it moves to startNotchCardJump(kind:session:sessionId:appState:autoCollapseAfterJump:shakeOffset:). ApprovalBar behaviour is preserved line for line; SessionCard is untouched (its jump has slightly different semantics around remote sessions, so it stays as it is).

The only thing that differed between the two cards is which surface may auto-collapse, now a NotchCardKind.

2. Wire up QuestionBar. It gains session / sessionId / appState, and the "CLI icon + project folder" row becomes the jump target — with a hover highlight and an ↗ glyph, so the affordance is discoverable rather than an invisible hit area. The row now also renders when the session has no cwd, so a jumpable session always has an entry point.

I deliberately did not make the question text clickable, the way the approval card's tool-name row is. That line is what the user is reading; a misclick there would yank them to another app mid-thought. The session-identity row carries the clearer meaning anyway: click which session this is → go to that session.

3. Fixed a doc comment that had drifted onto shortcutHint (it documents handleCardClick).

Behaviour

• Click the session row → the asking terminal comes to the front, exactly like the approval card.
• With Auto-Collapse After Jump on, the notch folds once the jump is verified. The question stays queued and answerable — in the terminal, or back on the card via ⌘⇧I / hovering the notch. This is the important distinction from Skip.
• Remote sessions have no local terminal, so the glyph and hover affordance stay hidden rather than presenting a dead control.
• Jump fails (terminal gone) → the existing error sound + shake, unchanged.

Tests

NotchPanelViewTests

• NotchCardKind.matches across every surface: a question-card jump must never collapse an approval card, and vice versa. Jump validation is async, so by the time it resolves the panel may have swapped cards — collapsing then would discard a live request the user never touched, the Answer from the notch card can be delivered to the wrong session when several sessions are waiting #308 failure mode.
• The retry schedule stays [120ms, 320ms, 640ms].

AppStateQuestionFlowTests

• testCollapsingAQuestionCardAfterAJumpKeepsItAnswerable — collapse the surface the way a successful jump does, then assert the question is still queued and still answers correctly through its continuation. This pins the property that separates a jump from a Skip.

Full suite green locally on macOS 26.4 / Xcode 26 (Swift 6.3.3): 890 tests, 2 skipped, 0 failures. swift build is clean — no new warnings from these files.

Notes

CHANGELOG is left alone since it looks like it's written at release time.