feat: save input text draft into local storage

[uinstinct]

Description

Save the unsubmitted input text into local storage so that it persists between reloads and page changes.

resolves CON-5281

AI Code Review

• Team members only: AI review runs automatically when PR is opened or marked ready for review
• Team members can also trigger a review by commenting @continue-review

Checklist

• [] I've read the contributing guide
• [] The relevant docs, if any, have been updated or created
• [] The relevant tests, if any, have been updated or created

Screen recording or screenshot

before.mp4

after.mp4

Tests

[ What tests were added or updated to ensure the changes work as expected? ]

---

Continue Tasks: ▶️ 2 queued — View all

---

Summary by cubic

Persist unsubmitted drafts for both the main input and per-message edits in local storage so text and position survive reloads and navigation. Drafts auto-load per chat/message, restore scroll and focus, and clear on submit or when empty. Resolves CON-5281.

• New Features

  • Save main input as JSON under inputDraft_; save per-message edit under editingDraft_ with content, messageId, and scrollTop.
  • Load saved drafts into the main input and matching message editor; restore scroll and focus when returning.
  • Clear the relevant draft after submission or when content becomes empty.
  • Added localStorage types for inputDraft_ and editingDraft_.

• Refactors

  • Removed the clearContent effect in TipTapEditor to prevent wiping drafts on mount.

^{Written for commit d090ce5. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 3 files

[RomneyDa]

@uinstinct it looks like this only works for the main input. I think it's an improvement but can we think of a simple way to have this work across conversations and in any tip tap editor when going to settings and back?

1. On closing/reopening vs code it's okay to lose drafts in any editor but would be nice if main editor was saved (already works on this branch) and great if all were saved (in a way that doesn't leak local storage etc memory)
2. On going to settings and back any editor's content is preserved, as well as the scroll position of the chat history in case I was editing message number 2 in a 5 message sequence

If too many tradeoffs we can merge this but let's brainstorm on full solution first. There might be a simple solution where we don't unmount the component at all when switching to settings (router level fix).

[uinstinct]

1. On closing/reopening vs code it's okay to lose drafts in any editor but would be nice if main editor was saved (already works on this branch) and great if all were saved (in a way that doesn't leak local storage etc memory)

It currently saves all - there would not be any memory leakage, as far as I think, because there can only be 2 drafts be saved: inputDraft_chat or inputDraft_edit which get cleared during submission

2. On going to settings and back any editor's content is preserved, as well as the scroll position of the chat history in case I was editing message number 2 in a 5 message sequence

I did a simple implementation for this to save the editing draft and scroll back to chat history position.

feat.mp4