Warp: file paths in terminal output no longer clickable (URLs still work fine) — regression, ~2 weeks

Environment

• Claude Code version: 2.1.220
• Terminal: Warp (Windows)
• OS: Windows 10 IoT Enterprise LTSC 2021

Symptom
File paths and URLs printed to the terminal by Claude Code are no longer clickable (ctrl/cmd-click to open) in Warp. This includes:

1. Paths written as plain text in the assistant's own chat-style response.
2. Absolute paths printed via an actual shell command's stdout (tested directly, e.g. ls -la <absolute-path> run through Claude Code's Bash tool) — still not clickable, even though this is genuine terminal output, not assistant-authored text.

This worked correctly until roughly 2 weeks ago and has since stopped, with no configuration change on my end.

Troubleshooting done

• Checked Warp's settings.toml and local warp.sqlite (server_experiments table) for a path/URL-detection toggle — found none; this appears to be built-in Warp behavior, not something disabled by a setting.
• Confirmed the regression reproduces with plain absolute Windows paths (e.g. C:\Users\...\file.md), one per line, no markdown formatting.

Possibly related
#54606 describes Warp failing to detect line-wrapped URLs due to hard newlines in Claude Code's output. My symptom looks broader than that (paths short enough to never wrap are also not detected), so this may be a distinct regression, but flagging in case the root cause overlaps (e.g. a change to how Claude Code's terminal output/PTY handling interacts with Warp's link-detection layer — synchronized output added around v2.1.200, and sandboxed command execution added around the same window, are both plausible candidates, though I have not confirmed either as the actual cause).

Ask
Would appreciate a pointer to whether this is a known regression, and if so, which version reintroduces working clickable links in Warp.