refining TUI paste behavior: opt‑in handling of file and image paths

[neurostream]

I’ve noticed that when I paste text, the TUI heuristically scans for path‑like strings, stats them, and (if they appear to be images) attempts to load them. This can lead to:

• Unintended filesystem probes for incidental path patterns
• Extra log noise on misses
• A small risk of surfacing files a user didn’t mean to attach

Would it make sense to shift toward a more explicit, opt‑in flow?

Or is there already an opt-in/out config to set this that I've missed in the docs?

If opting-out needs to be the default action to take, then a lot of terminals support bracketed paste mode, letting the app clearly distinguish an object paste block to interpret as a deliberately supplied file path. This would reduce unintended lookups while keeping attachment workflows smooth.