fix(booking): carry the clinic context through the panel and drop phantom locations

Two faults, one root: the per-context booking work updated ScheduleSection but
left the rest of the panel calling slot endpoints without clinic_uuid. Absent
clinic_uuid means the personal practice, so the panel asked about a schedule the
doctor barely uses and got nothing back.

- useClinicContext() resolves the current environment once and is used by the
  appointments page, useDoctorBookingServices, ServiceSlotPicker and both
  queries in NewAppointmentDrawer (a fifth call site a sweep turned up). It
  returns null in a doctor's personal environment so the mirror-image bug — a
  doctor seeing the clinic's schedule at their own practice — cannot appear.
  clinicUuid is part of every query key; without it the cache leaks across
  environments.
- appointment-slots returns empty_reason (no_schedule | holiday | day_off |
  outside_window). TurnsTimeline rendered «این روز تعطیل است» for any empty day,
  which is what the bug report actually saw; it now says which of the four it is.
- booking-locations lists a location only when the context has an address and an
  active shift points at it. The dev data had three "personal" schedules whose
  shifts referenced the clinic's address, so the public site advertised a
  personal practice that could never be booked.
- ?date= adds available_on_date per location, validated as a real calendar date.
- MyAppointmentsController and AdminApiController resolved the appointment
  address with no context and could store the wrong one. Both now go through the
  new BookingContextResolver, which also replaces AppointmentController's private
  copy of the same membership check.
- app:schedule:audit-locations reports shifts pointing at a missing or foreign
  address; --fix deactivates them rather than deleting.

Verified against the reported doctor: same date, no clinic_uuid -> 0 sessions,
with it -> 1 session; a full week matches the configured Sat/Tue/Wed/Thu.

Suite: 417 tests, 2 failures — both pre-existing and unrelated.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

src/Appointment/Service/SlotCalculatorService.php

@@ -13,6 +13,12 @@ use App\Doctor\Entity\Doctor;
 
 class SlotCalculatorService
 {
+    /** دلایل خالی‌بودن یک روز — برای پیام دقیق در پنل. */
+    public const EMPTY_NO_SCHEDULE    = 'no_schedule';
+    public const EMPTY_HOLIDAY        = 'holiday';
+    public const EMPTY_DAY_OFF        = 'day_off';
+    public const EMPTY_OUTSIDE_WINDOW = 'outside_window';
+
     public function __construct(
         private readonly WeeklyScheduleRepository $scheduleRepo,
         private readonly DateOverrideRepository   $overrideRepo,
@@ -135,6 +141,37 @@ class SlotCalculatorService
         return $result;
     }
 
+    /**
+     * چرا این روز اسلاتی ندارد. null یعنی اسلات دارد.
+     *
+     * پنل نمی‌تواند خالی‌بودن را به «تعطیل» ترجمه کند: نبودِ برنامه، تعطیلی، روزِ
+     * بدون شیفت و خارج‌بودن از بازهٔ نوبت‌دهی چهار چیز متفاوت‌اند و کاربر باید
+     * بداند کدام‌یک رخ داده تا بداند چه کاری باید بکند.
+     */
+    public function explainEmptyDay(Doctor $doctor, string $date, ?Clinic $clinic = null): ?string
+    {
+        if ($this->buildAllSessions($doctor, $date, $clinic) !== []) {
+            return null;
+        }
+
+        $schedule = $this->scheduleRepo->findByDoctorAndClinic($doctor, $clinic);
+        if ($schedule === null) {
+            return self::EMPTY_NO_SCHEDULE;
+        }
+
+        $dayStart = (int) strtotime($date . ' 00:00:00');
+
+        if ($this->holidayRepo->findActiveByDoctor($doctor, $dayStart, $dayStart + 86399, $clinic) !== []) {
+            return self::EMPTY_HOLIDAY;
+        }
+
+        if (!$this->isWithinBookingWindow($doctor, $dayStart, $clinic)) {
+            return self::EMPTY_OUTSIDE_WINDOW;
+        }
+
+        return self::EMPTY_DAY_OFF;
+    }
+
     /**
      * زودترین اسلات آزاد در $daysAhead روز آینده، یا null اگر ظرفیتی نباشد.
      *