nitro_kit 2.0.0.alpha.1 → 2.0.0.alpha.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4c85a9304b86e7fa5d7e77eb872ae140648189174928805acaef127899fc59a0
-  data.tar.gz: 43ff42ab7cabb3dc18eee28b4958d55b35e9e1ce5bfee57627f259fc94506c33
+  metadata.gz: 2cfb9e904d8890216a6c778b5dd10655e22f77fa7508fd4d9eb9521453b61cd8
+  data.tar.gz: 3c9564fa27b68e1a10c1febe8b7104416251a5203b1bd25aa89b1617cab1e116
 SHA512:
-  metadata.gz: 3a086bc5c2a642706b29932f04461f7c368b8370ec1c840fc8e604ec7ea7e2d0dd34e7ba7b13c13b62f0821dbb9fbd97a70126894347259bcd105e3f21635d4c
-  data.tar.gz: f55aa48a8699baf35ffa1523c9ee3af232dc6513fdc89fa2905425063a8e5a532e032e675b3b3ead1663fa20458f09a7559fa2a2627b54650b828478e8f48e6a
+  metadata.gz: de02c676e41ea2cb0d674de967efa9c73aa8d6f65195af0bfae0ce35e305dc9fb5e53979659e5feed738cf0fdc4e968902931be726a5d1bd67f22a400ce3c0b2
+  data.tar.gz: 2ffdd83fe0f4005c5146a3d9e4fa13e7ce8a6b6d84d0a7e881aace598a6ff938836b20c15f29bde5f9d72e9bed8ef2e4a6b8a083add6986a0acdacb653221a4e

data/CHANGELOG.md

@@ -1,5 +1,26 @@
 # Changelog
 
+## 2.0.0.alpha.2
+
+This alpha keeps the 2.0 API experimental while incorporating the first full
+catalog-pattern and external-agent testing pass.
+
+### Changed
+
+- Add the setup-only installer, project-local agent guidance, diagnostics, and
+  initialization prompt used by new and existing Rails applications.
+- Align desktop page-header actions with the title edge and improve nested
+  table and responsive dropzone composition.
+- Exercise desktop pointer capabilities in browser CI with environment-matched
+  Chrome tooling.
+
+### Fixed
+
+- Improve warning, destructive, form-error, and dark-mode contrast.
+- Preserve native list and fieldset semantics in form errors and grouped
+  controls.
+- Fix table-cell alignment leakage and cramped upload actions at narrow widths.
+
 ## 2.0.0.alpha.1
 
 Nitro Kit 2.0 alpha is a ground-up, intentionally incompatible rebuild around gem-owned Phlex composition. It replaces the generated, helper-driven 1.x architecture with a versioned component system owned by the gem.

data/README.md

@@ -6,14 +6,16 @@
 
 **Rails front-end for the agent era.**
 
-Nitro Kit is a gem-owned, agent-native UI system for Ruby on Rails. The `2.0.0.alpha.1` prerelease is a ground-up rebuild. The free core is available now; new documentation and the verified Nitro Kit Pro catalog are coming next.
+Nitro Kit is a gem-owned, agent-native UI system for Ruby on Rails. The `2.0.0.alpha.2` prerelease is a ground-up rebuild under active testing and must not be treated as stable. New documentation and the Nitro Kit Pro alpha catalog are coming next.
 
 [![RubyGems](https://img.shields.io/gem/v/nitro_kit.svg)](https://rubygems.org/gems/nitro_kit)
 
 ## Installation
 
+Install the alpha explicitly and keep it pinned while evaluating it.
+
 ```ruby
-gem "nitro_kit", "2.0.0.alpha.1"
+gem "nitro_kit", "2.0.0.alpha.2"
 ```
 
 Use the released gem and commit `Gemfile` with `Gemfile.lock`. Before upgrading, review the changelog, run `bundle update nitro_kit`, rerun the installer, and test the application.

data/app/assets/stylesheets/nitro_kit.css

@@ -105,7 +105,7 @@
     --nk-color-success-content: oklch(0.393 0.095 152.535);
     --nk-color-warning: oklch(0.681 0.162 75.834);
     --nk-color-warning-content: oklch(0.421 0.095 57.708);
-    --nk-color-danger: oklch(0.637 0.237 25.331);
+    --nk-color-danger: oklch(0.577 0.237 25.331);
     --nk-color-danger-foreground: oklch(1 0 0);
     --nk-color-danger-content: oklch(0.444 0.177 26.899);
     --nk-color-overlay: oklch(0 0 0 / 0.5);
@@ -200,8 +200,8 @@
       transparent 10%
     );
     --nk-color-danger-hover: light-dark(
-      oklch(0.577 0.245 27.325),
-      oklch(0.637 0.237 25.331)
+      oklch(0.54 0.237 25.331),
+      oklch(0.59 0.237 25.331)
     );
     --nk-app-shell-background: var(--nk-color-canvas);
     --nk-app-shell-sidebar-background: var(--nk-color-surface);
@@ -578,7 +578,7 @@
 
   :where([data-nk="alert"] > [data-slot="alert-description"]) {
     max-width: var(--nk-content-lg);
-    color: color-mix(in oklab, var(--_nk-alert-foreground) 82%, transparent);
+    color: var(--_nk-alert-foreground);
     text-wrap: pretty;
   }
 }
@@ -3485,7 +3485,9 @@
   }
 
   :where([data-nk="dropzone"] [data-slot="dropzone-remove-control"]) {
-    min-block-size: var(--nk-control-height-sm);
+    grid-column: -2 / -1;
+    justify-self: end;
+    min-block-size: var(--nk-control-height-md);
     padding-inline: calc(var(--nk-space) * 2);
     color: var(--nk-color-foreground);
     background: var(--nk-color-surface);
@@ -3500,6 +3502,13 @@
     border-color: var(--nk-color-primary);
   }
 
+  :where(
+    [data-nk="dropzone"][data-presentation="minimal"][data-state="idle"]
+      > [data-slot="dropzone-status"]
+  ) {
+    text-align: center;
+  }
+
   :where([data-nk="dropzone"][data-state="uploading"]) {
     border-color: var(--nk-color-info);
   }
@@ -5178,11 +5187,9 @@
     }
 
     /* Every text slot owns the first column, so the eyebrow, title, and
-       description each keep a row of their own. Sparse auto-placement then
-       lands the actions in the last of those rows. No row span is declared:
-       a span resolves against explicit rows this grid does not have, which is
-       what used to seat the actions beside the eyebrow and push the title down
-       onto a line of its own. */
+       description each keep a row of their own. Actions explicitly occupy
+       the first row so their top edge aligns with the header instead of
+       dropping beside the final line of supporting text. */
     :where(
       [data-nk="page-header"]:has(> [data-slot="page-header-actions"])
         > :not([data-slot="page-header-actions"])
@@ -5192,8 +5199,9 @@
 
     :where([data-nk="page-header"] > [data-slot="page-header-actions"]) {
       grid-column: 2;
+      grid-row: 1;
       justify-self: end;
-      align-self: end;
+      align-self: start;
       margin-block-start: 0;
     }
   }
@@ -5394,7 +5402,7 @@
     [data-nk="badge"][data-color="warning"],
     [data-nk="alert"][data-variant="warning"]
   ) {
-    --_nk-palette-light: oklch(55.5% 0.163 48.998);
+    --_nk-palette-light: oklch(55% 0.163 48.998);
     --_nk-palette-dark: oklch(92.4% 0.12 95.746);
     --_nk-palette-tint: oklch(82.8% 0.189 84.429);
   }
@@ -6502,10 +6510,16 @@
 }
 
 @layer nitro-kit.compound {
-  :where([data-nk="table"] [data-align="center"]) {
+  :where(
+    [data-nk="table"] [data-slot="table-header"][data-align="center"],
+    [data-nk="table"] [data-slot="table-cell"][data-align="center"]
+  ) {
     text-align: center;
   }
-  :where([data-nk="table"] [data-align="right"]) {
+  :where(
+    [data-nk="table"] [data-slot="table-header"][data-align="right"],
+    [data-nk="table"] [data-slot="table-cell"][data-align="right"]
+  ) {
     font-variant-numeric: tabular-nums;
     text-align: right;
   }

data/app/components/nitro_kit/checkbox_group.rb

@@ -52,8 +52,11 @@ module NitroKit
         attributes: {
           id: @id,
           disabled: @disabled,
-          aria: { required: @required ? "true" : nil }.compact,
-          data: { orientation: @orientation, presentation: @presentation }
+          data: {
+            orientation: @orientation,
+            presentation: @presentation,
+            required: @required ? "true" : nil
+          }.compact
         }.compact,
         html:,
         aria:,

data/app/components/nitro_kit/field.rb

@@ -175,7 +175,7 @@ module NitroKit
       ul(
         **slot_attributes(
           :error,
-          attributes: { id: errors_id, role: "alert" }.compact,
+          attributes: { id: errors_id, aria: { live: "assertive" } }.compact,
           html:,
           aria:,
           data:,

data/app/components/nitro_kit/radio_button_group.rb

@@ -45,8 +45,11 @@ module NitroKit
         attributes: {
           id: @id,
           disabled: @disabled,
-          aria: { required: @required ? "true" : nil }.compact,
-          data: { orientation: @orientation, presentation: @presentation }
+          data: {
+            orientation: @orientation,
+            presentation: @presentation,
+            required: @required ? "true" : nil
+          }.compact
         }.compact,
         html:,
         aria:,

data/docs/agent_native_spec.md

@@ -1,6 +1,6 @@
 # Nitro Kit 2.0 — agent-native Phlex UI system
 
-This is the canonical architecture specification for the stable Nitro Kit 2.0 line. The delivery sequence and ticket map are retained in [`implementation_plan.md`](implementation_plan.md) as design history; `tk` is the source of truth for live work status. [`component_contracts.md`](component_contracts.md) records the shipped Ruby and integration contracts.
+This is the canonical architecture specification for the stable Nitro Kit 2.0 line. `tk` is the source of truth for live work status, and [`component_contracts.md`](component_contracts.md) records the shipped Ruby and integration contracts.
 
 Nitro Kit is a gem-owned, versioned UI system for Rails. Developers and coding agents compose application interfaces in Ruby with Phlex. Nitro Kit owns component behavior, rendered structure, and default aesthetics. Applications own product code and documented theme overrides, not copies of Nitro Kit internals.
 
@@ -404,7 +404,7 @@ These ideas require new evidence and a deliberate future API decision. Their app
 
 The pivot was delivered in evidence-seeking stages: establish the kernel and representative vertical slice, migrate atoms, build atom-only product flows, record repeated friction, extract only proven layouts and page sections, expand the gallery, remove 1.x, then consolidate behavior, packaging, and documentation.
 
-The first evidence pass rejected more abstractions than it accepted. `Spacer`, `Split`, `Frame`, App/Marketing shells, AuthenticationPanel, and ProgressSteps stayed out because those flows did not establish a stable cross-domain responsibility. That pass initially extracted separate `VStack` and `HStack` components plus a fixed three-column Grid. The later responsive-layout consolidation superseded those APIs with unified `Flex` and responsive `Grid`; [`notes/block_candidates.md`](../notes/block_candidates.md) retains the original evidence as history. The application-layout mandate and the Sidebar and Top Navigation reference audit supplied enough repeated responsibility to approve `AppShell`; MarketingShell, AuthenticationPanel, and speculative layout primitives remain rejected.
+The first evidence pass rejected more abstractions than it accepted. `Spacer`, `Split`, `Frame`, App/Marketing shells, AuthenticationPanel, and ProgressSteps stayed out because those flows did not establish a stable cross-domain responsibility. That pass initially extracted separate `VStack` and `HStack` components plus a fixed three-column Grid. The later responsive-layout consolidation superseded those APIs with unified `Flex` and responsive `Grid`. The application-layout mandate and the Sidebar and Top Navigation reference audit supplied enough repeated responsibility to approve `AppShell`; MarketingShell, AuthenticationPanel, and speculative layout primitives remain rejected.
 
 ## Definition of done
 

data/docs/component_contracts.md

@@ -1,6 +1,6 @@
 # Nitro Kit 2.0 component contracts
 
-This is the shipped public catalog for `2.0.0.alpha.1`. It describes current Ruby construction, rendered roots, closed vocabularies, compound cardinalities, and integration boundaries. Other candidate abstractions and the historical delivery plan are not public API.
+This is the shipped public catalog for `2.0.0.alpha.2`. It describes current Ruby construction, rendered roots, closed vocabularies, compound cardinalities, and integration boundaries. Other candidate abstractions and the historical delivery plan are not public API.
 
 ## Shared component boundary
 
@@ -44,17 +44,17 @@ Every default string a person can read or hear comes from the engine-loaded `nit
 | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `AppearancePicker` | required `id:`; `label:` defaulting to `I18n.t("nitro_kit.appearance_picker.label")`; `presentation: :segmented`; `preference: :system`                                                                                                                                                                                                                           | `fieldset`, `label`, or `div[data-nk=appearance-picker]`; presentations `segmented radios select dropdown`; preferences `light dark system`                        | Owns labelled native choices or an icon-only Dropdown trigger with icon-led preference buttons. `preference:` renders the server-persisted choice as the initial `data-state`, checked radio, selected option, and trigger icon, so a stored preference does not flash. It requests changes from and subscribes to the document runtime; zero or many picker instances do not duplicate document media/storage listeners. `id:` follows the AppShell identifier contract. Preference names come from `nitro_kit.appearance_picker.preferences.*`.                                                                                              |
 | `Checkbox` | `label: nil`, `description: nil`, `id: nil`, `name: nil`, `value: "1"`, `unchecked_value: "0"`, `include_hidden: true`, `checked: false`, `indeterminate: false`, `disabled: false`, `required: false`, `invalid: false`, `size: :md`, `control_html: {}`, `control_aria: {}`, `control_data: {}` | `div[data-nk=checkbox]` containing a native checkbox input; sizes `md lg` | Requires label text, block content, or an accessible control name; a description requires a label or block and a non-blank String `id:` to bind `aria-describedby`. A named checkbox emits its unchecked hidden input by default, and `include_hidden: true` with a nil `unchecked_value` raises. `invalid: true` sets `aria-invalid` on the control. Checked state stays native; only `indeterminate: true` mounts the `nk--checkable` enhancer, which applies the native DOM property and owns `data-state="indeterminate"`. |
-| `CheckboxGroup` | required `legend:`, `options:`, `name:`; `value: []`, `id: nil`, `description: nil`, `orientation: :vertical`, `presentation: :list`, `unchecked_value: ""`, `include_hidden: true`, `disabled: false`, `required: false`, `size: :md` | native `fieldset[data-nk=checkbox-group]`; orientations `vertical horizontal`; presentations `list cards`; sizes `md lg` | Options are non-empty `Choice` values with unique values and IDs. Names normalize to `[]`; one group-level unchecked input is emitted by default and its `unchecked_value` stays Rails' array sentinel `""`. A name with no id-safe characters raises instead of skipping IDs. `required: true` marks the fieldset `aria-required`; it never marks individual checkboxes required. The legend and description scope the whole group, so choices do not repeat the description through `aria-describedby`. |
+| `CheckboxGroup` | required `legend:`, `options:`, `name:`; `value: []`, `id: nil`, `description: nil`, `orientation: :vertical`, `presentation: :list`, `unchecked_value: ""`, `include_hidden: true`, `disabled: false`, `required: false`, `size: :md` | native `fieldset[data-nk=checkbox-group]`; orientations `vertical horizontal`; presentations `list cards`; sizes `md lg` | Options are non-empty `Choice` values with unique values and IDs. Names normalize to `[]`; one group-level unchecked input is emitted by default and its `unchecked_value` stays Rails' array sentinel `""`. A name with no id-safe characters raises instead of skipping IDs. `required: true` marks application state as `data-required=true`; it does not emit invalid `aria-required` on the native fieldset or require every checkbox. The legend and description scope the whole group, so choices do not repeat the description through `aria-describedby`. |
 | `ControlGroup` | `label: nil`, `id: nil` | `div[data-nk=control-group]`; optional `role=group` when labelled | Requires direct content. Joins direct Input, Select, and Button children without taking ownership of their values or behavior. `addon(text)` renders a textual prefix, suffix, or unit. The group owns shared borders and logical corner geometry for copy fields, URL builders, and compact filter submissions. |
 | `Dropzone`         | required `id:`, `name:`; `label:` defaulting to `I18n.t("nitro_kit.dropzone.label")`, `description: nil`, `presentation: :input` (`input minimal`), `direct_upload: true`, `multiple: false`, `accept: nil`, `max_files: 1`, `max_bytes: nil`, `disabled: false`, `required: false`                                                                                                              | `div[data-nk=dropzone][data-presentation]`; states `idle drag uploading success error disabled`                                                                                       | Owns a labelled native input, description/error/live status, preview list, native progress, and remove controls. `label:` is the visible prompt heading and renders in the `dropzone-title` slot; it replaced the former `title:` keyword. Every other user-facing string comes from the `nitro_kit.dropzone.*` locale scope, and `CONTROLLER_MESSAGE_KEYS` hands the runtime strings to `nk--dropzone` as Stimulus values so no English lives in JavaScript. Limits are positive and consistent; `max_files` must be 1 unless `multiple: true`. Keyboard selection and `direct_upload: false` preserve ordinary form submission. `presentation: :minimal` hides the native input visually while keeping it focusable and named, so the drop target is the only visible affordance.                                                                                                                                                                                                                                                                                                                                  |
-| `Field`            | optional Rails form builder and field name; see the full signature below                                                                                                                                                                                                                                           | `div[data-nk=field][data-field-type=…]`; types listed below                                                                                                        | Default rendering owns label, description, control, and errors. A render block replaces the default composition. `label`, `description`, `control`, and `errors` remain available to custom compositions. The error region is a `role="alert"` list. Derived labels use `human_attribute_name` when the form object supplies one. `as: :radio_group` requires a legend and rejects `label: false`, falling back to `I18n.t("nitro_kit.field.options_legend")` when neither an explicit nor a derived label exists. `as: :combobox` binds the field label to `#{id}-input` through `for` and `aria-labelledby` and wires description, error, and invalid state onto the combobox input. |
+| `Field`            | optional Rails form builder and field name; see the full signature below                                                                                                                                                                                                                                           | `div[data-nk=field][data-field-type=…]`; types listed below                                                                                                        | Default rendering owns label, description, control, and errors. A render block replaces the default composition. `label`, `description`, `control`, and `errors` remain available to custom compositions. The error list keeps native list semantics and uses `aria-live=assertive`; controls reference it through `aria-describedby`. Derived labels use `human_attribute_name` when the form object supplies one. `as: :radio_group` requires a legend and rejects `label: false`, falling back to `I18n.t("nitro_kit.field.options_legend")` when neither an explicit nor a derived label exists. `as: :combobox` binds the field label to `#{id}-input` through `for` and `aria-labelledby` and wires description, error, and invalid state onto the combobox input. |
 | `RichTextArea`     | required captured editor content as an `ActiveSupport::SafeBuffer`; `id: nil`                                                                                                                                                                                                                                                                        | `div[data-nk=rich-text-area]` wrapping `div[data-slot=rich-text-area-editor]`                                                                                                                                      | `Field(as: :rich_text)` through `FormBuilder#field` is the expected path; construct `RichTextArea` directly only for a standalone editor. Wraps trusted output from the host application's rich-text helper. Nitro owns Field composition and theme variables; the editor owns inputs, attachments, and behavior.                                                                                                                                                                                                                                                                                                                                                                                                |
 | `FieldGroup`       | no component-specific keywords                                                                                                                                                                                                                                                                                     | `div[data-nk=field-group]`                                                                                                                                         | Requires a content block. It is the default vertical rhythm boundary for a standalone form's visible fields, submit control, and related links.                                                                                                                                                                                                                                                                                                                                                                                                                        |
 | `Fieldset`         | `legend: nil`, `description: nil`, `disabled: false`, `name: nil`                                                                                                                                                                                                                                                  | native `fieldset[data-nk=fieldset]`                                                                                                                                | Requires a content block and a legend through the constructor or the matching `legend` compound method; `description` accepts either form too. Declarations may appear anywhere in the block and always render legend → description → fields.                                                                                                                                                                                                                                                                                                                          |
 | `Input`            | `type: :text`, `id: nil`, `name: nil`, `value: nil`, `placeholder: nil`, `disabled: false`, `readonly: false`, `required: false`, `autocomplete: nil`, `min: nil`, `max: nil`, `step: nil`, `minlength: nil`, `maxlength: nil`, `multiple: false`, `accept: nil`, `pattern: nil`, `inputmode: nil`, `checked: nil` | native `input[data-nk=input]`; types `button checkbox color date datetime-local email file hidden month number password radio range search tel text time url week` | Every owned attribute is a keyword; passing one through `html:` raises and names the keyword. `type: :file` with a `value:` raises. Boolean attributes and length constraints are validated; minimum length cannot exceed maximum. Read-only controls have their own muted treatment. `type: :date` is the only date control; its CSS normalizes Safari's internal date editor alignment, so `Field`/`FormBuilder` `as: :date` inherits the fix.                                                                                                                       |
 | `Label`            | optional text; `for: nil`, `id: nil`                                                                                                                                                                                                                                                                               | native `label[data-nk=label]`                                                                                                                                      | Requires non-blank text or a content block.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
 | `RadioButton` | `label: nil`, `description: nil`, `id: nil`, `name: nil`, `value: "1"`, `checked: false`, `disabled: false`, `required: false`, `invalid: false`, `size: :md`, `control_html: {}`, `control_aria: {}`, `control_data: {}` | `div[data-nk=radio-button]` containing a native radio input; sizes `md lg` | Requires label text, block content, or an accessible control name; a description requires a label or block. `invalid: true` sets `aria-invalid` on the control. Selection is entirely native: no Stimulus controller and no mirrored `data-state`. |
-| `RadioButtonGroup` | required `legend:`, `options:`, `name:`; `value: nil`, `id: nil`, `description: nil`, `orientation: :vertical`, `presentation: :list`, `disabled: false`, `required: false`, `size: :md` | native `fieldset[data-nk=radio-button-group]`; orientations `vertical horizontal`; presentations `list cards segmented`; sizes `md lg` | Options are non-empty `Choice` values with unique values and IDs. A non-nil `value:` is compared by string value; `value: nil` selects nothing, including a choice whose value is `""`. A name with no id-safe characters raises instead of skipping IDs. `required: true` marks the fieldset `aria-required` and every native radio `required`. The legend and description scope the whole group, so choices do not repeat the description through `aria-describedby`. |
+| `RadioButtonGroup` | required `legend:`, `options:`, `name:`; `value: nil`, `id: nil`, `description: nil`, `orientation: :vertical`, `presentation: :list`, `disabled: false`, `required: false`, `size: :md` | native `fieldset[data-nk=radio-button-group]`; orientations `vertical horizontal`; presentations `list cards segmented`; sizes `md lg` | Options are non-empty `Choice` values with unique values and IDs. A non-nil `value:` is compared by string value; `value: nil` selects nothing, including a choice whose value is `""`. A name with no id-safe characters raises instead of skipping IDs. `required: true` marks application state as `data-required=true` and every native radio `required`; it does not emit invalid `aria-required` on the fieldset. The legend and description scope the whole group, so choices do not repeat the description through `aria-describedby`. |
 | `Select`           | `options: []`, `option_tags: nil`, `id: nil`, `name: nil`, `value: nil`, `include_blank: nil`, `prompt: nil`, `disabled: false`, `required: false`, `multiple: false`, `autocomplete: nil`, `control_html: {}`, `control_aria: {}`, `control_data: {}`                                                             | `span[data-nk=select]` wrapping a native select                                                                                                                    | `options:` and captured `option_tags:` are mutually exclusive, as are `include_blank:` and `prompt:`. `id:` and the `control_*` bags address the inner select; `html:`, `aria:`, and `data:` address the root span. Multiple names normalize to `[]`, drop the toggle icon, and accept array values.                                                                                                                                                                                                                                                                   |
 | `Switch` | `label: nil`, `description: nil`, `id: nil`, `name: nil`, `value: "1"`, `unchecked_value: "0"`, `include_hidden: true`, `checked: false`, `disabled: false`, `required: false`, `invalid: false`, `size: :md`, `control_html: {}`, `control_aria: {}`, `control_data: {}` | `div[data-nk=switch]` containing `input[type=checkbox][role=switch]`; sizes `md lg` | Uses native checkbox submission with an unchecked hidden input by default; checked state stays native, with no Stimulus controller and no mirrored `data-state`. Requires label text, block content, or an accessible control name; a description requires a label or block and is nested in the content slot beside the label text and connected with `aria-describedby`. The ARIA-only form renders the bare control and track without a label wrapper. `invalid: true` sets `aria-invalid` on the control. `role` is owned by Switch: a `control_html: { role: ... }` value is replaced by `role="switch"`. |
 | `Textarea`         | `id: nil`, `name: nil`, `value: nil`, `placeholder: nil`, `disabled: false`, `readonly: false`, `required: false`, `autocomplete: nil`, `rows: nil`, `cols: nil`, `minlength: nil`, `maxlength: nil`, `wrap: nil`                                                                                                  | native `textarea[data-nk=textarea]`; wraps `soft hard off`                                                                                                         | Every owned attribute is a keyword; passing one through `html:` raises and names the keyword. Rows and columns must be positive; lengths must be non-negative; minimum length cannot exceed maximum. Read-only controls have their own muted treatment.                                                                                                                                                                                                                                                                                                                |

data/docs/migration_1_to_2.md

@@ -9,7 +9,7 @@ Treat a 1.x migration as a product-flow review, not a helper rename. Nitro Kit
 Add the 2.0 alpha prerelease to the application's Gemfile:
 
 ```ruby
-gem "nitro_kit", "2.0.0.alpha.1"
+gem "nitro_kit", "2.0.0.alpha.2"
 ```
 
 Bundler records the exact released version in `Gemfile.lock`; commit `Gemfile`

data/docs/new_app_strategy.md

@@ -2,17 +2,15 @@
 
 Recommend a Rails application template for new applications, not a return to Nitro Kit's old component-copying generator.
 
-Rails application templates are designed to configure a new app during `rails new`, can add gems, and can run generators after Bundler finishes. That gives Nitro Kit an eventual one-command entry point:
+Rails application templates are designed to configure a new app during `rails new`, can add gems, and can run generators after Bundler finishes. Nitro Kit's starter therefore remains a thin one-command entry point:
 
 ```sh
 rails new my_app -m https://nitrokit.dev/template.rb
 ```
 
-The template should remain thin while the conventions settle. Its first
-version should add Nitro Kit and invoke `nitro_kit:install`. The generator owns
-the project-local skills and `AGENTS.md`; the template may add an application
-layout that renders the stylesheet, appearance bootstrap, and flash toasts. It
-must not copy Nitro components or their controllers.
+The template adds Nitro Kit and invokes `nitro_kit:install`. The generator owns
+the project-local skills and `AGENTS.md`. The template does not copy Nitro
+components, controllers, authentication, teams, billing, or product models.
 
 Existing applications install the gem directly and run the setup generator.
 Agent discovery, version-matched skill routing, diagnostics, and initialization

data/docs/rails_integration.md

@@ -7,7 +7,7 @@ Nitro Kit 2.0 uses Rails where Rails owns important application semantics: model
 Add the 2.0 alpha prerelease to the application's Gemfile:
 
 ```ruby
-gem "nitro_kit", "2.0.0.alpha.1"
+gem "nitro_kit", "2.0.0.alpha.2"
 ```
 
 Bundler records the exact released version in `Gemfile.lock`; commit `Gemfile`

data/lib/nitro_kit/upgrade_smoke_test.rb

@@ -244,7 +244,7 @@ module NitroKit
       assert_response :unprocessable_entity
       assert_select "turbo-frame##{UpgradeSmoke::FRAME_ID}", count: 1 do
         assert_select "input#profile_name[value='x'][aria-invalid='true'][aria-describedby~='profile_name-errors']"
-        assert_select "ul#profile_name-errors[data-slot='field-error'][role='alert'] > li", count: 1
+        assert_select "ul#profile_name-errors[data-slot='field-error'][aria-live='assertive']:not([role]) > li", count: 1
       end
       assert_select "section[data-nk='toast'] [data-nk='toast-item'][data-variant='error']"
     end
@@ -316,7 +316,7 @@ module NitroKit
         find("#nitro-kit-upgrade-smoke-form button[type='submit']").click
 
         assert_selector "#profile_name[value='x'][aria-invalid='true'][aria-describedby~='profile_name-errors']"
-        assert_selector "ul#profile_name-errors[data-slot='field-error'][role='alert'] > li", count: 1
+        assert_selector "ul#profile_name-errors[data-slot='field-error'][aria-live='assertive']:not([role]) > li", count: 1
         assert_selector "body section[data-nk='toast'] [data-nk='toast-item'][data-variant='error']"
         assert_stable_frame
 

data/lib/nitro_kit/version.rb

@@ -1,3 +1,3 @@
 module NitroKit
-  VERSION = "2.0.0.alpha.1"
+  VERSION = "2.0.0.alpha.2"
 end

data/src/stylesheets/nitro_kit/components/alert.css

@@ -48,7 +48,7 @@
 
   :where([data-nk="alert"] > [data-slot="alert-description"]) {
     max-width: var(--nk-content-lg);
-    color: color-mix(in oklab, var(--_nk-alert-foreground) 82%, transparent);
+    color: var(--_nk-alert-foreground);
     text-wrap: pretty;
   }
 }

data/src/stylesheets/nitro_kit/components/dropzone.css

@@ -115,7 +115,9 @@
   }
 
   :where([data-nk="dropzone"] [data-slot="dropzone-remove-control"]) {
-    min-block-size: var(--nk-control-height-sm);
+    grid-column: -2 / -1;
+    justify-self: end;
+    min-block-size: var(--nk-control-height-md);
     padding-inline: calc(var(--nk-space) * 2);
     color: var(--nk-color-foreground);
     background: var(--nk-color-surface);
@@ -130,6 +132,13 @@
     border-color: var(--nk-color-primary);
   }
 
+  :where(
+    [data-nk="dropzone"][data-presentation="minimal"][data-state="idle"]
+      > [data-slot="dropzone-status"]
+  ) {
+    text-align: center;
+  }
+
   :where([data-nk="dropzone"][data-state="uploading"]) {
     border-color: var(--nk-color-info);
   }

data/src/stylesheets/nitro_kit/components/page_header.css

@@ -40,11 +40,9 @@
     }
 
     /* Every text slot owns the first column, so the eyebrow, title, and
-       description each keep a row of their own. Sparse auto-placement then
-       lands the actions in the last of those rows. No row span is declared:
-       a span resolves against explicit rows this grid does not have, which is
-       what used to seat the actions beside the eyebrow and push the title down
-       onto a line of its own. */
+       description each keep a row of their own. Actions explicitly occupy
+       the first row so their top edge aligns with the header instead of
+       dropping beside the final line of supporting text. */
     :where(
       [data-nk="page-header"]:has(> [data-slot="page-header-actions"])
         > :not([data-slot="page-header-actions"])
@@ -54,8 +52,9 @@
 
     :where([data-nk="page-header"] > [data-slot="page-header-actions"]) {
       grid-column: 2;
+      grid-row: 1;
       justify-self: end;
-      align-self: end;
+      align-self: start;
       margin-block-start: 0;
     }
   }

data/src/stylesheets/nitro_kit/components/palette.css

@@ -28,7 +28,7 @@
     [data-nk="badge"][data-color="warning"],
     [data-nk="alert"][data-variant="warning"]
   ) {
-    --_nk-palette-light: oklch(55.5% 0.163 48.998);
+    --_nk-palette-light: oklch(55% 0.163 48.998);
     --_nk-palette-dark: oklch(92.4% 0.12 95.746);
     --_nk-palette-tint: oklch(82.8% 0.189 84.429);
   }

data/src/stylesheets/nitro_kit/components/table.css

@@ -100,10 +100,16 @@
 }
 
 @layer nitro-kit.compound {
-  :where([data-nk="table"] [data-align="center"]) {
+  :where(
+    [data-nk="table"] [data-slot="table-header"][data-align="center"],
+    [data-nk="table"] [data-slot="table-cell"][data-align="center"]
+  ) {
     text-align: center;
   }
-  :where([data-nk="table"] [data-align="right"]) {
+  :where(
+    [data-nk="table"] [data-slot="table-header"][data-align="right"],
+    [data-nk="table"] [data-slot="table-cell"][data-align="right"]
+  ) {
     font-variant-numeric: tabular-nums;
     text-align: right;
   }

data/src/stylesheets/nitro_kit/tokens.css

@@ -90,7 +90,7 @@
     --nk-color-success-content: oklch(0.393 0.095 152.535);
     --nk-color-warning: oklch(0.681 0.162 75.834);
     --nk-color-warning-content: oklch(0.421 0.095 57.708);
-    --nk-color-danger: oklch(0.637 0.237 25.331);
+    --nk-color-danger: oklch(0.577 0.237 25.331);
     --nk-color-danger-foreground: oklch(1 0 0);
     --nk-color-danger-content: oklch(0.444 0.177 26.899);
     --nk-color-overlay: oklch(0 0 0 / 0.5);
@@ -185,8 +185,8 @@
       transparent 10%
     );
     --nk-color-danger-hover: light-dark(
-      oklch(0.577 0.245 27.325),
-      oklch(0.637 0.237 25.331)
+      oklch(0.54 0.237 25.331),
+      oklch(0.59 0.237 25.331)
     );
     --nk-app-shell-background: var(--nk-color-canvas);
     --nk-app-shell-sidebar-background: var(--nk-color-surface);

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: nitro_kit
 version: !ruby/object:Gem::Version
-  version: 2.0.0.alpha.1
+  version: 2.0.0.alpha.2
 platform: ruby
 authors:
 - Mikkel Malmberg
@@ -179,7 +179,6 @@ files:
 - docs/component_contracts.md
 - docs/customization.md
 - docs/hotwire.md
-- docs/implementation_plan.md
 - docs/initialization_prompt.md
 - docs/migration_1_to_2.md
 - docs/new_app_strategy.md

data/docs/implementation_plan.md

@@ -1,279 +0,0 @@
-# Nitro Kit 2.0 implementation record
-
-This document records the staged delivery program used for the agent-native pivot. `tk` is the source of truth for live status and dependency order; ticket IDs below connect durable design intent to executable work. Candidate lists in early stages are historical investigation prompts, not current public API. The settled contract lives in [`agent_native_spec.md`](agent_native_spec.md) and [`component_contracts.md`](component_contracts.md).
-
-Nitro Kit 2.0 is allowed to break 1.x completely. Each stage should leave one simpler system behind rather than maintaining parallel APIs.
-
-The original implementation program reached release-quality consolidation. Component migration, evidence-gathering flows, accepted layout/block extraction, the expanded gallery, 1.x removal, documentation, packaging, and browser verification are retained here as history; later contract revisions such as responsive Flex/Grid remain tracked in `tk` and the canonical contract documents.
-
-## Definition of done
-
-The 2.0 pivot is complete when:
-
-- Every component is constructed directly from Phlex with explicit Ruby options.
-- Nitro Kit owns the Ruby, markup contract, behavior, CSS, examples, and documentation.
-- No Nitro-authored component, layout, block, flow, or gallery subject emits `class`, `style`, or an escape marker.
-- Applications can theme the system through documented `--nk-*` variables and compose or subclass components.
-- Rails forms, routes, assets, Turbo Frames, and Turbo Streams remain first-class.
-- The gem does not expose `nk_*` view helpers, copied-component generators, a Tailwind runtime, or a template-buffer bridge.
-- The complete catalog renders through explicit Rails routes in light/dark and narrow/wide states.
-- Keyboard behavior and Turbo lifecycle behavior pass browser tests.
-- The full Ruby, CSS, JavaScript formatting, package, and browser checks pass from a clean checkout.
-
-## Delivery rules
-
-Every migration ticket follows the same sequence:
-
-1. Define the smallest explicit Ruby API and closed vocabularies.
-2. Render native, self-describing HTML with `data-nk` and qualified `data-slot` identities.
-3. Preserve Rails and accessibility semantics before visual styling.
-4. Add static zero-specificity CSS driven by public theme tokens and private mechanics variables.
-5. Add focused render, invalid-option, reserved-attribute, and integration tests.
-6. Add representative and exhaustive gallery examples without classes or escape hatches.
-7. Verify the family independently before allowing dependent flows to use it.
-
-No compatibility layer should survive merely to keep a legacy example green. Replace the example and delete the obsolete API.
-
-## Stage 0 — ownership and execution scaffold
-
-Tickets: `nk-rzxf`, `nk-g3qu`
-
-- Work on the dedicated `2.0-agent-native` branch.
-- Keep the agent-native specification, component contracts, repository guidance, and this plan tracked with the gem.
-- Track the entire program in the workspace-level `.tickets` database.
-- Record implementation decisions and verification counts on each ticket before closing it.
-
-Gate: an agent can explain who owns Ruby, markup, CSS, behavior, theming, composition, and the class escape hatch by reading the tracked docs.
-
-## Stage 1 — kernel and distribution foundation
-
-Tickets: `nk-6q5i`, `nk-fooc`, `nk-rx0j`
-
-- Replace permissive attributes with explicit component options plus `html:`, `aria:`, and `data:` boundaries.
-- Centralize identity, slot attachment, reserved attributes, validation, additive Stimulus data, and `desperately_need_a_class:`.
-- Build deterministic layered CSS from split plain-CSS sources.
-- Ship the built stylesheet, optional Tailwind adapter, importmap pins, and controllers from the gem without vendored third-party JavaScript.
-- Prove the engine still boots when importmap-rails is absent.
-
-Gate: a minimal Rails app can render and style a Nitro component without copying sources or configuring Tailwind or JavaScript pins.
-
-## Stage 2 — representative vertical slice
-
-Ticket: `nk-g3x1`
-
-Migrate Button/Icon, Card, Input/Field/FormBuilder, Table, and Dialog all the way through Ruby, HTML, CSS, behavior, Rails integration, tests, and gallery routes.
-
-Use this slice to settle:
-
-- Direct compound-component methods and nested slot ownership.
-- Native attribute boundaries and error messages.
-- Intrinsic versus stretch sizing.
-- Rails form names, IDs, values, errors, multipart behavior, and checkbox semantics.
-- Native dialog behavior, stable ARIA relationships, and Stimulus cleanup.
-- The explicit gallery catalog and route contract.
-
-Gate: the slice is classless, invalid options fail immediately, focused tests pass, and its examples render through real Rails routes with Nitro CSS alone.
-
-## Stage 3 — complete atom migration
-
-Tickets: `nk-t17c`, `nk-b18t`, `nk-7lkw`, `nk-4r36`, `nk-i4xu`, `nk-19gd`
-
-### Display
-
-Migrate Alert, Avatar, AvatarStack, Badge, and Icon. Cover semantic intents, long content, image/fallback behavior, overflow, sizes, labeled/decorative icons, and nested combinations.
-
-### Actions and navigation
-
-Migrate ButtonGroup and Pagination. Preserve native links/buttons, current-page semantics, disabled previous/next controls, ellipses, compact ranges, and stable labels.
-
-### Forms
-
-Migrate Label, Textarea, Select, Checkbox, CheckboxGroup, RadioButton, RadioButtonGroup, Switch, FieldGroup, Fieldset, and all FormBuilder methods. Cover:
-
-- Bound and unbound forms.
-- Required, disabled, readonly, checked, indeterminate, invalid, prompt, and empty states.
-- Array and nested parameter names.
-- Active Model values and errors.
-- Multipart uploads and native file-input constraints.
-- Accessible descriptions, legends, labels, and error relationships.
-
-### Structured content
-
-Migrate Accordion and Tabs alongside the Card and Table slice. Require deterministic IDs and keys, direct compound APIs, semantic table structure, and keyboard-visible state.
-
-### Interaction
-
-Migrate Dropdown, Tooltip, Combobox, and Toast alongside Dialog. Require closed placement/state APIs, visible ARIA/data state, keyboard behavior, native controls where possible, and complete disconnect cleanup.
-
-Gate: every shipped atom has a classless direct-Phlex API, static CSS, focused tests, exhaustive examples, and no dependency on a legacy helper.
-
-## Stage 4 — Rails and Hotwire proof
-
-Ticket: `nk-19gd`
-
-- Exercise `form_with` directly from Phlex using `NitroKit::FormBuilder`.
-- Prove route helpers, DOM ID helpers, CSRF behavior, model errors, submit paths, and multipart forms.
-- Render Turbo Frames and Turbo Streams from direct-Phlex pages.
-- Add one small validation submit path that demonstrates the real request/response loop.
-- Document the supported Rails boundary and show examples without introducing Nitro view helpers.
-
-Gate: Rails supplies framework semantics while Phlex remains the only general UI composition language.
-
-## Stage 5 — gallery infrastructure and exhaustive combinations
-
-Tickets: `nk-q4mj`, `nk-put2`, `nk-jp63`, `nk-5028`, `nk-t23x`, `nk-rtwj`, `nk-8mh8`, `nk-t66i`, `nk-vnwu`
-
-- Keep one explicit catalog of component, block, and flow entries.
-- Render the shell, pages, sections, examples, samples, and notes in Phlex.
-- Pair every preview with highlighted, copyable Ruby extracted from the exact rendering block or concrete flow method.
-- Generate route contract tests from the catalog.
-- Assert every subject has stable Nitro identities and no `class`, `style`, or escape markers.
-- Add meaningful Cartesian coverage without mechanically showing nonsense combinations.
-
-Required pressure cases:
-
-- All closed variants and sizes.
-- Default, hover/focus-capable, disabled, readonly, invalid, empty, loading-like, open, and selected states where meaningful.
-- Short, long, wrapped, numeric, missing-image, and high-item-count content.
-- Nested atoms and compound slots.
-- Light and dark themes.
-- Narrow and wide viewports.
-- Forms, tables, overlays, and navigation used together rather than only in isolation.
-
-Gate: every catalog entry succeeds through an explicit route and the gallery itself requires no Tailwind or ERB templates.
-
-## Stage 6 — atom-only product flows
-
-Tickets: `nk-31ne`, `nk-7d05`, `nk-q37g`, `nk-tcig`, `nk-32vc`
-
-Build realistic screens before inventing layout abstractions:
-
-- Authentication, registration, password reset, and verification.
-- Onboarding progress, validation, resume, and completion.
-- Dashboard overview, statistics, recent records, and activity.
-- Profile, preferences, account, and destructive settings.
-- Billing plans, payment methods, invoices, and upgrade states.
-- Users search, filters, pagination, empty state, and detail.
-- Team members, invitations, roles, and removal confirmation.
-- API credential empty, create, reveal-once, list, and revoke states.
-
-Use deterministic PORO data and explicit state slugs. Record repeated layout and responsibility friction in `notes/block_candidates.md`; do not abstract a one-off screen.
-
-Gate: all required product states exist using atoms and plain Phlex composition, and repeated structures are backed by concrete evidence.
-
-## Stage 7 — evidence-driven layouts and blocks
-
-Tickets: `nk-okls`, `nk-bjv5`, `nk-b8eg`
-
-Extract the smallest vocabulary that removes proven repetition. The evidence pass accepted:
-
-- Layouts: VStack, HStack, the three-column Grid, and Container.
-- Shell: AuthShell.
-- Sections and blocks: SettingsLayout, Toolbar, PaginationBar, PageHeader, StatGrid, DataSection, FormSection, DangerZone, and EmptyState.
-
-This list records the first extraction decision. It has since been superseded: `VStack` and `HStack` were removed in favor of unified responsive `Flex`, and the fixed three-column Grid became a responsive 1–12-column `Grid`. See the canonical specification and component contracts for the current API.
-
-At that stage, the evidence pass deferred Spacer, Split, Frame, AppShell, MarketingShell, AuthenticationPanel, and ProgressSteps because their responsibilities were not stable across enough domains. A later application-layout mandate supplied enough evidence to accept AppShell; the other deferred candidates remain outside 2.0. The settled contracts, rather than this historical stage record, live in [`agent_native_spec.md`](agent_native_spec.md) and [`component_contracts.md`](component_contracts.md).
-
-Each abstraction must:
-
-- Have one clear responsibility.
-- Use closed layout options.
-- Own only structure that actually repeats.
-- Accept atoms/content through direct Ruby composition.
-- Emit classless self-describing markup.
-- Include examples showing reuse in at least two flows.
-
-Then rewrite the atom-only flows with blocks and compare the result. Delete abstractions that do not make application code meaningfully clearer.
-
-Gate: flow code describes product intent, while layouts and blocks remain a small coherent vocabulary rather than a second page framework.
-
-## Stage 8 — expanded application gallery
-
-Tickets: `nk-pmcn`, `nk-q1tc`, `nk-oi4y`, `nk-gn4s`, `nk-ky42`
-
-Extend the block-based gallery across:
-
-- Data detail, activity, audit, uploads, and integrations.
-- Billing, authentication, onboarding, team, and API states.
-- System error, permission, empty, loading-like, and marketing states.
-- Changelog, support, and help experiences.
-
-Prefer depth of state over disconnected decorative pages. Each flow should show success, empty/error, destructive/confirmation, and constrained-width behavior where applicable.
-
-Gate: the gallery demonstrates that the vocabulary can build a credible Rails product, not only isolated controls.
-
-## Stage 9 — remove the old system
-
-Ticket: `nk-u534`
-
-- Delete all `nk_*` view helpers and automatic variant aliases.
-- Delete copied-component generators, schemas, manifests, and installation paths.
-- Delete the Action View/template capture bridge and legacy builder path.
-- Remove Tailwind Merge and consumer Tailwind dependencies.
-- Remove legacy ERB test pages, Tailwind assets, and obsolete tests.
-- Audit packaged gem files and runtime dependencies.
-
-Gate: repository-wide searches find no public legacy invocation, copied-source promise, internal component class string, or required Tailwind runtime.
-
-## Stage 10 — browser behavior and lifecycle verification
-
-Tickets: `nk-352j`, `nk-6ivz`, `nk-gxwn`, `nk-lij5`, `nk-tkds`
-
-- Enumerate every catalog URL and state in a real browser.
-- Exercise keyboard order, arrows, Escape, Enter/Space, tab trapping/return, and focus visibility.
-- Exercise open/close, select, filter, validation, submit, and destructive confirmation paths.
-- Navigate through Turbo Drive, Frames, Streams, and morph refreshes; look for duplicate controllers and leaked listeners/positioners/timers.
-- Review representative pages at narrow/wide sizes and light/dark themes.
-- Check for horizontal overflow, clipped overlays, unstable layout, unreadable content, and broken focus state.
-
-Gate: browser coverage proves both route completeness and interaction lifecycle behavior.
-
-## Stage 11 — release-quality consolidation
-
-Tickets: `nk-g3qu`, `nk-obb7`
-
-- Reconcile actual component APIs with `docs/component_contracts.md` and `STYLE_GUIDE.md`.
-- Document Rails integration, theming tokens, composition, subclass caveats, and the escape hatch.
-- Run a data-structure review for duplicated collections, scattered state, and invalid intermediate states.
-- Run a simplification pass and remove compatibility branches, duplicate validation, dead CSS, dead JavaScript, and unused dependencies.
-- Audit all CSS selectors for zero specificity and owner scoping.
-- Audit all controllers for disconnect cleanup and Turbo safety.
-- Run the complete test, lint, format, CSS build/check, package, route, and browser suites.
-
-Gate: every child of `nk-rzxf` is closed with evidence and the repository contains one coherent 2.0 architecture.
-
-## Stage 12 — deterministic agent installation
-
-Ticket: `2an-5ayl`
-
-- Ship concise Nitro Kit Rails, Hotwire, and UI skills that resolve the
-  installed gem before acting.
-- Add a setup-only generator that installs the skills for Codex and Claude and
-  maintains a bounded `AGENTS.md` section without copying component source.
-- Add diagnostics for the resolved version, agent guidance, Hotwire wiring,
-  Phlex Kit inclusion, stylesheet loading, and Nitro Kit 1.x shadows.
-- Print or copy an initialization prompt without launching an agent.
-- Make guided and Pro eval profiles run the real installer and name Nitro Kit
-  2.x explicitly; retain cold profiles for diagnostic comparisons.
-
-Gate: installation is idempotent, preserves application-owned instructions,
-routes agents to version-matched doctrine, and is exercised by the eval
-harness.
-
-## Verification matrix
-
-| Surface       | Required verification                                                                             |
-| ------------- | ------------------------------------------------------------------------------------------------- |
-| Ruby API      | Focused construction/render tests; invalid vocabulary; missing content; reserved attributes       |
-| Markup        | Native semantics; stable IDs; ARIA relationships; `data-nk`; qualified `data-slot`; visible state |
-| CSS           | Deterministic build/check; zero-specificity owner-scoped selectors; token audit; light/dark       |
-| Rails         | Real `form_with`; Active Model; routes/DOM IDs; multipart; validation submit; Frame/Stream        |
-| JavaScript    | Keyboard behavior; open/close/select; disconnect cleanup; Turbo navigation and morph              |
-| Gallery       | Catalog routes; exact escaped source; copy behavior; no class/style/escape; narrow/wide           |
-| Packaging     | Engine boot with optional integrations absent; gem contents and dependencies audited              |
-| Documentation | Specification, contracts, style guide, Rails boundary, theming, examples, repository commands     |
-
-## Execution and handoff
-
-Use `tk ready` to select dependency-safe work. Preparatory parallel work is permitted only when the orchestrator explicitly assigns non-overlapping ownership. Every handoff names changed files, behavior decisions, focused test counts, and known failures. The orchestrator independently reviews and reproduces meaningful checks before closing a feature ticket.