Test 3 - full pipeline check

Initial Rails application setup including database configuration, gem installation, and base architecture decisions. This module establishes the foundation for authentication (staff-only via Devise), internationalization (I18n with Spanish/English locales), and responsive front-end tooling (Tailwind or Bootstrap with mobile-first breakpoints). It also includes setting up the deployment pipeline, environment configs, and basic CI. Every other module depends on this foundational setup being correctly structured, including timezone handling which is critical for a scheduling app.

This module allows the clinic manager to manage the three practitioners' profiles and define their recurring weekly availability (e.g., Mon-Fri 9am-1pm, 3pm-7pm) using a flexible schedule model. It supports defining slot duration/intervals per practitioner, and generating bookable slots dynamically for the next four weeks based on the recurring template. Holiday/time-off blocking is also handled here, allowing the manager to mark specific dates or date ranges as unavailable for one or all practitioners, which automatically removes those slots from what patients can book. This module is core infrastructure that the booking module directly depends on to know what slots are actually available.

The patient-facing booking experience where a visitor selects a practitioner, views available slots across the next four weeks in a simple calendar/list view, and books an appointment by entering name, email, and phone (no account required). This module handles slot locking/concurrency (preventing double-booking the same slot), form validation, and appointment creation. It depends on the Practitioner & Schedule module for slot availability and triggers the Notifications module upon successful booking. The UI must be fully responsive and available in both Spanish and English with locale-aware date/time formatting.

Automated email system that sends the patient a confirmation email after booking, including a secure tokenized cancellation link, and sends the clinic manager a notification email whenever a booking is made or cancelled. This module uses ActionMailer with locale-aware templates (Spanish/English based on patient's selection) and a signed/token-based cancellation route that doesn't require login. It integrates tightly with the Public Booking Flow (trigger on create) and adds a patient-facing cancellation page. Deliverability setup (SMTP provider like SendGrid/Postmark) is included here.