[FEATURE] Mark Clipboard Paste temporary writes with org.nspasteboard.TransientType so clipboard managers ignore dictations

[mkallistos]

Problem

When the insertion mode is set to Clipboard Paste (reliablePaste) — the recommended workaround for apps where Clipboard Free Insert doesn't land (e.g. webview/terminal wrappers, related: #479) — every dictation is written to NSPasteboard.general as a plain string item with no metadata.

For anyone running a clipboard history manager (Maccy, Raycast Clipboard History, Paste, CopyClip, …) this has two side effects:

1. Every dictated phrase is captured into clipboard history, even though the user never "copied" anything. Dictations routinely contain sensitive content, and the user has no signal this is being persisted by their history tool.
2. The clipboard restore creates duplicate history entries. restorePasteboardSnapshot re-writes the previous clipboard contents, which bumps changeCount again, so polling managers record the user's prior clip a second time and reorder history.

Per-app ignore lists in clipboard managers can't filter this out: managers attribute a pasteboard change to the frontmost app, which during dictation is the target app being typed into, not FluidVoice.

Proposed solution

Adopt the community pasteboard convention from http://nspasteboard.org: when withTemporaryPasteboardString (in Sources/Fluid/Services/TypingService.swift) writes the temporary paste payload, declare org.nspasteboard.TransientType (and arguably org.nspasteboard.AutoGeneratedType) on the same pasteboard item:

pasteboard.clearContents()
let item = NSPasteboardItem()
item.setString(text, forType: .string)
item.setData(Data(), forType: NSPasteboard.PasteboardType("org.nspasteboard.TransientType"))
pasteboard.writeObjects([item])

Well-behaved clipboard managers ignore items marked transient by default (Maccy, Raycast, Paste, Alfred all honor this), so dictations would stop polluting clipboard history while paste behaviour is completely unchanged for the target app.

Marking the restore write as transient too would fix side effect 2, since it re-writes content the manager has already recorded.

Alternatives considered

• Excluding FluidVoice in the clipboard manager's per-app ignore list — doesn't work, see above (pasteboard changes are attributed to the frontmost app).
• Staying on Clipboard Free Insert mode — avoids the issue, but isn't usable in apps where CGEvent insertion doesn't arrive (Dictated list not inserted in Claude Code under cmux — only "a" appears (transcript correct; VS Code works) #479), which is exactly when users are told to switch to Clipboard Paste.

Environment: FluidVoice 1.6.4 (Homebrew cask), macOS 26.5 (Tahoe)

[grohith327]

Is this mainly for clipboard paste route ? For some people the clipboard text is actually a fallback, i.e. if insertion fails the text is still available somewhere.