chore: update deps

Author: antfu

.github/workflows/ci.yml

@@ -15,7 +15,7 @@ jobs:
     with:
       build: pnpm run ci:build
       # The Build step above already produced a fresh dist/ for this exact
-      # checkout, so skip `test`'s own `build && vitest` — running plain
+      # checkout, so skip `test`'s own `build && vitest` - running plain
       # vitest halves the number of full-monorepo `turbo run build` passes
       # per job, which is where the flaky Windows native-toolchain crash
       # (see scripts/ci-retry.ts) shows up.

AGENTS.md

@@ -121,7 +121,7 @@ export const alias = {
   '@devframes/plugin-assets': p('assets/src/index.ts'),
 }
 
-// update tsconfig.base.json — CSS aliases exist for Vite resolution only;
+// update tsconfig.base.json - CSS aliases exist for Vite resolution only;
 // TypeScript resolves `*.css` side-effect imports through ambient shims.
 const raw = fs.readFileSync(join(root, 'tsconfig.base.json'), 'utf-8').trim()
 const tsconfig = JSON.parse(raw)

alias.ts

@@ -128,7 +128,7 @@ export function devframeNav(prefix = ''): DefaultTheme.NavItem[] {
       text: 'Guide',
       items: [
         ...guideItems(prefix),
-        { text: 'Examples', items: examplesItems(prefix) },
+        { text: 'Examples', link: `${prefix}/examples/` },
       ],
     },
     {

docs/.vitepress/config.ts

@@ -1,7 +1,7 @@
 # A11y × Messages Playground
 
 A focused hub playground for testing **[`@devframes/plugin-a11y`](../../plugins/a11y)**
-alongside **[`@devframes/plugin-messages`](../../plugins/messages)** — and, above
+alongside **[`@devframes/plugin-messages`](../../plugins/messages)** - and, above
 all, the **message → dock navigation** they share.
 
 Where [`vite-devframe-hub`](../vite-devframe-hub) mounts every
@@ -25,27 +25,27 @@ URL.
 
 The window is split in two:
 
-- **Left — App under test.** A tiny client-side-routed app whose every route is
+- **Left - App under test.** A tiny client-side-routed app whose every route is
   broken on purpose:
-  - `/` — a missing `alt`, an icon-only button, an empty link, a skipped heading
+  - `/` - a missing `alt`, an icon-only button, an empty link, a skipped heading
     level
-  - `/images` — a gallery of `alt`-less images
-  - `/forms` — inputs and a select with no labels
-  - `/contrast` — low-contrast text and a custom control with no accessible name
-- **Right — Devtools.** The **A11y Inspector** and **Messages** docks.
+  - `/images` - a gallery of `alt`-less images
+  - `/forms` - inputs and a select with no labels
+  - `/contrast` - low-contrast text and a custom control with no accessible name
+- **Right - Devtools.** The **A11y Inspector** and **Messages** docks.
 
 ## What to try
 
-1. **Live scanning** — open the **A11y Inspector**. It scans the left pane on
+1. **Live scanning** - open the **A11y Inspector**. It scans the left pane on
    load; the Dashboard shows the totals and severity breakdown.
-2. **Route tracking** — click the route tabs in the app under test (`Home`,
+2. **Route tracking** - click the route tabs in the app under test (`Home`,
    `Images`, `Forms`, `Contrast`). Each navigation is a `history.pushState`,
-   which the agent patches — the Violations tab accrues one group per route.
-3. **Select + highlight** — hover a violation to ring the element in the page;
+   which the agent patches - the Violations tab accrues one group per route.
+3. **Select + highlight** - hover a violation to ring the element in the page;
    tick a violation's checkbox to highlight all its elements with numbered
    badges, then hit **Generate fix prompts** in the nav for a paste-ready AI
    prompt covering everything you selected.
-4. **Message → dock navigation** *(the headline)* — open the **Messages** dock.
+4. **Message → dock navigation** *(the headline)* - open the **Messages** dock.
    Each scan mirrors a summary entry plus one entry per violated rule, and every
    entry carries a navigation action. Select an entry and click **View in a11y
    inspector** (or **Open a11y dashboard**): the hub switches the focused dock to
@@ -54,7 +54,7 @@ The window is split in two:
 
 ## How it's wired
 
-`src/a11y-messages-playground.ts` is the whole host — a ~120-line Vite plugin
+`src/a11y-messages-playground.ts` is the whole host - a ~120-line Vite plugin
 that runs `@devframes/hub` in the dev server, mounts the two plugins as docks,
 and attaches the a11y agent as the a11y dock's `clientScript`:
 
@@ -72,13 +72,13 @@ a11yMessagesPlayground({
 scans the app under test) and renders the dock rail from `devframe:docks` shared
 state. The navigation itself rides existing hub primitives: the messages panel
 calls `hub:docks:activate`, the hub broadcasts it, and the client host switches
-the focused dock — the same path a manual dock click takes.
+the focused dock - the same path a manual dock click takes.
 
 ## Files
 
 | File | Role |
 |---|---|
-| `src/a11y-messages-playground.ts` | The Vite host — hub context, static + connection-meta mounts, side-car WS, instance-registry registration |
+| `src/a11y-messages-playground.ts` | The Vite host - hub context, static + connection-meta mounts, side-car WS, instance-registry registration |
 | `vite.config.ts` | Mounts a11y + messages; attaches the a11y agent as its dock's `clientScript` |
 | `src/client/main.ts` | Boots the client host, renders the dock rail + iframe stage |
 | `src/client/app-under-test.ts` | The intentionally-broken, multi-route app the agent scans |

examples/a11y-messages-playground/README.md

@@ -42,13 +42,13 @@ <h1 class="m0 flex items-center gap-1.5 shrink-0 text-sm font-semibold select-no
       </header>
 
       <div class="grid grid-cols-[1fr_1.1fr] min-h-0 flex-1">
-        <!-- Left: the app under test — plain page content the a11y agent scans -->
+        <!-- Left: the app under test - plain page content the a11y agent scans -->
         <section class="min-w-0 of-auto border-r border-base p5">
           <p class="mt0 mb3 text-[0.68rem] uppercase tracking-wider color-muted">App under test</p>
           <div id="app-under-test"></div>
         </section>
 
-        <!-- Right: the devtools — a11y + messages docks -->
+        <!-- Right: the devtools - a11y + messages docks -->
         <div class="grid grid-cols-[210px_1fr] min-w-0 min-h-0">
           <aside class="flex flex-col gap-0.5 of-auto border-r border-base bg-secondary p2">
             <h2 class="px2 py1 text-[0.68rem] uppercase tracking-wider color-muted">Docks</h2>

examples/a11y-messages-playground/index.html

@@ -3,7 +3,7 @@
   "type": "module",
   "version": "0.8.2",
   "private": true,
-  "description": "A focused hub playground that pairs @devframes/plugin-a11y with @devframes/plugin-messages over an intentionally-broken, multi-route app under test — for exercising a11y scanning, route tracking, and message→dock navigation.",
+  "description": "Hub playground that pairs the a11y and messages plugins over a demo app full of accessibility issues.",
   "homepage": "https://github.com/devframes/devframe/tree/main/examples/a11y-messages-playground",
   "scripts": {
     "dev": "pnpm -C ../.. run build && vite --host",

examples/a11y-messages-playground/package.json

@@ -16,14 +16,14 @@ export interface A11yMessagesPlaygroundOptions {
   devframes?: DevframeDefinition[]
   /**
    * Per-dock client scripts, keyed by devframe id. Attached to the mounted
-   * iframe dock so the hub client runtime imports them into the host page —
+   * iframe dock so the hub client runtime imports them into the host page -
    * this is how the a11y inspector's in-page agent gets into the page it scans.
    */
   clientScripts?: Record<string, ClientScriptEntry>
 }
 
 /**
- * A tiny Vite plugin that runs `@devframes/hub` inside the Vite dev server —
+ * A tiny Vite plugin that runs `@devframes/hub` inside the Vite dev server -
  * the same shape as `examples/hub-vite`, trimmed to the two plugins this
  * playground pairs (a11y + messages). One `initHub()` call assembles the whole
  * hub: it mounts each devframe as a dock (attaching the a11y agent as its
@@ -45,7 +45,7 @@ export function a11yMessagesPlayground(options: A11yMessagesPlaygroundOptions =
     },
 
     async configureServer(server: ViteDevServer) {
-      // Vite re-invokes `configureServer` on restart — tear the old hub down so
+      // Vite re-invokes `configureServer` on restart - tear the old hub down so
       // we don't leak the WS port or leave a ghost registry record behind.
       await hub?.close().catch(() => {})
 

examples/a11y-messages-playground/src/a11y-messages-playground.ts

@@ -1,6 +1,6 @@
 // The "app under test": an intentionally-inaccessible, client-side-routed mini
 // app the a11y agent scans. Each route seeds a different family of axe
-// violations, and navigating between them (History API pushState — which the
+// violations, and navigating between them (History API pushState - which the
 // a11y agent patches) exercises the inspector's per-route tracking.
 //
 // Keep the chrome (the route nav) accessible so the deliberate violations stay
@@ -9,7 +9,7 @@
 interface Route {
   path: string
   label: string
-  /** What the route is designed to make axe flag — shown as a hint. */
+  /** What the route is designed to make axe flag - shown as a hint. */
   hint: string
   render: () => string
 }
@@ -70,7 +70,7 @@ const ROUTES: Route[] = [
     render: () => `
       <h1 style="color:#b8b8b8;background:#ffffff">Low-contrast heading</h1>
       <p style="color:#a9a9a9;background:#ffffff">
-        This paragraph sets light grey text on a white background — well below
+        This paragraph sets light grey text on a white background - well below
         the WCAG AA contrast ratio for body text.
       </p>
       <span style="color:#f0c419;background:#ffffff;padding:4px 8px">

examples/a11y-messages-playground/src/client/app-under-test.ts

@@ -32,15 +32,15 @@ function isIframeDock(d: DevframeDockEntry): d is DevframeDockEntry & { type: 'i
 async function main() {
   setStatus('Connecting…')
 
-  // The app under test renders immediately — it's plain page content the a11y
+  // The app under test renders immediately - it's plain page content the a11y
   // agent (imported below as the a11y dock's client script) will scan.
   mountAppUnderTest(appEl)
 
   const rpc = await connectDevframe({ baseURL: HUB_BASE })
   setStatus(`Connected · backend=${rpc.connectionMeta.backend}`, 'ready')
 
   // Boot the hub client runtime: it publishes the shared client context and
-  // imports each dock's client script into this page — here, the a11y agent,
+  // imports each dock's client script into this page - here, the a11y agent,
   // which then scans this document live and mirrors findings into the messages
   // feed. The rail below reads the same `devframe:docks` shared state.
   const host = await createDevframeClientHost({ rpc })