feat: close the last four domain events, and the panel paths they describe

Every one of the fourteen named events now has an emit point. The four that
were missing all sat on paths owned by earlier tasks:

- AppointmentCompleted fires from both status-change routes, after the row is
  saved. A rejected transition or a version conflict leaves no event; otherwise
  the completed count runs ahead of the appointments themselves.
- AppointmentRescheduled is a third event, not a replacement. A rebook is a
  confirm plus a cancel, and a consumer that only hears the cancel messages a
  patient who still has an appointment.
- ResourceBlocked / ResourceReleased are a pair. Capacity coming back has to be
  as audible as capacity going away, or the resource reads as permanently taken.

Publishing is now on the scheduler rather than an unregistered command: the
logic moved out of PublishDomainEventsCommand into OutboxPublisher so the
recurring message and the manual command share it, and the existing
worker-scheduler container consumes it. The scheduler message carries no data
on purpose — what to publish is read from the table, so an event recorded
between two ticks is not skipped. DomainEventMessage routes to async, since a
slow consumer was otherwise slowing the drain itself and its failure marked a
row failed that had in fact been delivered.

Panel work that these paths made reachable:

- Cancelling from the appointment page now goes through the policy-aware
  endpoint and shows the penalty preview before the confirm, so the operator
  does not discover the patient's penalty after the fact. The cancellation
  service writes the timeline entry itself and accepts a reason, which that
  path previously dropped on the floor.
- Rescheduling reuses the booking page under ?rebook=<uuid> — the search and
  hold steps are identical and only the final step differs. The doctor picker
  is hidden there: a reschedule is not an invitation to change doctors.
- A new GET /appointment/{uuid}/segments exposes the recorded plan. An empty
  list is not an error, it means the appointment is slot-based, and that is
  exactly what gates the resource-mode reschedule button.

AppointmentInvoiceCard no longer crashes the whole detail page when an older
invoice has no discount breakdown.

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

docs/api/appointment-booking.md

@@ -109,6 +109,42 @@ UNIQUE (resource_id, bucket_at, seat)
 جابه‌جایی: **اول** رزرو جدید، بعد آزادسازی قدیم. ترتیب عمدی است — اگر رزرو جدید شکست
 بخورد، نوبت قدیمی دست‌نخورده می‌ماند و بیمار بی‌نوبت نمی‌شود.
 
+```json
+{ "hold_uuid": "5e0e…" }
+```
+
+پاسخ: `appointment_uuid` · `released_intervals` (تعداد اشغال آزادشدهٔ زمان قبلی) ·
+`starts_at` (زمان تازه).
+
+سه رویداد دامنه ثبت می‌شود، نه یکی: `AppointmentBooked`، `AppointmentCancelled` و
+`AppointmentRescheduled`. سومی همان چیزی است که دو تای اول را به هم وصل می‌کند؛ بدون آن،
+مصرف‌کننده‌ای که فقط لغو را می‌شنود برای بیماری که هنوز نوبت دارد پیام لغو می‌فرستد.
+
+در پنل، همین مسیر با `/admin/resource-booking?rebook={uuid}` باز می‌شود: همان جستجو و
+رزرو موقت، فقط گام آخرش جابه‌جایی است.
+
+## `GET /api/v1/appointment/{uuid}/segments`
+
+بخش‌های **ثبت‌شدهٔ** نوبت — عکسِ لحظهٔ رزرو، نه الگوی امروزِ خدمت. تغییر بعدیِ الگو این
+فهرست را عوض نمی‌کند.
+
+```json
+{
+  "success": true,
+  "data": [
+    { "sequence": 1, "name": "بی‌حسی", "starts_at": 1811232000, "ends_at": 1811232300,
+      "duration_minutes": 5, "patient_present": true },
+    { "sequence": 2, "name": "انتظار", "starts_at": 1811232300, "ends_at": 1811234100,
+      "duration_minutes": 30, "patient_present": false }
+  ]
+}
+```
+
+**فهرست خالی خطا نیست** و یعنی نوبت اسلاتی است. پنل با همین تفاوت تصمیم می‌گیرد دکمهٔ
+جابه‌جایی منبع‌محور را نشان بدهد یا نه.
+
+**۴۰۴** روی نوبت محیط دیگر.
+
 ---
 
 ## اشغال: یک ردیف per (بخش × منبع)