[Feature Request] Add persistent draft caching for in-progress prompts

⏺ Got it - let me fix that feature request:

---
Report 2: Feature Request (Revised)

[Automated Bug Detection System]

UX ISSUE: Draft caching interval too slow - prompts lost between cache cy

## Issue
Claude Code has an existing draft caching system, but the caching loop in

## Expected Behavior
Draft caching should be aggressive enough that:

• Rapid typing followed by immediate history navigation preserves the draft
• The cache interval is short enough to capture most real-world typing patterns
• Or: caching triggers on specific events (blur, history-nav-start) rather than just intervals

## Actual Behavior (tested 2025-12-31)

• Existing cache loop runs on a slow interval
• Typing a prompt and quickly pressing up-arrow can occur between cache cycles
• Result: draft is not yet cached when history navigation begins, causing data loss

## Impact

• False sense of security ("there's caching, my draft should be safe")
• Unpredictable behavior - sometimes drafts survive, sometimes they don't
• The slower you type, the safer you are (counterintuitive)
• Fast typists and rapid workflows penalized

## Suggested Fix

• Decrease the cache loop interval significantly (e.g., 500ms or less)
• And/or: add event-triggered caching on history navigation start, input blur, etc.
• Consider debounced keystroke-triggered caching as primary mechanism instead of interval-based