Naser Mansour
0f9d12c3cf
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>
1.2 KiB
1.2 KiB
id, title, status, date, parent
| id | title | status | date | parent |
|---|---|---|---|---|
| 7-6 | 7-6 Booking Limit Indicator | QA Review | 2026-09-27 | 7 |
Description
As a client, I want to see my booking status and limits clearly, So that I understand when I can book consultations. - resources/views/livewire/client/booking-status.blade.php - Reusable status component. Full implementation history: docs/stories/story-7.6-booking-limit-indicator.md
Acceptance Criteria
- Dashboard widget showing booking status
- Booking page status banner
- "You can book a consultation today" (when no booking exists for today)
- "You already have a booking for today" (when pending/approved booking exists for today)
- "You have a pending request for [date]" (shows first pending request date)
- Pass
bookedDatesarray to availability calendar component - Calendar marks user's booked dates as unavailable (distinct styling)
- Visual indicator differentiates "user already booked" from "no slots available"
- Clear messaging about 1-per-day limit
- Bilingual messages (Arabic/English)
- Handle multiple pending requests (show count or list)
- Handle cancelled bookings (should not block new booking)
- Loading state while fetching booking status