Statusline OSC 8 links with custom URI schemes (e.g. vscode://) aren't dispatched on click in `claude agents` / FleetView

What happened

A custom statusline emits an OSC 8 hyperlink whose target is a custom URI scheme, e.g. an "Open in VS Code" link pointing at vscode://file/<absolute-path>.

• In the interactive claude TUI, clicking the link works — the terminal hands vscode:// to the OS and VS Code opens at the folder.
• After switching to claude agents (FleetView), the same statusline link still renders (underlined), but clicking it does nothing. http(s):// links appear to work; custom OS-registered schemes (vscode://, cursor://, etc.) are not dispatched.

The scheme is valid and registered at the OS level (open "vscode://file/<path>" succeeds), and it works from the normal TUI — so this is specific to how FleetView handles clicks on custom-scheme OSC 8 links.

Expected

FleetView dispatches clicks on OSC 8 hyperlinks with custom URI schemes the same way the interactive TUI does (hand the URL to the OS handler), or documents that only http(s):// is supported there.

Repro

1. Add a statusline that prints an OSC 8 link to vscode://file/<absolute-folder-path> (label e.g. "Open in VS Code").
2. In the interactive claude TUI, click it → VS Code opens. ✅
3. Switch to claude agents / FleetView, click the same link → nothing happens. ❌

Environment

• Claude Code 2.1.174
• macOS
• VS Code installed; vscode:// registered (confirmed via open)

Notes

Possibly related to #23438 (OSC 8 rendering in tmux), but distinct: here the link renders correctly and the issue is click dispatch for non-http(s) schemes in FleetView specifically.