{{--
Row actions for the Cancellations DataTable —
docs/wireframes-v12/cancellation.html (~line 160):
Two controls and only two, which is the wireframe's own pair: there is no
delete here and no permission that could gate one (CR-9 §3.5) — undoing a
cancellation would mean re-taking a unit that may have been sold again since,
which is a new booking rather than an undo.
Neither is conditional on the row's state, unlike the bookings listing's
equivalents: every row this table draws is cancelled, and a cancelled booking
is exactly what both of these screens exist for.
Rendered by CancellationsDataTable through rawColumns(['actions']), which
means this output is injected into the page unescaped. **Nothing
user-controlled reaches it**: the only dynamic values are two route urls
built from the model key. There is no confirm() string and therefore no
Js::from() — the destructive action moved to its own screen in CR-9, and this
partial has nothing left to quote.
Every control is gated on its own bare permission rather than on one blanket
check, so a user with `cancellations.view` alone gets the eye and nothing
else. Bare permissions and not a policy — CR-9 §0.4.
yajra hands the row's model in as $model.
--}}
@php
/** @var \App\Models\Booking $model */
@endphp