[atn18]

Description of changes

• Picking a session in /sessions or /recent while it is still replying showed the previous completed exchange (the last reply with text plus the input it answers), so a message just sent appeared nowhere and looked lost. The pick transcript now also sends the newest user input created after the shown reply started - once, right after the reply.
• The waiting input is detected by comparing the prompt's creation time with the shown reply's, so it behaves the same on V1 and V2 (the V2 adapter carries no parent link).
• Notes: a prompt whose reply was aborted, errored, or ended without a text reply is shown as waiting, because the transcript deliberately hides failed or text-less replies. The input quote itself still does not appear on OpenCode V2 (pre-existing; the V2 adapter maps no parent). The background-notification button keeps its existing reply-only behaviour.

Closes issue (optional)

• None

How it was tested

• npm run lint, npm run build, npm run typecheck, npm test - all green (2806 passed, 7 skipped).
• New unit tests for the waiting-input detection (created after the shown reply, predates it, no prompt); the pick integration test asserts the waiting input arrives after the reply.
• Manually verified on an installed copy: send -> /detach -> return while the reply is still running shows the waiting input; idle picks show no duplicate quote.

Checklist

• PR title follows Conventional Commits: <type>(<scope>)?: <description>
• This PR contains one logically complete change
• Branch is rebased on the latest main
• I ran npm run lint, npm run build, and npm test
• If this PR is OS-sensitive, behavior/limitations for Linux/macOS/Windows are described

[grinev]

@atn18 thanks for contribution!