@godxjp/ui 19.4.0 → 19.4.1

package/dist/components/data-display/badge.d.ts

@@ -19,7 +19,7 @@ export interface BadgeProps extends Omit<React.HTMLAttributes<HTMLDivElement>, "
      * `<div>` would be invalid HTML: inside a `TabsTrigger`/`PopoverTrigger`/`Button` (all render a
      * `<button>`, whose content model is phrasing content only), inside a `<label>` or a `<p>`.
      * It swaps the TAG only — the chip's own `inline-flex` box, icon and label are unchanged, and
-     * both the icon `<svg>` and the label `<span>` are already phrasing content (gh#354).
+     * both the icon `<svg>` and the label `<span>` are already phrasing content.
      */
     as?: "div" | "span";
     /** Corner shape — `default` (badge radius) · `pill` (fully rounded) · `sharp` (square). */

package/dist/components/data-display/popover.d.ts

@@ -9,7 +9,7 @@ export declare function PopoverAnchor(props: React.ComponentProps<typeof Popover
  * edge and draw its own separators across the full width. The popover drops its own padding by
  * zeroing `--popover-space-inset` ON THE PANEL, so the inset stays one token (a service that
  * retunes `--popover-space-inset` still owns every padded popover) and no consumer has to reach
- * for a zero-padding utility, which no service theme can reach (gh#354).
+ * for a zero-padding utility, which no service theme can reach.
  */
 type PopoverContentFlush = {
     flush?: FlushProp;

package/dist/components/data-display/table.d.ts

@@ -65,7 +65,7 @@ export declare const TableHead: React.ForwardRefExoticComponent<React.ThHTMLAttr
 /**
  * The cell's CONTENT owns its inset — an expanded detail panel, a nested table, a full-bleed media
  * strip. The cell drops its own padding so the child reaches the cell edges; without it the only
- * route was a zero-padding utility at the call site, which no service theme can reach (gh#354).
+ * route was a zero-padding utility at the call site, which no service theme can reach.
  */
 type TableCellFlush = {
     flush?: FlushProp;

package/dist/components/layout/mobile-shell.d.ts

@@ -1,7 +1,7 @@
 import type { MobileShellProp } from "../../props/components/layout.prop.js";
 export type { MobileShellProp, MobileShellProp as MobileShellProps, } from "../../props/components/layout.prop.js";
 /**
- * MobileShell — the HANDHELD app shell (gh#354 §6): a status band, an app bar, ONE scroll region,
+ * MobileShell — the HANDHELD app shell: a status band, an app bar, ONE scroll region,
  * a sticky action bar and a bottom tab bar, in that fixed order.
  *
  * The fourth root shell. The other three cannot express a phone app: `AppShell` REQUIRES a sidebar

package/dist/props/components/data-display.prop.d.ts

@@ -140,7 +140,7 @@ export type BadgeProp = {
     /**
      * Render element — `div` (default) or `span` when the chip sits in a phrasing context where a
      * `<div>` is invalid HTML (inside a `<button>` rendered by TabsTrigger/PopoverTrigger/Button,
-     * a `<label>`, a `<p>`). Swaps the tag only (gh#354).
+     * a `<label>`, a `<p>`). Swaps the tag only.
      */
     as?: "div" | "span";
     variant?: "default" | "secondary" | "outline";

package/dist/props/components/layout.prop.d.ts

@@ -107,7 +107,7 @@ export type FlexProp = React.HTMLAttributes<HTMLDivElement> & {
      * `<div>` would be invalid HTML: inside a `TabsTrigger`/`PopoverTrigger`/`Button` (all of which
      * render a `<button>`, whose content model is phrasing content only), inside a `<label>`, or
      * inside a `<p>`. Same closed shape as `ListRow`'s `as` — it swaps the TAG, nothing else: the
-     * `.ui-flex` rules carry `display: flex`, so the box is identical either way (gh#354).
+     * `.ui-flex` rules carry `display: flex`, so the box is identical either way.
      */
     as?: "div" | "span";
     direction?: FlexDirectionProp;
@@ -282,7 +282,7 @@ export type AuthShellProp = {
  * `AppShell` REQUIRES a sidebar (its bar is a grid area beside the nav rail), `AuthShell` is the
  * UNAUTHENTICATED root and centres a ~24rem card, and `CenteredShell` is a scrolling DOCUMENT —
  * its `main` scrolls the page, which is exactly what a handheld app must not do. Composing one out
- * of `Card` + `ui-card-inset*` (what docs/showcase/case6 did before gh#354) reproduces the look
+ * of `Card` + `ui-card-inset*` (what docs/showcase/case6 once did) reproduces the look
  * and none of the two behaviours that matter on a real device:
  *
  *  1. The shell is the only scroll container. The root is exactly one screen tall, so the DOCUMENT

package/dist/props/vocabulary/layout.prop.d.ts

@@ -57,7 +57,7 @@ export type AuthShellPresetProp = "default" | "login" | "registration" | "device
  * `"none"` is a DELIBERATE zero, not the absence of a value: two lines that read as ONE block —
  * a name over its role, a weekday over its date, a tab bar with no seam between its triggers.
  * Without it those stacks had to carry `gap="xs"`, which is a visual change forced by a missing
- * step rather than by design (gh#354).
+ * step rather than by design.
  */
 export type GapProp = "none" | "xs" | "sm" | "md" | "lg" | "xl";
 /** DataTable row density subset. */

package/docs/FRAME-A11Y-CI.md

@@ -20,11 +20,56 @@ A control the **user cannot bring into the frame** — not merely one whose box
 
 - `check:contrast` (`scripts/check-contrast.mjs`) — a hand-picked set of ~6 pages checked for WCAG-AA text contrast. It never saw the other ~100 component frames. - `audit:examples` (`pnpm audit docs`) — a static source-regex linter. It can catch a hard-coded hex value but cannot see what actually renders: computed contrast, DOM landmark structure, focus order, or anything a Radix portal produces at runtime.
 
-## Chrome vs component: two independently-tracked scopes
+## Chrome vs component vs overlay: three independently-tracked scopes
 
-`check:frame-axe` runs axe **twice** per frame/viewport:
+`check:frame-axe` runs axe **twice** per frame/viewport, and a **third** time on the frames that declare an open step:
 
 - **Preview chrome** = the zoom / dimension **toolbar** (`.demo-block-toolbar`, `preview/src/demo-block.tsx`). We own this. It **must be 0** — a chrome violation fails the build.
+- **Component/demo** = everything else, in the frame's **default** state (the rendered frame _and_ its Radix portals). Allowlisted in `baseline.component`.
+- **Overlay** = the same scope re-measured **after opening an overlay** — see below. Allowlisted separately in `baseline.overlay`.
+
+### The overlay scope: opening the thing before measuring it (#355)
+
+The gate used to load each frame in its default state and scan once, so every axe rule whose _condition only exists while an overlay is open_ — `aria-hidden-focus` first among them — was **outside its field of view**, not merely un-triggered. 164 frames × 2 viewports reported clean while `aria-hidden-focus` fired on the app background the moment a `Select` or `DropdownMenu` opened in a consumer app.
+
+A frame opts in **declaratively**, from the demo itself:
+
+```tsx
+// the trigger itself, when it forwards DOM props
+<DropdownMenuTrigger asChild>
+  <Button data-axe-open …>…</Button>
+</DropdownMenuTrigger>
+
+// the region that owns the trigger, when the component renders it internally
+<CardContent data-axe-open>
+  <FormField id="status" label="状態"><Select … /></FormField>
+</CardContent>
+
+// right-click, for the one overlay that opens on no other gesture
+<ContextMenuTrigger data-axe-open="contextmenu" …>
+```
+
+What the gate does with it, per frame/viewport, **after** the two default-state scans (opening an overlay is destructive to the state those measure):
+
+1. Take the **first** `[data-axe-open]` on the page. No declaration ⇒ the frame skips this scope entirely and costs nothing.
+2. Press **Escape** up to three times while any overlay is mounted. Several demos deliberately render one open at rest, and a modal one makes the rest of the page inert — so the trigger is unreachable until it is dismissed. This also makes the measurement a real **closed → open transition** rather than whatever the demo happened to leave mounted.
+3. Resolve the click target: the declaring element itself when it matches `button, [role=button], [role=combobox], [role=menuitem], a[href], summary`, otherwise the first such control inside it. (`DatePicker`, the data-driven `Select` and `SearchSelect` own their trigger DOM and forward no `data-*` to it — hence the "declare on the region" form. `DatePicker`'s combobox `<input>` opens the calendar on click, which is what gets pressed there.)
+4. Click (or right-click), then wait until **one more** overlay is mounted (`[data-radix-popper-content-wrapper], [role=dialog], [role=alertdialog], [role=menu], [role=listbox]`) plus a 400 ms animation settle — never a bare timer.
+5. Re-run axe with the same scope as the component pass and record it under `baseline.overlay`.
+
+A declaration whose overlay never opens is an **infrastructure error** (blocking), not a silent skip: a broken declaration must not read as a clean frame.
+
+**Frames declaring an open step today** (the overlay families named in #355): `data-entry-select`, `data-entry-select-matrix` (SearchSelect), `data-entry-date-picker`, `data-display-popover`, `navigation-dropdown-menu`, `navigation-context-menu`, `feedback-dialog`, `feedback-sheet`.
+
+**Cost**: the overlay pass only runs on declaring frames, so it is ~8 frames × 2 viewports, measured at **+~55 s on a ~9.5 min local sweep (~10 %)**. Both viewports are kept for now; if the declaring set grows, narrow `OVERLAY_VIEWPORTS` in the script to `["desktop"]` — an overlay is portalled to `<body>` and its aria-hidden background is the same tree at either width.
+
+**What is still outside this scope** — deliberately, and worth knowing before trusting a green run:
+
+- Only the **first** declaration per frame is exercised. A frame with several distinct overlays (the Sheet demo has five) is measured on one of them.
+- Only **one step deep**: submenus (`DropdownMenuSub`), an overlay opened _from inside_ another overlay, and the state _after_ a selection are not reached.
+- **Keyboard-only opening** is not exercised — the gate clicks. A trigger that opens on click but not on `Enter`/`Space` would pass.
+- The overlay's own **focus trap and focus order** are still not asserted by axe here (`focus-order-semantics` needs the focus to actually move); `src/components/__tests__/overlay-hidden-background.a11y.test.tsx` remains the DOM-level guard for the aria-hidden/inert contract, and it is what fails first if the `inert` mirror in `src/components/general/inert-background.ts` regresses in jsdom.
+- Frames with **no declaration** (156 of 164) are unchanged: default state only.
 
 ## The component allowlist — and how it shrinks to zero
 
@@ -43,6 +88,10 @@ git add scripts/frame-axe.baseline.json && git commit -m "chore(a11y): tighten f
 
 There is **no blanket suppression**: a documented axe false positive would be an explicit per-rule entry with a comment, never a mute.
 
+`baseline.overlay` is the same shape and obeys the same rule, for the overlay-open scope. It is only rewritten for frames whose open step **actually ran** — a frame that stopped declaring one has not been proven clean, it has been left unmeasured.
+
+**Keys that are not violation data are preserved (#356).** The baseline also carries human notes — `scopeGap` records what the gate cannot see and which violations are deliberately unfixed. `--update-baseline` used to rebuild the file from scratch and delete them without a word. It now regenerates only the keys it owns (`generatedAt`, `note`, `component`, `overlay`), carries every other key over verbatim, and **names them in its log line** (`carried over: scopeGap`) so a disappearing key cannot go unnoticed.
+
 `0` chrome violations, `0` regressions. See [Remaining baseline debt](#remaining-baseline-debt--the-12-frames) below for exactly what's left and the path to zero.
 
 ## Running it locally
@@ -68,28 +117,47 @@ pnpm exec playwright install chromium        # local dev — downloads Playwrigh
 | `pnpm check:frame-axe --format json`                | Machine-readable result on stdout (same exit-code semantics) — no colored human report            |
 | `pnpm check:frame-axe --update-baseline`            | Regenerate the allowlist (2-pass union by default) — see below                                    |
 | `AXE_RUNS=3 pnpm check:frame-axe --update-baseline` | More union passes, for a component with flaky portal timing                                       |
+| `AXE_SHARD=2/4 pnpm check:frame-axe`                | Run only shard 2 of 4 (1-based) for CI fan-out — see below                                        |
 | `pnpm check:frame-axe http://localhost:6008`        | Point at an already-running preview instead of building+serving one                               |
 
+#### Sharding the sweep (`AXE_SHARD=i/n`)
+
+`AXE_SHARD=2/4` runs only the frames of shard 2 of 4. The partition is taken over frame ids sorted **by code point**, not in manifest/directory order, so the same tree always yields the same partition, every frame lands in exactly one shard, and the union of all `n` shards is exactly the full sweep. Unset (the default) leaves the frame list untouched — sharding changes nothing until you ask for it.
+
+Two things are deliberately _not_ the same under a shard, because a shard cannot know them:
+
+- **"Baseline rule no longer fires" (shrink hints) is skipped.** The baseline is keyed per frame, so _new_ rule detection stays exact on a partial run — but a frame this shard never visited looks identical to a frame that got fixed. Only a full sweep can tell those apart.
+- **`--update-baseline` refuses to run** with `AXE_SHARD` set (exit 2). Writing the baseline from a fraction of the frames would delete every frame the shard did not visit.
+
+`AXE_FRAMES_LIMIT` truncates the list instead of partitioning it; it is a local smoke-test knob, not a fan-out mechanism.
+
 If no preview server answers at the base URL (`http://localhost:6008` by default), the script builds one itself: `pnpm preview:build` then serves the static output with `vite preview` (`ensurePreviewServer` in `scripts/frame-harness.mjs`) — deterministic and stable under a long headless sweep, unlike the dev server's per-request recompilation. If a `pnpm preview` dev server (or a remote base) is already reachable, it's reused as-is and never rebuilt.
 
 ### Reading the output
 
-Terminal report (human mode) has two blocks:
+Terminal report (human mode) has three blocks:
 
 ```
 Preview-chrome axe (blocking — must be 0):
-  ✓ 0 chrome violations across all 107 frame(s).
+  ✓ 0 chrome violations across all 164 frame(s).
 
 Component/demo axe (allowlisted — baseline may only shrink):
-  47 component violation node(s) remaining across 12 frame(s).
+  0 component violation node(s) remaining across 0 frame(s).
   ✓ no new component violation types (rule-set within baseline).
+
+Overlay axe (frames declaring data-axe-open — baseline may only shrink):
+  8 frame(s) opened an overlay before scanning; 128 violation node(s) while open.
+  ✓ no new overlay violation types (rule-set within baseline).
 ```
 
 - A **red `✗ <rule>`** under chrome is always blocking.
 - A **red `✗ N NEW violation-type(s) not in baseline`** under component means a frame gained a
   rule the baseline didn't have — that's the actual CI failure mode for a component regression.
+- A **red `✗ N NEW violation-type(s) not in the overlay baseline`** is the same failure for the
+  overlay-open state — that is what turns red when, say, the `inert` background patch regresses
+  and `aria-hidden-focus` comes back.
 - A **yellow `↓ shrink hint`** means a baseline rule no longer fires anywhere it's listed — free
-  baseline tightening available via `--update-baseline`.
+  baseline tightening available via `--update-baseline`. Not emitted under `AXE_SHARD`.
 
 ### Evidence JSON
 
@@ -103,19 +171,27 @@ Shape:
   "base": "http://localhost:6008",
   "summary": {
     "status": "ok", // "ok" | "fail"
-    "frames": 107,
+    "frames": 164,
+    "shard": null, // "i/n" when AXE_SHARD is set
     "viewports": ["desktop", "mobile"],
     "chromeViolations": 0, // total chrome violation NODE count
-    "componentViolations": 47, // total component violation NODE count (reporting only)
+    "componentViolations": 0, // total component violation NODE count (reporting only)
     "componentRegressions": 0, // rules present now but not in the baseline
+    "overlayFrames": 8, // frames whose declared open step ran
+    "overlayViolations": 128, // total NODE count measured with an overlay open
+    "overlayRegressions": 0, // overlay rules present now but not in baseline.overlay
     "infrastructureErrors": 0, // frames that failed to load / axe crashed
   },
   "chrome": {/* rule → { impact, nodes, frames: ["<frameId>@<viewport>", …] } */},
   "componentCurrent": {/* frameId → viewport → ruleId → node count, this run */},
   "regressions": [/* { frame, rule } — new rules, the actual gate failure */],
   "shrinkHints": [/* { frame, rule } — baseline rules that no longer fire */],
-  "infraErrors": [/* { frame, viewport, message } */],
-  "results": [/* per-frame { id, viewports: { desktop: { chrome, component }, mobile: {…} } } */],
+  "overlayCurrent": {/* frameId → viewport → ruleId → node count, with the overlay OPEN */},
+  "overlayFrames": [/* frame ids whose declared open step ran */],
+  "overlayRegressions": [/* { frame, rule } — new rules in the overlay-open state */],
+  "overlayShrinkHints": [/* { frame, rule } */],
+  "infraErrors": [/* { frame, viewport, message } — includes "overlay open: …" failures */],
+  "results": [/* per-frame { id, viewports: { desktop: { chrome, component, overlay? }, … } } */],
 }
 ```
 
@@ -140,6 +216,8 @@ Playwright Inspector / browser devtools with the `axe-core` extension against th
    violation, not fixed an old one).
 4. Commit the baseline alongside the fix in the same PR.
 
+`--update-baseline` also preserves every non-violation key in the file verbatim (see #356 above) and refuses to run under `AXE_SHARD`.
+
 `AXE_FRAMES_LIMIT` + `--update-baseline` together only touch the frames actually run — the merge
 logic in `check-frame-axe.mjs` overwrites `runFrameIds` and leaves every other frame's baseline
 entry untouched, so a scoped re-snapshot (e.g. after fixing just `Select`) never silently drops
@@ -258,10 +336,14 @@ Before opening a PR that adds or meaningfully changes a `/frame/**` example:
 8. If you do land a frame with a tracked violation, add it to `scripts/frame-axe.baseline.json` via
    `--update-baseline` (never hand-edit the JSON) and note _why_ + the follow-up issue in the PR
    description — the baseline file's own `note` field explains it may only shrink from here.
-9. Register the case you authored in `preview/frame-coverage.ledger.json` so
-   `check:frame-coverage-ledger` stops reporting that dimension `UNTESTED`. You **cannot** hand-write
-   a verdict — add an entry to the ledger's `cases` array (frame path + case heading + resolvable
-   evidence paths + reviewer + HTTPS review link + ISO timestamp) and run
-   `pnpm gen:frame-coverage-ledger`; the gate recomputes every cell from that evidence and rejects
-   any verdict it cannot reproduce. See [FRAME-COVERAGE-LEDGER.md](./FRAME-COVERAGE-LEDGER.md) and
-   [FRAME-COVERAGE-STANDARD.md](./FRAME-COVERAGE-STANDARD.md).
+9. **If the frame demos an overlay, declare its open step**: `data-axe-open` on the trigger (or on
+   the region that owns it when the component renders the trigger itself), `data-axe-open="contextmenu"`
+   for a context menu. Without it the frame is only ever measured closed, and the whole
+   `aria-hidden-focus` family of rules cannot fire — see [the overlay scope](#the-overlay-scope-opening-the-thing-before-measuring-it-355).
+10. Register the case you authored in `preview/frame-coverage.ledger.json` so
+    `check:frame-coverage-ledger` stops reporting that dimension `UNTESTED`. You **cannot** hand-write
+    a verdict — add an entry to the ledger's `cases` array (frame path + case heading + resolvable
+    evidence paths + reviewer + HTTPS review link + ISO timestamp) and run
+    `pnpm gen:frame-coverage-ledger`; the gate recomputes every cell from that evidence and rejects
+    any verdict it cannot reproduce. See [FRAME-COVERAGE-LEDGER.md](./FRAME-COVERAGE-LEDGER.md) and
+    [FRAME-COVERAGE-STANDARD.md](./FRAME-COVERAGE-STANDARD.md).

package/docs/FRAME-COVERAGE-REPORT.md

@@ -3,8 +3,8 @@
 > Generated by `scripts/frame-coverage.mjs` (issue #163). Do not edit by hand — run `pnpm check:frame-coverage`.
 > Standard: [FRAME-COVERAGE-STANDARD.md](./FRAME-COVERAGE-STANDARD.md). A missing dimension is **UNTESTED**, never a pass.
 
-- Public components: **124**
-- With ≥1 frame: **124** · zero-frame: **0**
+- Public components: **126**
+- With ≥1 frame: **126** · zero-frame: **0**
 - Fully covered (every contract axis declared): **0**
 
 ## Per-component contract axes
@@ -19,6 +19,7 @@ Legend: ✓ covered · N/A reasoned skip · · UNTESTED (blank cell = UNTESTED).
 | AppShell | ✓ | N/A | N/A | N/A | · | · | · | · | · | · |
 | AuthShell | ✓ | ✓ | N/A | N/A | · | · | · | · | · | · |
 | CenteredShell | ✓ | N/A | N/A | N/A | · | · | · | · | · | · |
+| MobileShell | ✓ | N/A | N/A | N/A | · | · | · | · | · | · |
 | Sidebar | ✓ | N/A | N/A | N/A | · | · | · | · | · | · |
 | Topbar | ✓ | N/A | N/A | N/A | · | · | · | · | · | · |
 | MasterDetail | ✓ | N/A | N/A | N/A | · | · | · | · | · | · |
@@ -47,6 +48,7 @@ Legend: ✓ covered · N/A reasoned skip · · UNTESTED (blank cell = UNTESTED).
 | CodeBlock | ✓ | · | N/A | N/A | · | · | · | · | · | · |
 | Prose | ✓ | · | N/A | N/A | · | · | · | · | · | · |
 | Timeline | ✓ | ✓ | N/A | N/A | · | · | · | · | · | · |
+| TimelineGrid | ✓ | N/A | N/A | N/A | · | · | · | · | · | · |
 | Table | ✓ | N/A | N/A | N/A | · | · | · | · | · | · |
 | DataState | ✓ | N/A | · | N/A | · | · | · | · | · | · |
 | InfiniteQueryState | ✓ | N/A | · | N/A | · | · | · | · | · | · |

package/docs/data-display/popover.tsx

@@ -135,7 +135,10 @@ export default function Demo() {
             <Flex direction="row" wrap gap="sm">
               <Popover>
                 <PopoverTrigger asChild>
-                  <Button variant="outline">side=top</Button>
+                  {/* data-axe-open: opened by check-frame-axe before its overlay scan. */}
+                  <Button data-axe-open variant="outline">
+                    side=top
+                  </Button>
                 </PopoverTrigger>
                 <PopoverContent side="top" aria-label="上側の配置例">
                   <PopoverDescription>上に開きます。</PopoverDescription>

package/docs/data-entry/date-picker.tsx

@@ -33,7 +33,8 @@ export default function Demo() {
               形式に整形され、 解釈できない入力は元の値へ復帰する。
             </CardDescription>
           </CardHeader>
-          <CardContent>
+          {/* data-axe-open: check-frame-axe opens the calendar before scanning. */}
+          <CardContent data-axe-open>
             <FormField id="issue-date" label="発行日" required>
               <DatePicker
                 id="issue-date"

package/docs/data-entry/form-field/index.tsx

@@ -130,7 +130,7 @@ export default function Demo() {
 
         <Card>
           <CardHeader>
-            <CardTitle level={2}>Field identity · data-field (gh#337)</CardTitle>
+            <CardTitle level={2}>Field identity · data-field</CardTitle>
             <CardDescription>
               項目キーを control の data-field に出す。既定は id から導出。id が DOM
               一意化のためのもので項目キーと違う場合だけ field を明示する。AppProvider
@@ -176,7 +176,7 @@ export default function Demo() {
 
         <Card>
           <CardHeader>
-            <CardTitle level={2}>Static value · mixed with editable fields (gh#294)</CardTitle>
+            <CardTitle level={2}>Static value · mixed with editable fields</CardTitle>
             <CardDescription>
               staticText renders a read-only VALUE as a FormField itself: Descriptions.Item's exact
               value typography, no control, no id/aria-* wiring. An immutable name/email row and an

package/docs/data-entry/select-matrix.tsx

@@ -142,7 +142,8 @@ export default function Demo() {
               references. The internal search textbox has its own visible-purpose accessible name.
             </CardDescription>
           </CardHeader>
-          <CardContent>
+          {/* data-axe-open: check-frame-axe opens the searchable panel before scanning. */}
+          <CardContent data-axe-open>
             <FormField
               id="searchable-invalid"
               label="担当拠点"

package/docs/data-entry/select.tsx

@@ -82,7 +82,9 @@ export default function Demo() {
               Pass an options array; name= submits the value with the form.
             </CardDescription>
           </CardHeader>
-          <CardContent>
+          {/* data-axe-open: check-frame-axe opens this Select before scanning, so the
+              overlay-open a11y state is measured. See docs/FRAME-A11Y-CI.md. */}
+          <CardContent data-axe-open>
             <FormField id="status" label="状態">
               <Select
                 id="status"

package/docs/feedback/dialog.tsx

@@ -109,7 +109,8 @@ export default function Demo() {
           <CardContent>
             <Dialog open={detailOpen} onOpenChange={setDetailOpen}>
               <DialogTrigger asChild>
-                <Button variant="outline" size="sm">
+                {/* data-axe-open: opened by check-frame-axe before its overlay scan. */}
+                <Button data-axe-open variant="outline" size="sm">
                   取引詳細を見る
                 </Button>
               </DialogTrigger>

package/docs/feedback/sheet.tsx

@@ -213,7 +213,8 @@ export default function Demo() {
           <CardContent>
             <Sheet open={editOpen} onOpenChange={setEditOpen}>
               <SheetTrigger asChild>
-                <Button variant="ghost" size="sm">
+                {/* data-axe-open: opened by check-frame-axe before its overlay scan. */}
+                <Button data-axe-open variant="ghost" size="sm">
                   取引先を編集
                 </Button>
               </SheetTrigger>

package/docs/layout/app-shell.tsx

@@ -282,8 +282,8 @@ export default function Demo() {
                 を切り替え、sidebar・topbar・page actions・grid・split pane
                 の変換を同じ実用構成で確認する。900px 以下ではドックされたサイドバーが隠れ、
                 AppShell 所有のモバイルドロワー（トップバー左のハンバーガー → フォーカストラップ付き
-                Sheet · Esc で閉じてトリガーへフォーカス復帰）が navigation を提供する（gh#165）。
-                このデモは mobileNav を渡していないため、同じ Sidebar がドロワーに再利用される。
+                Sheet · Esc で閉じてトリガーへフォーカス復帰）が navigation を提供する。 このデモは
+                mobileNav を渡していないため、同じ Sidebar がドロワーに再利用される。
               </CardDescription>
               <CardDescription>
                 「トップバーなし（チャット型）」を押すと topbar / topbarLeft / topbarRight / logo の
@@ -297,8 +297,8 @@ export default function Demo() {
                 で代用しないこと ― それは 4 スロットが埋まった状態と同じで、バーの行は残る。
               </CardDescription>
               <CardDescription>
-                横方向のページ余白軸の持ち主は <code>--space-page-x</code> ひとつ（gh#330）。
-                トップバーは <code>.app-main</code> と同じグリッド列に載っている ―
+                横方向のページ余白軸の持ち主は <code>--space-page-x</code> ひとつ。 トップバーは{" "}
+                <code>.app-main</code> と同じグリッド列に載っている ―
                 つまりバー先頭のコントロールとページタイトルは同じ縦線に並ぶべきもので、
                 <code>--app-shell-bar-inset</code> はその持ち主を読む （
                 <code>--app-shell-bar-inset-compact</code> も同様に

package/docs/layout/responsive-grid.tsx

@@ -35,8 +35,8 @@ export default function Demo() {
               列、右の狭いサイドバー（約 20rem）は 1 列に折り返す。ビューポート幅は同一なので、
               折り返しの基準がコンテナ幅であることが分かる。ResponsiveGrid は自身のクエリコンテナ
               （container-type: inline-size）を持つため、外側に @container を用意しなくても正しく
-              折り返す（gh#165）。閾値はコンテナ幅 40 / 48 / 64rem。 列間の gap は
-              var(--space-stack-md) に固定で、prop では変更できない。
+              折り返す。閾値はコンテナ幅 40 / 48 / 64rem。 列間の gap は var(--space-stack-md)
+              に固定で、prop では変更できない。
             </CardDescription>
           </CardHeader>
           <CardContent>
@@ -72,7 +72,7 @@ export default function Demo() {
             <CardDescription>
               固定幅の親の中でも、同じ columns=&#123;4&#125; が親幅で列数を変える。親には
               container-type を付けていない。ResponsiveGrid が自身のスコープでクエリするため、
-              外側にコンテナ宣言がなくても 1 列に潰れない（gh#165）。
+              外側にコンテナ宣言がなくても 1 列に潰れない。
             </CardDescription>
           </CardHeader>
           <CardContent>

package/docs/layout/sidebar.tsx

@@ -402,7 +402,7 @@ export default function Demo() {
               <CardDescription>
                 行の中身まで利用側が書く旧エスケープハッチ。これが原因で
                 <code>&lt;Link&gt;{"{item.label}"}&lt;/Link&gt;</code>
-                がアイコンを全て落とす回帰が発生しました（gh#213）。 現在は rowProps.children
+                がアイコンを全て落とす回帰が発生しました。 現在は rowProps.children
                 にライブラリ製の行内容が入るので、それを描画すれば 正規の行が復元されます（ここでは
                 その右にお気に入りスターを添えています）。 新規コードでは linkComponent か
                 SidebarItem asChild を使ってください。
@@ -436,7 +436,7 @@ export default function Demo() {
                 sections を使わず SidebarSection / SidebarItem を直接組み立てて、
                 ナビゲーション全体を 自前で構成します。右は同じ構成に SidebarItem の asChild
                 を足したものです。子として ルーターの Link
-                を「要素だけ」渡すと、アイコン・ラベル・バッジは ライブラリが差し込みます（gh#213。
+                を「要素だけ」渡すと、アイコン・ラベル・バッジは ライブラリが差し込みます（。
                 children は書きません）。
               </CardDescription>
             </CardHeader>
@@ -590,7 +590,7 @@ export default function Demo() {
                   "badgeTone で未読（neutral）と自分宛て（destructive）を色だけで区別",
                   "disabled=true で項目を非活性化（クリック不可）",
                   "footer prop でスクロール外にユーザー情報を固定",
-                  "linkComponent · ルーター Link は「要素だけ」渡す。行の中身はライブラリが組み立てる（gh#213）",
+                  "linkComponent · ルーター Link は「要素だけ」渡す。行の中身はライブラリが組み立てる",
                   "linkComponent は葉・サブメニュー・折りたたみレール・フライアウトの全てに適用される",
                   "グループのトリガーは aria-expanded を持つ開閉ボタンのままなので linkComponent は適用されない",
                 ].map((note) => (

package/docs/layout/split-pane.tsx

@@ -302,8 +302,8 @@ export default function Demo() {
                   </Text>
                   <Text as="p" tone="muted">
                     パネル自身の幅が 48rem 未満になると縦積みにフォールバックします
-                    （ビューポートではなくコンテナ基準 · gh#165）。
-                    常にサイドバイサイドが必要な場合は CSS Grid を使用してください。
+                    （ビューポートではなくコンテナ基準）。 常にサイドバイサイドが必要な場合は CSS
+                    Grid を使用してください。
                   </Text>
                 </Flex>
               </CardContent>
@@ -410,9 +410,8 @@ export default function Demo() {
           <CardHeader>
             <CardTitle level={2}>Container stress · narrow vs wide embed</CardTitle>
             <CardDescription>
-              大きな viewport 内でも、パネル自身の幅で分割が決まる（gh#165）。狭い埋め込み（約
-              28rem）は 1 カラムに潰れ、広い埋め込み（約 56rem）は 2 カラムに分割する。ビューポート
-              幅は同一。
+              大きな viewport 内でも、パネル自身の幅で分割が決まる。狭い埋め込み（約 28rem）は 1
+              カラムに潰れ、広い埋め込み（約 56rem）は 2 カラムに分割する。ビューポート 幅は同一。
             </CardDescription>
           </CardHeader>
           <CardContent>

package/docs/navigation/context-menu.tsx

@@ -48,7 +48,12 @@ export default function Demo() {
           <CardContent>
             <ContextMenu>
               {/* ui-audit-disable-next-line no-hand-rolled-surface — the dashed area is the right-click target the demo asks you to use */}
-              <ContextMenuTrigger className="border-border h-36 w-full cursor-context-menu rounded-md border border-dashed">
+              {/* data-axe-open="contextmenu": check-frame-axe right-clicks here before its
+                  overlay scan. */}
+              <ContextMenuTrigger
+                data-axe-open="contextmenu"
+                className="border-border h-36 w-full cursor-context-menu rounded-md border border-dashed"
+              >
                 <Flex align="center" justify="center" gap="xs">
                   <Text tone="muted">ここを右クリックしてください</Text>
                 </Flex>

package/docs/navigation/dropdown-menu.tsx

@@ -52,7 +52,8 @@ export default function Demo() {
               <Text>JE-0042 · 売上計上 ¥480,000</Text>
               <DropdownMenu>
                 <DropdownMenuTrigger asChild>
-                  <Button variant="ghost" size="icon-sm" aria-label="行アクション">
+                  {/* data-axe-open: opened by check-frame-axe before its overlay scan. */}
+                  <Button data-axe-open variant="ghost" size="icon-sm" aria-label="行アクション">
                     <MoreHorizontal />
                   </Button>
                 </DropdownMenuTrigger>

package/docs/navigation/tabs.tsx

@@ -73,7 +73,7 @@ export default function Demo() {
             <CardTitle level={2}>先頭タブが disabled · フォールバック選択</CardTitle>
             <CardDescription>
               defaultValue/value を渡さない場合、Tabs は先頭の ENABLED タブを自動選択する(disabled
-              の先頭タブは選ばない)。全タブが disabled の場合は何も選択しない (gh#175)。
+              の先頭タブは選ばない)。全タブが disabled の場合は何も選択しない。
             </CardDescription>
           </CardHeader>
           <CardContent>
@@ -106,7 +106,7 @@ export default function Demo() {
             <CardTitle level={2}>320px stress · 長いローカライズラベル</CardTitle>
             <CardDescription>
               狭いコンテナでも長いラベルはクリップされず、水平タブリストが自身でスクロールする
-              (gh#175)。compact navigation への変換は Tabs API に存在しないため擬似実装しない —
+              。compact navigation への変換は Tabs API に存在しないため擬似実装しない —
               スクロールが意図した縮退動作。
             </CardDescription>
           </CardHeader>

package/docs/showcase/case6-agency-handy.tsx

@@ -333,7 +333,7 @@ function SectionHeader({ children, count }: { children: React.ReactNode; count?:
 // ── Phone shell ──────────────────────────────────────────────────────────────
 
 /**
- * gh#354 §6 — this file used to BUILD the shell: a `Card` + `CardContent flush` phone frame, a
+ * This file used to BUILD the shell: a `Card` + `CardContent flush` phone frame, a
  * `ui-card-inset-x h-9` status row, an `h-14 border-b` header, a `flex-1 overflow-y-auto` body, a
  * `shrink-0 border-t` action strip and a `ResponsiveGrid` tab bar. It reproduced the look and
  * neither behaviour that matters on a device — the document still scrolled, and nothing padded out
@@ -962,7 +962,7 @@ export default function AgencyHandyShowcase() {
 
   // SELECT MODE REPLACES THE APP BAR — it does not stack a second strip under it. That is the
   // platform pattern on both iOS and Android, and it is what the `header` slot is for: one bar to
-  // read at a time. Before gh#354 this file rendered the title bar AND a contextual strip, because
+  // read at a time. This file once rendered the title bar AND a contextual strip, because
   // there was no bar to swap.
   const header = selectMode ? (
     <Flex align="center" justify="between" gap="xs" className="w-full">

package/docs/showcase/org-switcher.tsx

@@ -120,7 +120,7 @@ function OrgSwitcher({ organizations, currentId, onSelect, onCreate, onJoin }: O
           className="w-full justify-between"
         >
           {/* Inside a Button, i.e. inside a <button>, whose content model is phrasing content
-              only — so every Flex on this branch renders as a <span> (gh#354). */}
+              only — so every Flex on this branch renders as a <span>. */}
           <Flex as="span" align="center" gap="sm" className="min-w-0">
             <Avatar className="size-7 rounded-md">
               <AvatarFallback>{monogram(current.name)}</AvatarFallback>

package/docs/showcase/settings-account-sections.tsx

@@ -61,7 +61,7 @@ import { AlertDialog } from "@godxjp/ui/feedback";
 import { Flex, PageContainer } from "@godxjp/ui/layout";
 
 // ── Label bundles: the SAME screen at its longest JA / EN / VI wording ────────────────────────
-// Long-label stress is a first-class acceptance criterion (#216), so the bundle intentionally
+// Long-label stress is a first-class acceptance criterion, so the bundle intentionally
 // carries the verbose form of each label instead of the tidy demo form.
 
 type LabelBundle = {
@@ -348,7 +348,7 @@ export default function SettingsAccountSectionsShowcase() {
       title={b.pageTitle}
       subtitle={b.pageSubtitle}
       breadcrumb={[{ label: b.pageTitle }]}
-      // PageHeader action composition (#216): the header owns the page-level actions through
+      // PageHeader action composition: the header owns the page-level actions through
       // `extra`. It wraps at 390 instead of overflowing, so no page-local header geometry.
       extra={
         <Flex direction="row" align="end" gap="sm" wrap>

package/docs/showcase/table-master-detail.tsx

@@ -417,7 +417,7 @@ export default function Demo() {
         </Card>
 
         {/* ── Empty detail state (nothing selected) ──
-            Fixed-track split, so the geometry belongs to MasterDetail, not this page (gh#223):
+            Fixed-track split, so the geometry belongs to MasterDetail, not this page:
             rail="master" keeps the leading 一覧 on the fixed track while the detail surface stays
             fluid, and collapseBelow="md" stacks 一覧→詳細 once the card body itself is too narrow
             for two tracks. No grid tracks, no per-breakpoint widths, no page-local spacing. */}

package/docs/showcase/table-view-tabs.tsx

@@ -369,7 +369,7 @@ const DOT_CLASS: Record<SavedView["dot"], string> = {
 
 // TabsTrigger renders a <button>, whose content model is phrasing content only — so the row and
 // the count chip take `as="span"`. Before Flex/Badge had that seam the only valid shape here was a
-// raw `<span className="flex …">`, i.e. utility layout (gh#354).
+// raw `<span className="flex …">`, i.e. utility layout.
 function ViewTrigger({ view, count }: { view: SavedView; count: number }) {
   return (
     <Flex as="span" align="center" gap="sm">

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@godxjp/ui",
-  "version": "19.4.0",
-  "godxUiMcp": "19.4.0",
+  "version": "19.4.1",
+  "godxUiMcp": "19.4.1",
   "license": "Apache-2.0",
   "repository": {
     "type": "git",