<?php

declare(strict_types=1);

namespace App\Events\FormBuilder;

use Illuminate\Broadcasting\InteractsWithSockets;
use Illuminate\Broadcasting\PrivateChannel;
use Illuminate\Contracts\Broadcasting\ShouldBroadcast;
use Illuminate\Foundation\Events\Dispatchable;
use Illuminate\Queue\SerializesModels;

/**
 * Broadcast when TriggerPersonIdentityMatchOnFormSubmit (D2) writes the
 * final identity_match_status. Frontend portal IdentityMatchBanner
 * subscribes to this channel and refetches the submission resource on
 * receipt, so the banner copy transitions from "we're checking matches…"
 * to the final state without a manual reload.
 *
 * Per RFC-WS-6 §Q1 v1.3 addition 2.
 *
 * Wiring (the dispatch call from TriggerPersonIdentityMatchOnFormSubmit::handle)
 * lands in D2. This class exists in D1 so D2's wiring is a one-liner.
 */
final class FormSubmissionIdentityMatchResolved implements ShouldBroadcast
{
    use Dispatchable;
    use InteractsWithSockets;
    use SerializesModels;

    public function __construct(
        public readonly string $submissionId,
        public readonly string $status,        // 'matched' | 'no_match' | 'multiple_candidates'
        public readonly int $matchCount,
    ) {}

    /**
     * Private channel keyed on submission ULID.
     *
     * Frontend subscribes via `Echo.private('submission.${submissionId}')`.
     * Authorization (only the submitter / organisation admins can subscribe)
     * is the responsibility of the channel-authorization callback in
     * routes/channels.php — that wiring lands in D2 alongside the dispatch.
     *
     * @return array<int, PrivateChannel>
     */
    public function broadcastOn(): array
    {
        return [
            new PrivateChannel("submission.{$this->submissionId}"),
        ];
    }

    public function broadcastAs(): string
    {
        return 'identity-match.resolved';
    }
}