[qdaxb]

Summary

• Add unified form submission system with pluggable handler architecture
• Implement backend REST API endpoint POST /api/forms/submit for all form types
• Create database model form_submissions for submission tracking and auditing
• Add WebSocket events for real-time form status updates
• Implement handlers for clarification, final_prompt, and pipeline_confirmation
• Create reusable GenericForm component with dynamic field rendering
• Support multiple field types: single_choice, multiple_choice, text_input, datetime_picker, number_input
• Add frontend hook useFormSubmission for submission state management
• Include comprehensive unit tests for backend handlers and frontend components

Architecture

Backend:
- POST /api/forms/submit -> FormSubmissionService -> Handler Registry -> Specific Handler
- WebSocket events: form:submitted, form:processing, form:completed, form:error

Frontend:
- GenericForm -> FormFieldRenderer -> Field Components (SingleChoice, MultipleChoice, etc.)
- useFormSubmission hook for state management and WebSocket integration

New Files

Backend:

• backend/app/services/forms/ - Forms service module with registry pattern
• backend/app/api/endpoints/adapter/forms.py - REST API endpoint
• backend/app/models/form_submission.py - Database model
• backend/app/schemas/form.py - Pydantic schemas
• backend/alembic/versions/q7r8s9t0u1v2_add_form_submissions_table.py - Migration

Frontend:

• frontend/src/features/tasks/components/forms/ - Form components
• frontend/src/apis/forms.ts - API client
• frontend/src/types/form.ts - TypeScript types

Test plan

• Backend unit tests pass for form handlers and registry
• Frontend component tests pass for GenericForm
• Manual test: Submit clarification form via new API
• Manual test: Submit pipeline confirmation via new API
• Verify WebSocket events are emitted correctly
• Verify form submissions are persisted in database