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>

src/Shared/Event/Command/PublishDomainEventsCommand.php

@@ -4,28 +4,26 @@ namespace App\Shared\Event\Command;
 
 use App\Shared\Event\Entity\DomainEventLog;
 use App\Shared\Event\Repository\DomainEventLogRepository;
-use Doctrine\ORM\EntityManagerInterface;
+use App\Shared\Event\Service\OutboxPublisher;
 use Symfony\Component\Console\Attribute\AsCommand;
 use Symfony\Component\Console\Command\Command;
 use Symfony\Component\Console\Input\InputInterface;
 use Symfony\Component\Console\Input\InputOption;
 use Symfony\Component\Console\Output\OutputInterface;
 use Symfony\Component\Console\Style\SymfonyStyle;
-use Symfony\Component\Messenger\MessageBusInterface;
 
 /**
- * انتشار صندوق خروجی: ردیف‌های `published_at IS NULL` به messenger می‌روند.
+ * اجرای دستیِ انتشار صندوق خروجی.
  *
- * شکست انتشار ردیف را نمی‌کشد؛ `attempts` بالا می‌رود و خطا ثبت می‌شود. بعد از سقف
- * تلاش، ردیف با خطایش باقی می‌ماند تا ادمین ببیند — حذف خاموش یعنی رویداد گم‌شدهٔ بی‌رد.
+ * منطقش در `OutboxPublisher` است چون زمان‌بند هم همان را هر دقیقه صدا می‌زند؛ این دستور
+ * برای وقتی می‌ماند که صف عقب افتاده و باید همین حالا تخلیه شود.
  */
 #[AsCommand(name: 'app:events:publish', description: 'Publish pending domain events from the outbox.')]
 class PublishDomainEventsCommand extends Command
 {
     public function __construct(
+        private readonly OutboxPublisher          $publisher,
         private readonly DomainEventLogRepository $events,
-        private readonly MessageBusInterface      $bus,
-        private readonly EntityManagerInterface   $em,
     ) {
         parent::__construct();
     }
@@ -37,36 +35,10 @@ class PublishDomainEventsCommand extends Command
 
     protected function execute(InputInterface $input, OutputInterface $output): int
     {
-        $io      = new SymfonyStyle($input, $output);
-        $pending = $this->events->findPending(max(1, (int) $input->getOption('limit')));
+        $io     = new SymfonyStyle($input, $output);
+        $result = $this->publisher->publish((int) $input->getOption('limit'));
 
-        $published = 0;
-        $failed    = 0;
-
-        foreach ($pending as $event) {
-            try {
-                $this->bus->dispatch(new \App\Shared\Event\Message\DomainEventMessage(
-                    $event->getUuid(),
-                    $event->getName(),
-                    $event->getEntityType(),
-                    $event->getEntityId(),
-                    $event->getPayload(),
-                    $event->getOccurredAt(),
-                ));
-
-                $event->markPublished();
-                $published++;
-            } catch (\Throwable $e) {
-                $event->markFailed($e->getMessage());
-                $failed++;
-            }
-        }
-
-        if ($pending !== []) {
-            $this->em->flush();
-        }
-
-        $io->success(sprintf('%d رویداد منتشر شد، %d ناموفق.', $published, $failed));
+        $io->success(sprintf('%d رویداد منتشر شد، %d ناموفق.', $result['published'], $result['failed']));
 
         return Command::SUCCESS;
     }

src/Shared/Event/Message/PublishDomainEventsMessage.php

@@ -0,0 +1,13 @@
+<?php
+
+namespace App\Shared\Event\Message;
+
+/**
+ * پیام نشانه‌ای که زمان‌بند هر دقیقه می‌فرستد تا صندوق خروجی تخلیه شود.
+ *
+ * خودش داده ندارد: «چه چیزی منتشر شود» را `OutboxPublisher` از جدول می‌خواند، نه از
+ * پیام — وگرنه رویدادی که بین دو تیکِ زمان‌بند ثبت شده جا می‌ماند.
+ */
+final class PublishDomainEventsMessage
+{
+}

src/Shared/Event/MessageHandler/PublishDomainEventsHandler.php

@@ -0,0 +1,18 @@
+<?php
+
+namespace App\Shared\Event\MessageHandler;
+
+use App\Shared\Event\Message\PublishDomainEventsMessage;
+use App\Shared\Event\Service\OutboxPublisher;
+use Symfony\Component\Messenger\Attribute\AsMessageHandler;
+
+#[AsMessageHandler]
+final class PublishDomainEventsHandler
+{
+    public function __construct(private readonly OutboxPublisher $publisher) {}
+
+    public function __invoke(PublishDomainEventsMessage $message): void
+    {
+        $this->publisher->publish();
+    }
+}

src/Shared/Event/Service/OutboxPublisher.php

@@ -0,0 +1,62 @@
+<?php
+
+namespace App\Shared\Event\Service;
+
+use App\Shared\Event\Message\DomainEventMessage;
+use App\Shared\Event\Repository\DomainEventLogRepository;
+use Doctrine\ORM\EntityManagerInterface;
+use Symfony\Component\Messenger\MessageBusInterface;
+
+/**
+ * تخلیهٔ صندوق خروجی — ردیف‌های `published_at IS NULL` به messenger می‌روند.
+ *
+ * منطق اینجاست نه در Command، چون دو فراخوان دارد: دستور دستی برای وقتی که صف عقب
+ * افتاده، و زمان‌بند برای اجرای همیشگی. اگر در Command می‌ماند، زمان‌بند مجبور بود
+ * پروسهٔ کنسول اجرا کند و خطاهایش را از exit code حدس بزند.
+ */
+final class OutboxPublisher
+{
+    public function __construct(
+        private readonly DomainEventLogRepository $events,
+        private readonly MessageBusInterface      $bus,
+        private readonly EntityManagerInterface   $em,
+    ) {}
+
+    /**
+     * شکستِ یک ردیف بقیه را متوقف نمی‌کند؛ `attempts` بالا می‌رود و خطا روی خودِ ردیف
+     * می‌نشیند تا بعد از سقف تلاش، با دلیلش قابل دیدن بماند.
+     *
+     * @return array{published: int, failed: int}
+     */
+    public function publish(int $limit = 100): array
+    {
+        $pending   = $this->events->findPending(max(1, $limit));
+        $published = 0;
+        $failed    = 0;
+
+        foreach ($pending as $event) {
+            try {
+                $this->bus->dispatch(new DomainEventMessage(
+                    $event->getUuid(),
+                    $event->getName(),
+                    $event->getEntityType(),
+                    $event->getEntityId(),
+                    $event->getPayload(),
+                    $event->getOccurredAt(),
+                ));
+
+                $event->markPublished();
+                $published++;
+            } catch (\Throwable $e) {
+                $event->markFailed($e->getMessage());
+                $failed++;
+            }
+        }
+
+        if ($pending !== []) {
+            $this->em->flush();
+        }
+
+        return ['published' => $published, 'failed' => $failed];
+    }
+}