Problem
Design docs are currently orphaned:
- DB has design_docs table (empty, unused)
- DB has design_doc column on tasks (not in Task record)
- Task.taskDescription exists but isn't emphasized for epics
- No web UI to view/edit design docs
- No linking between docs and tasks
Proposal: Epics ARE Design Docs
Instead of separate design_docs table, treat Epic descriptions as the design doc:
1. Epic description = the design/planning document
2. Subtasks under the epic = implementation work
3. Web UI shows epic description prominently (rendered markdown)
4. Can link to epic from subtasks (already works via parent)
Benefits
- No new tables or data model changes
- Already have taskDescription field
- Already have epic->subtask hierarchy
- Already created t-149 this way (description has the full plan)
Implementation
Phase 1: Enhance Epic Display in Web UI
- On epic detail page, render description as markdown (full width, prominent)
- Add 'Design' or 'Plan' section header
- Show subtask progress below
Phase 2: Better Epic Editing
- Multiline description input in web UI (textarea)
- Or link to edit in CLI: jr task edit t-149 --description='...'
Phase 3: Cleanup
- Remove unused design_docs table
- Remove unused design_doc column from tasks table
- Remove any dead code referencing these
Schema Changes
None required - just use existing taskDescription field.
Files to Modify
- Omni/Jr/Web.hs - Epic detail view, markdown rendering
- Omni/Jr/Web/Style.hs - Styles for rendered markdown
- Omni/Task/Core.hs - Remove design_docs table creation (cleanup)