Count a row written by hand in the design guard's stylesheet checks

`data-md-list-row` on an application's own `<li>`, `<div>`, `<tr>` or
`<x-row>` draws its hover, focus and press state layer, its cursor and
its `data-md-selected` fill from list-item.css, but missingStylesheets()
and unusedStylesheets() read only component tags and `->links()`.
ReStride had the stylesheet only because table.css imports it: had its
last `<x-table>` gone, every hand-made row would have lost its states
and its fill without a finding, and importing list-item.css for the
rows directly was reported unused.

A Blade view outside the package's own `resources/views` that writes a
hook in the new `HOOK_STYLESHEETS` now needs that hook's stylesheet in
both checks, named at the earliest line that needs it. The one entry is
`data-md-list-row` → `components/list-item.css`, except on `<x-card>`
(any spelling), whose row card.css draws; the card's opening tag is
blanked out before the hook is read, and a selector such as
`[data-md-list-row]` or a name in backticks writes no row. Nothing else
list-rows.js, the skill or the README has an application write needs a
stylesheet of its own: `data-md-list-open` and a row's
`data-md-selected` are drawn only through the row, a selected row in
`<x-table>` by table.css, `data-md-dragged` by foundation.css's
`md-state-layer` or card.css, `data-md-field-control` by field.css
inside `<x-field>`. The constant's docblock says so, and the guard's
docblocks, the README, the skill and UPGRADE.md describe the check.

A fixture test reads a hand-made `<li>` and `<tr>` row and a card-only
view (plain and namespaced `<x-card data-md-list-row>`, and a selector
in a script) against both checks; it fails without the change. A
second test scans the package's list-item and card views and expects
no row finding; it fails when package views are read.

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

UPGRADE.md

@@ -24,6 +24,15 @@
   family now too: `border-collapse`, `border-spacing-*`, `from-10%`, `via-none`, `fill-none`,
   `stroke-*`, `text-shadow-*`, `text-inherit`, and Tailwind 4.2's `mauve`, `olive`, `mist` and
   `taupe` palettes. A test that expects no findings may fail on them.
+- **`DesignGuard`** counts a row written by hand. `data-md-list-row` on an `<li>`, a `<div>`, a
+  `<tr>` or `<x-row>` takes its hover, focus and press state layer and its selected fill from
+  `components/list-item.css`, but `missingStylesheets()` and `unusedStylesheets()` read only tags
+  and `->links()`: an application had the stylesheet through `table.css` or `<x-list-item>`, lost
+  it without a finding when the last of those left its views, and an `@import` of `list-item.css`
+  for its own rows was reported unused. A view of the application that writes `data-md-list-row`
+  on anything but `<x-card>`, whose row card.css draws, now needs `list-item.css`; a selector such
+  as `[data-md-list-row]` and the package's own views do not count. A test that expects no findings
+  may name the `@import` to add, and a filter written around the unused report can go.
 - **A selected row written by hand** — `data-md-list-row` with `data-md-selected` on an `<li>`, a
   `<div>` or a `<tr>`, not `<x-list-item>` or `<x-card>` — is drawn in `secondary-container` with
   `on-secondary-container` ink again, as 1.x's `data-list-row` with `data-selected` was; 2.0.0