Take full on the searchable choice and the pickers, as on every field

`full` takes the 40rem bound off `[data-md-field]` from `medium`, and
`<x-input>`, `<x-password>`, `<x-textarea>`, `<x-select>` and `<x-file>`
pass it to the field they draw. `<x-choices searchable>`,
`<x-datepicker>` and `<x-timepicker>` draw the same field but did not
declare the prop, and their roots only forward `class` and `style`, so
`full` reached no element and the field stopped at 40rem: ReStride's
time zone choice stood narrower than the rows filling its card.

The three now declare `full` and pass it to their field (the date
picker's own field, not the dialog's entry fields). `<x-choices>`' chips
are not a field and have no bound, so they take `full` and render
nothing for it, and a call site can switch `searchable` on and off
without it. The docblocks and the skill list every component that takes
it.

The browser test that bounds a field at 600px now measures a bounded
and a `full` searchable choice, date picker and time picker too; it
fails without the change in Chrome, Firefox and Safari. A feature test
renders `full` on every field-shaped component and none on the chips.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

resources/views/components/choices.blade.php

@@ -12,7 +12,8 @@
        caret), Enter chooses, Escape puts the field back — WAI-ARIA's combobox keyboard, since M3
        has no combobox. One value only. The list is a popover in the top
        layer, placed by CSS anchor positioning, so a card's clipping never cuts it off. `icon`,
-       `variant` and `placeholder` are the field's.
+       `variant` and `placeholder` are the field's, and `full` takes the 40rem bound off the field
+       as it does off every field. Chips have no such bound, so they take `full` and change nothing.
 
      The selection lives in Alpine, entangled with the `wire:model` property (live with
      `wire:model.live`), rather than in native checkboxes, which would send every value back as a
@@ -38,6 +39,7 @@
     'variant' => null,
     'placeholder' => null,
     'value' => null,
+    'full' => false,
 ])
 
 @php
@@ -134,7 +136,7 @@
         @if ($model === null) x-modelable="value" @endif
     >
         <div style="anchor-name: {{ $anchor }}">
-            <x-livewire-material::field :$id :$label :$hint :$messages :$icon :$variant>
+            <x-livewire-material::field :$id :$label :$hint :$messages :$icon :$variant :$full>
                 <input
                     id="{{ $id }}"
                     type="text"

resources/views/components/datepicker.blade.php

@@ -26,9 +26,10 @@
      range as one update so `after_or_equal:period.start` validates against the end it came
      with, and the errors for `period`, `period.start` and `period.end` all belong to this field.
      `min` and `max` (`Y-m-d` or a date object) disable the days outside them and keep the
-     keyboard inside them. `label`, `hint`, `icon`, `variant` (`outlined`, `filled`) and `size`
-     are the field's; `clearable` adds a button that empties it (a date, or both ends of a range)
-     once it holds one; `name` adds hidden inputs carrying `Y-m-d` for a plain form post. `class` and
+     keyboard inside them. `label`, `hint`, `icon`, `variant` (`outlined`, `filled`), `size` and
+     `full` (the 40rem bound taken off) are the field's; `clearable` adds a button that empties it
+     (a date, or both ends of a range) once it holds one; `name` adds hidden inputs carrying
+     `Y-m-d` for a plain form post. `class` and
      `style` land on the root; every other attribute (`required`, `disabled`, `readonly`) reaches
      the text field. Errors under
      the `wire:model` name replace the hint, and so does a typed date that cannot be read.
@@ -67,6 +68,7 @@
     'clearable' => false,
     'weekStart' => null,
     'format' => null,
+    'full' => false,
 ])
 
 @php
@@ -168,6 +170,7 @@
             :$icon
             :$size
             :$variant
+            :$full
             :data-md-invalid="$invalid ? '' : null"
             :data-md-readonly="$attributes->get('readonly') ? '' : null"
             x-bind:data-md-invalid="(fieldError !== '' || {{ $invalid ? 'true' : 'false' }}) ? '' : null"

resources/views/components/timepicker.blade.php

@@ -23,9 +23,9 @@
      multiple of the step; a drag and the arrows move by the step). `min` and `max` (`H:i`, inclusive;
      a `min` later than `max` spans midnight) grey out and skip what lies outside them and turn typed
      values outside them into errors — validate on the server as well. `clearable` adds a button that
-     empties the field; `name` posts the value from a hidden input. `label`, `hint`, `icon`, `variant`
-     and `size` are the field's; `class` and `style` land on the root, other attributes (`required`,
-     `disabled`, `placeholder`) reach the field's input.
+     empties the field; `name` posts the value from a hidden input. `label`, `hint`, `icon`, `variant`,
+     `size` and `full` (the 40rem bound taken off) are the field's; `class` and `style` land on the
+     root, other attributes (`required`, `disabled`, `placeholder`) reach the field's input.
 
      From androidx Compose Material 3 at commit 27cf9a7d5788aa0f5f2d8b6699ce279560daf326 (Apache-2.0):
      TimePickerTokens and TimeInputTokens — a surface-container-high dialog with an extra-large
@@ -56,6 +56,7 @@
     'value' => null,
     'name' => null,
     'clearable' => false,
+    'full' => false,
 ])
 
 @php
@@ -143,7 +144,7 @@
     x-data="materialTimepicker(@if ($model !== null) @entangle($attributes->wire('model')) @else @js($current) @endif, @js($config))"
     @if ($model === null) x-modelable="value" @endif
 >
-    <x-livewire-material::field :$id :$label :$hint :$messages :$icon :$size :$variant data-md-timepicker-field>
+    <x-livewire-material::field :$id :$label :$hint :$messages :$icon :$size :$variant :$full data-md-timepicker-field>
         <input
             {{ $inputAttributes }}
             id="{{ $id }}"