feat(ux): implement autosave functionality for all user inputs to eliminate submit buttons

[AlexVOiceover]

Overview

Replace manual submit actions with automatic saving for all user inputs to create a more seamless and accessible user experience. This includes privacy toggles, action CRUD operations, and answer responses.

---

Problem Statement

Currently, users must manually submit their inputs through explicit submit buttons, which:

• Creates friction in the user experience
• Adds cognitive load for neurodivergent users
• Increases risk of data loss if users forget to save
• Makes the interface less intuitive and modern

---

Proposed Solution

Implement autosave functionality for all form inputs with the following scope:

1. Privacy Toggle Autosave

• Current: Privacy toggles require submit button press
• Proposed: Automatically save privacy settings when toggle is changed
• Implementation: Debounced save on toggle change event

2. Actions CRUD Autosave

• Current: Creating, updating, deleting actions requires submit buttons
• Proposed: Automatically save action changes on input blur/change
• Implementation: Debounced save for text inputs, immediate save for selections

3. Answer Response Autosave with Undo Support

• Current: Answer text requires submit button
• Proposed: Automatically save answer content with undo functionality to prevent accidental data loss
• Implementation:
  • Debounced save (5-10 seconds after last keystroke)
  • Local undo stack for recent changes (Ctrl+Z support)
  • "Restore previous version" button for quick recovery
  • Visual indicator showing autosave status and undo availability

---

User Experience Benefits

• Reduced cognitive load: No need to remember to save
• Accessibility improvement: Fewer actions required for neurodivergent users
• Data safety: Automatic persistence prevents data loss
• Modern UX: Matches expectations from contemporary applications
• Seamless workflow: Users can focus on content rather than interface

---

Technical Requirements

Implementation Strategy

• Add debounced autosave utility function
• Implement visual feedback for save states (saving, saved, error)
• Undo system for answer responses:
  • Local undo stack storing previous 5-10 versions
  • Keyboard shortcuts (Ctrl+Z/Cmd+Z) for undo
  • "Restore previous version" UI button
  • Clear visual indicators for undo availability
• Maintain data integrity with optimistic updates
• Handle network failures gracefully with retry logic
• Ensure accessibility compliance for save state indicators

Database Considerations

• Leverage existing response versioning system
• Maintain audit trail for autosaved changes
• Consider rate limiting to prevent excessive database writes

Error Handling

• Display user-friendly messages for save failures
• Implement offline support where possible
• Provide manual save option as fallback

---

Acceptance Criteria

• Privacy toggles autosave without submit button
• Action creation/editing autosaves without submit button
• Answer text responses autosave with undo support
• Local undo stack implementation (5-10 versions)
• Keyboard shortcuts (Ctrl+Z/Cmd+Z) for undo functionality
• "Undo" button in UI
• Visual indicators show save status (saving/saved/error) and undo availability
• Debounced saving prevents excessive API calls (5-10 second delay for answers)
• Graceful error handling for network failures
• Accessibility compliance maintained for all new features
• All existing functionality preserved
• Test coverage for autosave and undo scenarios

---