{{--
    The "Proceed to Booking" control — v12 draws it on view-inquiry.html,
    add-inquiry.html and follow-up.html, in the wireframe's success fill under
    the `.btn-outline` class (`.btn.btn-booking` in the module's style partial).

        @include('inquiries.partials.proceed-to-booking', ['inquiry' => $inquiry])

    CR-6 §1 made it a deliberately inert disabled <button>, because the Booking
    module did not exist yet. **CR-8 §3.5 is the CR that exists**, so on the
    three screens that HAVE an inquiry the control is now a live link to
    `bookings.create?inquiry={id}`, which opens the New Booking form prefilled
    from this inquiry.

    A partial rather than the same six lines in three views: the *state* logic
    below is a rule about bookings, and three copies of a rule about when a
    button is available is three chances for one screen to offer a booking the
    server would refuse. inquiries/create.blade.php deliberately does NOT
    include it — that screen has no inquiry to book yet, so its button stays the
    disabled one it always was.

    ## The three states

      * **Live link** — the user holds `bookings.create`, this inquiry has no
        live booking, and it is not already `booking_confirm`.
      * **Disabled, "Booking already exists"** — a booking is already holding
        this inquiry, or its status says one confirmed it. Both are the same
        fact from two directions (Booking::scopeLive() and
        BookingService::confirmInquiry() write them together), and both are
        checked because either can be true without the other after a manual
        data change. The title text is inline, per CR-8 §0.1.

        The status half of that pair is also CR-6.2's lock, reached from the
        other side: this control was already refusing a `booking_confirm`
        inquiry before the client asked for the lock, which is why this file
        needed no change for it. The listing's Booking Action option — the one
        place that still offered a second booking on a booked inquiry — is what
        CR-6.2 closed. Note the `hasLiveBooking()` call below is CORRECT here
        and deliberately not swapped for isLockedByBooking(): this screen asks
        the wider "is any live booking holding this inquiry" question, on one
        model, once per page; the lock asks the narrower status question, per
        listing row, where a query would not be free.
      * **Disabled, no title** — the user cannot create bookings. Not the
        "coming soon" title it used to carry: the module is here, and telling a
        salesperson without the permission that it is coming soon would be a
        lie about a permission problem.

    An anchor when it is live and a <button disabled> when it is not, and not an
    anchor without an href in either case: an anchor with no href is not
    focusable and reads as decoration, while a disabled button reads as a
    control that is not available.
--}}
@php
    /** @var \App\Models\Inquiry $inquiry */
    $bookingExists = $inquiry->status === \App\Enums\InquiryStatus::BookingConfirm
        || $inquiry->hasLiveBooking();
    $mayBook = auth()->user()?->can('bookings.create') === true;
@endphp
@if ($mayBook && ! $bookingExists)
    <a href="{{ route('bookings.create', ['inquiry' => $inquiry->id]) }}" class="btn btn-outline btn-booking">
        <i class="fa-solid fa-file-contract" aria-hidden="true"></i>{{ __('inquiries.actions.proceed_to_booking') }}
    </a>
@else
    <button type="button" class="btn btn-outline btn-booking" disabled
            @if ($bookingExists) title="Booking already exists" @endif>
        <i class="fa-solid fa-file-contract" aria-hidden="true"></i>{{ __('inquiries.actions.proceed_to_booking') }}
    </button>
@endif