Feature request: Local history for dictated text and failed inserts

[Marabun]

Problem

When a user dictates or prepares text with Clicky, insertion can sometimes fail. If the clipboard already contains unrelated content, the dictated text may become impossible to recover and the user's work is lost.

This is especially frustrating for longer voice input: the user has already spent time composing the message, but a transient insertion failure forces them to dictate it again.

Proposed solution

Add a privacy-preserving, local-only history of recently dictated or prepared text.

The history should:

• Be stored only on the user's device, with no server upload or cloud sync required.
• Be accessible from a clear history panel inside the app.
• Preserve text after a failed voice-to-insert or smart insertion attempt.
• Let the user restore an entry, copy it, or retry inserting it.
• Optionally include a setting to enable or disable history.
• Include configurable retention controls, such as maximum entries or automatic deletion after a chosen period.
• Make it easy to clear individual entries or the full history immediately.

Why this preserves privacy

This does not require retaining dictated text on Clicky's servers. A local device log can provide recovery and a much better user experience without introducing server-side storage or data leakage.

Acceptance criteria

• Recent dictated/prepared text appears in an in-app history view.
• Text remains recoverable when insertion fails.
• Each entry has clear Restore/Copy/Insert actions.
• History data remains local to the device by default.
• Users can disable history and control retention or clear it.
• The UI clearly communicates that the history is stored locally.