Prepare project for pipeline takeover: task tracker, UX doc, CLAUDE.md pointers

Adds docs/tasks/ (16 epics + 102 stories converted to task/subtask files with
statuses.md as the new status source of truth) and docs/ux-design.md
(retrospective design-system reference), and points CLAUDE.md at them.
docs/prd.md and docs/architecture.md are kept as BMAD wrote them; the legacy
docs/stories/, docs/epics/, docs/qa/gates/ and .bmad-core/ stay in place as
historical/traceability records, superseded but not deleted.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

docs/tasks/4-6.md

@@ -0,0 +1,30 @@
+---
+id: 4-6
+title: 4-6 Timeline Update Notifications
+status: QA Review
+date: 2026-09-27
+parent: 4
+---
+
+## Description
+
+As a client, I want to receive email notifications when my timeline is updated, So that I stay informed about my case progress without checking the portal. Context: Integrates with: timeline_updates creation, email system; Technology: Laravel Notifications, queued emails; Follows pattern: Event-driven notification pattern. Full implementation history: docs/stories/story-4.6-timeline-update-notifications.md
+
+## Acceptance Criteria
+
+- [ ] Email sent when new update added to timeline
+- [ ] Triggered automatically on TimelineUpdate creation
+- [ ] Queued for performance
+- [ ] Case name and reference
+- [ ] Update summary or full text
+- [ ] Date of update
+- [ ] Link to view timeline
+- [ ] Libra branding
+- [ ] Email in client's preferred language
+- [ ] Arabic template
+- [ ] English template
+- [ ] No email for archived timeline reactivation
+- [ ] No email if client deactivated
+- [ ] Professional email template
+- [ ] Tests for notification sending
+- [ ] Error handling for failed sends