Linux clipboard error handling and dependencies

[Seth-Lamancusa]

Issue Description

On Linux (especially minimal or server environments), highlighting text in the TUI triggers a "Copied to clipboard" notification even if the underlying clipboard tool (xclip, xsel, wl-copy) is missing or failing. This leads to a confusing user experience where the UI reports success but the clipboard remains unchanged.

Expected Behavior

• The TUI should report an error or warning if the copy operation fails.
• Standard clipboard tools should be included in the development environment.

Proposed Solution

• Modify Clipboard.copy to throw errors instead of swallowing them. This allows the TUI's existing .catch(toast.error) logic to display the actual failure reason.
• Add xclip and xsel to flake.nix.
• Add structured logging for debugging clipboard operations.

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• No issue template was used. Please resubmit using one of the three required templates: Bug Report, Feature Request, or Question. This issue appears to be a mix of both — if it's a bug report, include the required Description field and reproduction steps; if it's a feature request, the title should start with [FEATURE]: and include the verification checkbox.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

This issue might be a duplicate of existing issues. Please check:

• [FEATURE]:Linux TUI: show clipboard tool notice/warning on copy #10333: Very similar request — Linux TUI should show a warning/notice when clipboard tools (xclip, xsel, wl-clipboard) are missing, instead of silently succeeding
• Ubuntu terminal opencode can't copy the text in the window, "Copied to clipboard" showed #10175: Same symptom — "Copied to clipboard" notification shown on Ubuntu even when the copy operation fails due to missing clipboard tools

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new issue that follows our issue templates.