@godxjp/ui 25.2.0 → 25.3.0

package/dist/components/data-entry/calendar.js

@@ -22,7 +22,7 @@ function Calendar({
   onClose,
   footer,
   width = "auto",
-  bordered = false,
+  bordered = true,
   cellRender,
   month: monthProp,
   onMonthChange,

package/dist/components/data-entry/date-picker.js

@@ -49,6 +49,7 @@ function DatePicker(props) {
     toDate,
     disabledDate,
     cellRender,
+    bordered,
     allowClear,
     triggerLabel,
     format: formatProp,
@@ -381,6 +382,7 @@ function DatePicker(props) {
     onMonthChange: setViewAnchor,
     locale: dayPickerLocale,
     cellRender,
+    bordered,
     showWeekNumber: showWeek,
     startMonth: minimum,
     endMonth: maximum,

package/dist/contracts/measurement.json

@@ -1,6 +1,6 @@
 {
   "$comment": "AUTO-GENERATED by scripts/gen-measurement-contract.mjs — do not edit. Read this instead of guessing: docs/MEASUREMENT-CONTRACT.md.",
-  "version": "25.2.0",
+  "version": "25.3.0",
   "targetSize": {
     "standard": "WCAG 2.2 SC 2.5.8 Target Size (Minimum), level AA — 24×24 CSS px",
     "min": 24,

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

@@ -725,8 +725,10 @@ export type CalendarProp = DayPickerProps & CalendarFooterProp & {
      * What a month grid needs is the ruling BETWEEN days, so a week reads as a row of cells the
      * eye can track across.
      *
-     * Default `false`, because a picker popover wants the opposite: floating day buttons with no
-     * ruling, so the selected day is the only shape in the panel.
+     * Default `true` — the owner's call, from a real screen: with no ruling the month read as a
+     * cloud of numbers and was "very hard to read". Pass `bordered={false}` for the floating-button
+     * look. The line colour is `--calendar-grid-border-color` (default `--input`, the ≥3:1 tier;
+     * the decorative `--border` measured 1.15:1 and was invisible as a 1px ruling).
      */
     bordered?: boolean;
     /** Decorate a day cell — 祝日, a booked day, a deadline. @see CalendarCellRenderProp */
@@ -861,6 +863,12 @@ export type DatePickerBaseProp = FieldA11yProps & PickerChromeProp & {
     toDate?: Date;
     /** Decorate a day cell — 祝日, a booked day, a deadline. @see CalendarCellRenderProp */
     cellRender?: CalendarCellRenderProp;
+    /**
+     * Rule the day grid in the panel — forwarded to `Calendar bordered`, and defaults to `true`
+     * like it. Applies to the DAY grid (`picker="date"` / `"week"`, single, `multiple` and `range`);
+     * the month / quarter / year period grid has no day cells to rule and ignores it.
+     */
+    bordered?: boolean;
     /**
      * Forbid individual dates by predicate — the rule `minDate`/`maxDate` cannot express, because a
      * business calendar is rarely one contiguous range: 土日, a closed accounting period, a 祝日, a

package/dist/styles/control.css

@@ -2180,13 +2180,13 @@
 
   .ui-calendar[data-bordered="true"] .ui-calendar-day,
   .ui-calendar[data-bordered="true"] .ui-calendar-weekday {
-    border-inline-start: 1px solid hsl(var(--border));
-    border-block-start: 1px solid hsl(var(--border));
+    border-inline-start: 1px solid var(--calendar-grid-border-color, hsl(var(--input)));
+    border-block-start: 1px solid var(--calendar-grid-border-color, hsl(var(--input)));
   }
 
   .ui-calendar[data-bordered="true"] .ui-calendar-week,
   .ui-calendar[data-bordered="true"] .ui-calendar-weekdays {
-    border-inline-end: 1px solid hsl(var(--border));
+    border-inline-end: 1px solid var(--calendar-grid-border-color, hsl(var(--input)));
   }
 
   .ui-calendar[data-bordered="true"] .ui-calendar-weekday {
@@ -2198,7 +2198,7 @@
   }
 
   .ui-calendar[data-bordered="true"] .ui-calendar-grid {
-    border-block-end: 1px solid hsl(var(--border));
+    border-block-end: 1px solid var(--calendar-grid-border-color, hsl(var(--input)));
   }
 
   .ui-calendar[data-bordered="true"] .ui-calendar-day.invisible {
@@ -2219,8 +2219,12 @@
 
   .ui-calendar[data-bordered="true"] .ui-calendar-week-number,
   .ui-calendar[data-bordered="true"] .ui-calendar-week-number-header {
-    border-inline-start: 1px solid hsl(var(--border));
-    border-block-start: 1px solid hsl(var(--border));
+    border-inline-start: 1px solid var(--calendar-grid-border-color, hsl(var(--input)));
+    border-block-start: 1px solid var(--calendar-grid-border-color, hsl(var(--input)));
+  }
+
+  .ui-calendar[data-bordered="true"] .ui-calendar-day {
+    inline-size: var(--control-height);
   }
 
   .ui-calendar[data-bordered="true"] .ui-calendar-day-button {

package/dist/tokens/components/control.css

@@ -290,6 +290,8 @@
 
   --calendar-bordered-weekday-padding-block: var(--space-1);
 
+  --calendar-grid-border-color: initial;
+
   --transfer-pane-min-height: 14rem;
   --transfer-pane-radius: var(--radius-md);
   --transfer-panes-space-gap: var(--space-3);

package/docs/DEVELOPMENT.md

@@ -122,7 +122,7 @@ pnpm test                 # FULL suite — CI only, never from an agent loop
 pnpm preview:build        # integration test: examples + docs must build — at most once, pre-PR
 pnpm audit                # godxjp-ui-audit — 0 errors for touched files
 pnpm check:mcp-sync       # MCP registry ↔ library export drift guard
-pnpm check:frame-axe      # WCAG 2.2 AA over every frame — see FRAME-A11Y-CI.md
+pnpm check:frame-axe      # WCAG 2.2 AA over every frame — LOCAL ONLY, never in CI (FRAME-A11Y-CI.md)
 ```
 
 `pnpm verify` and `pnpm verify:release` run these together (verify:release also builds) — **both include the full suite, so both belong to CI.** Locally, run them at most once immediately before opening a PR, never inside an edit loop and never while other agents are working on the same machine. It needs `pnpm exec playwright install chromium` once locally; see [FRAME-A11Y-CI.md](./FRAME-A11Y-CI.md) for how to run/scope it, read the evidence, and regenerate its baseline after an accessibility fix.
@@ -190,5 +190,5 @@ npm versions are immutable, so you can never "fix" a bad published version in pl
 - [README](../README.md) — overview, component groups, consumer setup.
 - [CONSUMER-RULES.md](./CONSUMER-RULES.md) — the ten rules every consumer follows (the audit enforces them).
 - `docs/TOKENS.md`, `docs/SPACING.md`, `docs/PROPS-VOCABULARY.md`, `docs/PROPS-REGISTRY.md`.
-- [FRAME-A11Y-CI.md](./FRAME-A11Y-CI.md) — per-frame axe a11y + geometry + coverage CI gates.
+- [FRAME-A11Y-CI.md](./FRAME-A11Y-CI.md) — per-frame axe a11y (**local only, never in CI**) + geometry + coverage gates.
 - **`godx-ui-component-placement`** skill — decide whether a component belongs here.

package/docs/FRAME-A11Y-CI.md

@@ -1,6 +1,13 @@
-# Per-frame accessibility CI — `check:frame-axe`
+# Per-frame accessibility — `check:frame-axe` (LOCAL ONLY)
 
-One ruler, run in the repository that owns the CSS.
+One ruler, run in the repository that owns the CSS — **on a developer machine, never in CI/CD.**
+
+> **Owner's standing rule (2026-09-17): axe must not run in any GitHub Actions workflow.** It is a
+> local measurement only. gh#643 had wired it into `ci-browser.yml` (four shards on every merge) and
+> `ci-browser-full.yml` (nightly); both jobs are removed. `check:gate-coverage` lists
+> `check:frame-axe` as EXEMPT with this reason, so its absence from the workflows is a declaration,
+> not a dead gate. **Do not re-wire it into a workflow.** The file keeps its historical name so
+> existing links still resolve.
 
 ## Why it exists (gh#643)
 
@@ -234,41 +241,45 @@ which changes what `color-contrast` resolves a background to). Two sweeps after
 
 ## Cost
 
-|                                       |                                                                                                                |
-| ------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
-| full sweep                            | **3m20s** locally · **12m01s** on the self-hosted runner — 215 routes × 3 viewports                            |
-| sequential                            | ~55 min — the three viewport passes run concurrently, which is the whole difference                            |
-| showcase only (`--scope=showcase`)    | 30s                                                                                                            |
-| full sweep **with the overlay scope** | **2m14s** on the machine gh#643 item 4 was built on, same 215 × 3 — the runner number has not been re-measured |
+|                                       |                                                                                     |
+| ------------------------------------- | ----------------------------------------------------------------------------------- |
+| full sweep                            | **2m14s** locally, with the overlay scope — 215 routes × 3 viewports                |
+| sequential                            | ~55 min — the three viewport passes run concurrently, which is the whole difference |
+| showcase only (`--scope=showcase`)    | ~30s                                                                                |
+| one route (`pnpm check:frame-axe /isolate/…`) | seconds — the loop to use while fixing                                      |
 
 The overlay pass is bounded by declaration: only the 7 declaring routes pay it (21 extra scans plus
-their open steps), and no `/showcase/**` route declares one, so `--scope=showcase` — the merge lane —
-is unchanged.
+their open steps), and no `/showcase/**` route declares one, so `--scope=showcase` is unchanged by it.
+
+## Where it runs: your machine
 
-`--shard=i/n` is in the script for the day the sweep outgrows the lane. Using it adds check-run
-names, which costs nothing here because none of them is in `REQUIRED_CI_CHECK_RUNS`.
+**Never in CI/CD** — see the rule at the top. The procedure:
 
-## Where it runs
+```bash
+pnpm build && pnpm preview:build        # the STATIC preview — not `pnpm dev` / `pnpm preview`
+pnpm check:frame-axe                    # full sweep; must end with 0 baselined entries, 0 nodes
+pnpm check:frame-axe /isolate/<frame>   # one route, while fixing
+```
 
-Two lanes, split on a **measurement taken on the runner, not on a laptop**:
+Run it before a PR that touches markup, ARIA, focus behaviour or colour, and commit what it writes —
+`audit-evidence/frame-axe/results.json` and, only when a full sweep genuinely changed it,
+`frame-axe-baseline.json`.
 
-| lane                                                              | what                                      | when                                                           | measured                               |
-| ----------------------------------------------------------------- | ----------------------------------------- | -------------------------------------------------------------- | -------------------------------------- |
-| `ci-browser.yml` · `Per-frame axe (showcases, WCAG 2.2 AA)`       | `--scope=showcase` — 30 whole-page frames | every push to `main`                                           | 30s locally                            |
-| `ci-browser-full.yml` · `Per-frame axe (all frames, WCAG 2.2 AA)` | the full 215-route sweep                  | nightly, `workflow_dispatch`, or a `run-browser` label on a PR | **12m01s on the pool** (3m20s locally) |
+**The static preview, not the dev server.** Against the vite dev server the sweep produces 1–3
+spurious `route-did-not-render` / `axe-did-not-run` rows on different routes each run — 30s
+`page.goto` timeouts while three viewport contexts hammer an on-demand-transforming server. Each is
+clean alone. The static build does not do this.
 
-The full sweep went into the merge lane first, on the local 3m20s. On the pool's runner the same
-job took **12m01s** — three times the local wall clock and more than twice CONTRACT.md L4's
-five-minute budget for that whole lane. So the merge lane keeps the showcases, which are the only
-frames here shaped like the screens a consumer ships, and the wide matrix moved to the lane this
-repository already reserves for wide matrices.
+**`--shard=i/n` and `--scope=` are for splitting a LOCAL run**, e.g. across two terminals. Two guards
+hold for both: `--update` refuses under either (a partial run would rewrite the ledger from a fraction
+of the frames and delete the rest), and the "no longer fires" report is suppressed on a partial run
+(every other partition's rows would read as fixed). Regenerate the baseline from a full sweep only.
 
-**Not** the PR lane: that file's own header lists axe among what it deliberately excludes, at a
-measured 653–745s, and that decision is not reopened here.
+### What leaving CI costs, stated rather than discovered
 
-The job is not in `REQUIRED_CI_CHECK_RUNS` (#492 removed it from the release proof map and this does
-not put it back). It still protects a release through `assertCiProvenance`'s collateral rule — **any**
-red check run on the SHA being published refuses the publish.
+A regression is now caught when someone runs this, not on merge. Nothing in the pipeline will turn
+red on a new `aria-*` defect, a nameless button or a sub-24px target. That is the trade the rule
+makes, and the only thing that closes it is the local run above actually happening before a PR.
 
 ## Related
 

package/docs/README.md

@@ -12,7 +12,7 @@
 | [SPACING.md](./SPACING.md)                   | Golden ratio (φ) macro spacing — PageContainer sections, Flex gap, Card rhythm                                                                                                                                        |
 | [FORMS.md](./FORMS.md)                       | **Mandatory** react-hook-form + Zod 4                                                                                                                                                                                 |
 | [TESTING.md](./TESTING.md)                   | **Mandatory** Vitest per component                                                                                                                                                                                    |
-| [FRAME-A11Y-CI.md](./FRAME-A11Y-CI.md)       | Per-frame axe a11y + geometry + coverage CI gates — how to run/regenerate locally                                                                                                                                     |
+| [FRAME-A11Y-CI.md](./FRAME-A11Y-CI.md)       | Per-frame axe a11y (LOCAL ONLY, never CI) + geometry + coverage gates — how to run/regenerate                                                                                                                         |
 | [../README.md](../README.md)                 | Setup, workspace wiring, theme                                                                                                                                                                                        |
 
 ## Preview

package/docs/data-entry/calendar.tsx

@@ -29,6 +29,10 @@ export default function Demo() {
     from: new Date(2026, 3, 1),
     to: new Date(2026, 3, 30),
   });
+  const [ruledRange, setRuledRange] = useState<DateRange | undefined>({
+    from: new Date(2026, 3, 13),
+    to: new Date(2026, 3, 22),
+  });
   const [shiftDays, setShiftDays] = useState<Date[] | undefined>([
     new Date(2026, 3, 6),
     new Date(2026, 3, 13),
@@ -67,6 +71,48 @@ export default function Demo() {
           </CardContent>
         </Card>
 
+        <Card>
+          <CardHeader>
+            <CardTitle level={2}>
+              罫線 (bordered) · 既定で表示 / bordered={"{false}"} で解除
+            </CardTitle>
+            <CardDescription>
+              日と日の間に罫線を引くのが既定。線色は --calendar-grid-border-color (既定
+              --input、背景に対し 3:1
+              以上)。選択日・今日・範囲の始点/中間/終点・無効日・前後月の日が
+              罫線の中でも判別できる。罫線なしの浮いたボタン表示にしたい場合のみ bordered=
+              {"{false}"} を渡す。
+            </CardDescription>
+          </CardHeader>
+          <CardContent>
+            <Flex gap="lg" wrap>
+              <Calendar
+                mode="range"
+                selected={ruledRange}
+                onSelect={setRuledRange}
+                defaultMonth={new Date(2026, 3, 1)}
+                today={new Date(2026, 3, 8)}
+                locale={ja}
+                disabled={[new Date(2026, 3, 5), new Date(2026, 3, 27)]}
+                aria-label="罫線あり (既定) の期間カレンダー"
+                data-testid="calendar-ruled"
+              />
+              <Calendar
+                mode="range"
+                selected={ruledRange}
+                onSelect={setRuledRange}
+                defaultMonth={new Date(2026, 3, 1)}
+                today={new Date(2026, 3, 8)}
+                locale={ja}
+                disabled={[new Date(2026, 3, 5), new Date(2026, 3, 27)]}
+                bordered={false}
+                aria-label="罫線なし (bordered=false) の期間カレンダー"
+                data-testid="calendar-unruled"
+              />
+            </Flex>
+          </CardContent>
+        </Card>
+
         <Card>
           <CardHeader>
             <CardTitle level={2}>範囲選択 · Popover 内</CardTitle>

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

@@ -55,6 +55,36 @@ export default function Demo() {
           </CardContent>
         </Card>
 
+        <Card>
+          <CardHeader>
+            <CardTitle level={2}>カレンダーの罫線 (bordered)</CardTitle>
+            <CardDescription>
+              ポップアップのカレンダーは既定で日ごとに罫線を引く (Calendar bordered を転送)。
+              bordered={"{false}"} で罫線なしに戻せる。range / multiple / week
+              でも同じ。月・四半期・年の グリッドには日のセルがないため対象外。
+            </CardDescription>
+          </CardHeader>
+          <CardContent>
+            <Flex gap="lg" wrap>
+              <FormField id="ruled-date" label="罫線あり (既定)">
+                <DatePicker
+                  id="ruled-date"
+                  name="ruled_date"
+                  defaultValue={new Date(2026, 0, 15)}
+                />
+              </FormField>
+              <FormField id="unruled-date" label="罫線なし (bordered={false})">
+                <DatePicker
+                  id="unruled-date"
+                  name="unruled_date"
+                  defaultValue={new Date(2026, 0, 15)}
+                  bordered={false}
+                />
+              </FormField>
+            </Flex>
+          </CardContent>
+        </Card>
+
         <Card>
           <CardHeader>
             <CardTitle level={2}>fromDate で過去日を無効化</CardTitle>

package/package.json

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