Keep a button at its label's width in a stack and a form

<x-stack> stretches its children across by default and <x-form> is a
one-track grid, so a button written directly in either drew as a
full-width pill. M3 keeps a button's width "dynamic to fit label" and
says not to "stretch buttons into long flat shapes on large windows".
A button there now sits at the start edge at its own width; a stack
aligned start, centre or end is untouched, and an application's own
width still wins (a cap on the button itself was rejected for exactly
that: it would have limited an app's inline-size, which CascadeTest
guards). Chromium test in both directions, failing without the rules.
Decided with the user (plan step 46).

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

tests/Feature/Components/FieldTest.php

@@ -297,3 +297,9 @@ it('draws the file picker\'s button from its own stylesheet', function () {
         ->and((string) file_get_contents(__DIR__.'/../../../resources/css/components/field.css'))->not->toContain("[type='file']")
         ->and((string) file_get_contents(__DIR__.'/../../../resources/css/all.css'))->toContain("@import './components/file.css';");
 });
+
+it('keeps a button written among a form\'s fields at its label\'s width', function () {
+    // M3: keep a button's width "dynamic to fit label"; don't "stretch buttons into long flat shapes".
+    expect(ComponentStylesheet::read('form')->declarations('[data-md-form] > [data-md-button]'))
+        ->toBe(['justify-self' => 'start']);
+});