{{-- `name` is excluded from the client rule set — its `unique` would render as a REMOTE check — so its `required` is re-armed from the attributes below, read by nrems-client-rules.js. The message is the SERVER's own, from the lang layer with the same displayable attribute the FormRequest uses, so the two sides say one sentence. Renaming is allowed for every role that reaches this screen (decision D11): people hold a role by id, so the holders are unaffected, and UpdateRoleRequest's unique rule ignores this row. --}} {{-- The Role Code slot, kept empty so the row stays two tracks wide and Role Name keeps its half. --}}

{{-- v12 draws this as a bare checkbox and a label side by side with the helper line under the pair, and no `.form-label` above it (edit-role.html:143-149). with no label is exactly that shape, and it brings the hint line and the inline error with it. The control is hand-written rather than an because the library ships no single-checkbox component: checkbox-group renders a grid of boxes posting one array name, which is a different control. It stays editable on this screen. `is_system` blocks DELETION and nothing else (decision D1's weaker half), so an administrator may promote or demote a role without the flag ever becoming a one-way door. --}}

{{-- The Status slot, kept empty for the same reason as the Role Code one above. --}}

{{-- `table-wrapper` is v12's own scroll box; `table-responsive` rides along because it is Bootstrap's name for the same thing and the one the rest of this application uses. The grid is ten rows and five columns, so it scrolls sideways on a phone rather than compressing the module names — which is why `.rl-permission-table tbody td:first-child` is `nowrap`. The table is written out here and again in the twin rather than pulled into a shared partial: recipe §9's twin rule is that both form files spell out every field, with no shared form partial, and this grid IS the second field on the screen. What keeps the duplication honest is that neither copy contains a list — both iterate $modules, which the controller reads from App\Support\RolePermissionMatrix, so a module added there appears on both screens with neither file changing. --}}

@foreach (\App\Support\RolePermissionMatrix::ACTIONS as $action) @endforeach @foreach ($modules as $module) @foreach ($module['cells'] as $action => $permission) {{-- A null cell renders EMPTY and keeps its @endforeach @endforeach

{{ __('roles.matrix.columns.module') }}	{{ __('roles.matrix.columns.'.$action) }}
{{ __('roles.matrix.modules.'.$module['key']) }}	(decision D7): Booking and Cancellation have no Delete checkbox, and dropping the cell would shift every column after it out of line. --}}	@if ($permission !== null) {{-- The two data- attributes are how nrems-role-form.js finds a box. It never parses the label beside it, which would have made the auto-check rules one translation away from silently not firing. aria-label because the visible label for these boxes is the column header plus the row heading, and a screen reader announcing "checkbox" thirty- eight times is not a form. --}} @endif

{{-- v12's card footer: Cancel as the outline button, then the primary action, both right-aligned inside the card's bottom rule. `.card-footer` is already the flex row, so no wrapper of its own. --}}