@invisibleloop/pulse 0.20.11 → 0.20.20

package/docs/.claude/commands/verify.md

@@ -1,84 +0,0 @@
-# Verify
-
-Run the full verification loop on the current page or the page specified in $ARGUMENTS.
-
-## Steps
-
-### 1. Identify the target
-
-If $ARGUMENTS is provided, use it as the file path or route. Otherwise, identify the most recently edited spec file from context.
-
-### 2. Validate the spec
-
-Use `pulse_validate` with the spec file content. If validation fails, report every error clearly and stop — do not proceed to screenshot until the spec is valid.
-
-### 3. Check the dev server
-
-Use `pulse_fetch_page` to confirm the server is responding for the route. If it errors, use `pulse_restart_server` and retry once.
-
-**If `pulse_fetch_page` returns unexpected HTML (e.g. a different project's page title, a Next.js 404, or any non-Pulse response):** check the `X-Pulse` response header — Pulse servers always send this. If it is absent, the wrong server is running on that port. Stop and inform the user before continuing.
-
-### 4. Screenshot
-
-Use `mcp__chrome-devtools__navigate_page` to load the page route, then `mcp__chrome-devtools__take_screenshot` to capture the result. Describe what you see — layout, content, any obvious rendering issues.
-
-### 5. Lighthouse — desktop
-
-Run `mcp__chrome-devtools__lighthouse_audit` on the route with `{ "strategy": "desktop" }`.
-
-**Pass bar: Accessibility, Best Practices, and SEO must all be 100.** Performance is measured and reported but is not a hard requirement (it varies with machine load). Report the actual scores. If Accessibility, Best Practices, or SEO is below 100, identify the failing audit(s), fix the issue, and restart from step 2.
-
-### 6. Lighthouse — mobile
-
-Run `mcp__chrome-devtools__lighthouse_audit` on the same route with `{ "strategy": "mobile" }`.
-
-**Same pass bar: Accessibility, Best Practices, and SEO must all be 100.** Fix any failures and restart from step 2.
-
-**If you need to visually inspect the layout at a mobile viewport width** (e.g. to debug a wrapping or overflow issue), use `mcp__chrome-devtools__emulate` with `viewport: "390x844x2,mobile,touch"` — not `resize_page`. The `emulate` tool reliably sets the viewport; `resize_page` does not reliably trigger responsive layout changes. Reset afterward with `emulate` using the desktop viewport: `"1440x900x1"`.
-
-### 7. Performance
-
-Navigate to the page route, then run `mcp__chrome-devtools__performance_start_trace` with `reload: true` and `autoStop: true`. Report LCP and CLS. Flag any LCP insight that suggests a fixable problem (render-blocking resources, large image load delay, etc.).
-
-### 8. Console errors
-
-Use `mcp__chrome-devtools__list_console_messages` — report any errors or unexpected warnings.
-
-### 9. Code review
-
-Call `pulse_review` with the absolute path to the spec file. Read the source, rendered HTML, validator output, and checklist it returns. Fix every issue before proceeding. This is the structured review — do not skip it or replace it with a manual checklist read.
-
-### 10. Close the browser
-
-Use `mcp__chrome-devtools__list_pages` to get all open pages, then call `mcp__chrome-devtools__close_page` for every page ID returned. This closes the entire browser, not just the tab. `pageId` must be a number, not a string.
-
-### 11. Write verification stamp
-
-Run:
-
-```bash
-date +%s > .pulse-verified
-```
-
-**This must be the last write operation before stopping.** The stop hook compares each edited spec's modification time against this stamp — if any spec is newer than the stamp, the hook blocks. Do not edit any spec file after writing the stamp.
-
-### 12. Report
-
-Summarise:
-- Validation: pass or fail (with errors if any)
-- Visual: what was visible in the screenshot
-- Lighthouse desktop: scores for all four categories
-- Lighthouse mobile: scores for all four categories
-- Performance: LCP and CLS values, any flagged insights
-- Console: any errors
-- Review: pass or issues found and fixed
-
-**Pass bar — all of these must be met before the page is confirmed good:**
-- Validation: clean (no errors, no warnings)
-- Lighthouse desktop: Accessibility, Best Practices, SEO all 100
-- Lighthouse mobile: same
-- CLS: 0.00 — any layout shift is a blocker
-- LCP: report the value; flag and fix any insight that identifies a fixable cause
-- Console: no errors
-
-If any gate fails, fix the issue and run `/verify` again.

package/docs/.claude/coverage-check.js

@@ -1,196 +0,0 @@
-#!/usr/bin/env node
-/**
- * coverage-check.js
- *
- * Called by the Stop hook in .claude/settings.json to enforce test coverage.
- * Runs `npm run test:coverage` and blocks the agent if any src/pages/ file
- * has uncovered lines — except code that cannot be unit-tested without mocking
- * real APIs:
- *
- *   - server fetchers (`server:` blocks) and store fetchers
- *   - action `run:` functions
- *   - `guard:`, `submit:`, and `sitemap:` handlers
- *   - `meta:` blocks (async meta functions hit real data sources)
- *
- * Also honours c8-style ignore comments, which Node's built-in coverage
- * (--experimental-test-coverage) does NOT support natively. In a block or line
- * comment, write:
- *
- *   "c8 ignore next"      — exempts the following line
- *   "c8 ignore next 3"    — exempts the following 3 lines
- *   "c8 ignore start" ... "c8 ignore stop"  — exempts the range
- *   ("coverage-ignore" works as a synonym for "c8 ignore")
- *
- * Outputs a Claude Code hook JSON decision to stdout.
- */
-
-import { execSync } from 'child_process'
-import fs from 'fs'
-import { pathToFileURL } from 'url'
-
-// Property blocks that are exempt — all server-side-only code paths that call
-// real external APIs and cannot run in unit tests.
-const EXEMPT_BLOCK_STARTS = [
-  /^server\s*:/,
-  /^run\s*:/, /^run\s*\(/,
-  /^guard\s*:/,
-  /^submit\s*:/,
-  /^sitemap\s*:/,
-  /^meta\s*:/,
-]
-
-/**
- * Build the set of exempt (1-based) line numbers for a source string:
- * lines inside exempt property blocks, plus c8-ignore-annotated lines.
- *
- * @param {string} src
- * @returns {Set<number>}
- */
-export function computeExemptLines(src) {
-  const srcLines = src.split('\n')
-  const exemptLines = new Set()
-
-  // 1. Exempt property blocks — scan tracking brace/paren depth from block start
-  let i = 0
-  while (i < srcLines.length) {
-    const trimmed = srcLines[i].trimStart()
-    if (EXEMPT_BLOCK_STARTS.some(re => re.test(trimmed))) {
-      let depth = 0
-      let started = false
-      while (i < srcLines.length) {
-        exemptLines.add(i + 1) // 1-based
-        for (const ch of srcLines[i]) {
-          if (ch === '{' || ch === '(') { depth++; started = true }
-          if (ch === '}' || ch === ')') { depth-- }
-        }
-        if (started && depth <= 0) break
-        i++
-      }
-    }
-    i++
-  }
-
-  // 2. c8-style ignore comments (Node's built-in coverage ignores these, so we
-  //    honour them here — the marker line itself is always exempt too)
-  const IGNORE = /(?:c8 ignore|coverage-ignore)(?:\s+(next|start|stop))?(?:\s+(\d+))?/
-  let rangeOpen = false
-  for (let n = 0; n < srcLines.length; n++) {
-    if (rangeOpen) exemptLines.add(n + 1)
-    const m = srcLines[n].match(IGNORE)
-    if (!m) continue
-    exemptLines.add(n + 1)
-    const keyword = m[1]
-    if (keyword === 'start') { rangeOpen = true; continue }
-    if (keyword === 'stop')  { rangeOpen = false; continue }
-    // 'next' (or bare marker) — exempt the following N lines (default 1)
-    const count = m[2] ? parseInt(m[2], 10) : 1
-    for (let k = 1; k <= count; k++) exemptLines.add(n + 1 + k)
-  }
-
-  return exemptLines
-}
-
-/**
- * Returns true if all uncovered line numbers fall on exempt lines.
- *
- * @param {string} filePath
- * @param {string} uncoveredSpec - e.g. "30-36 50"
- * @returns {boolean}
- */
-export function allLinesExempt(filePath, uncoveredSpec) {
-  let src
-  try { src = fs.readFileSync(filePath, 'utf8') } catch { return false }
-
-  // Expand "30-36 50" → [30, 31, 32, 33, 34, 35, 36, 50]
-  const lineNums = []
-  for (const part of uncoveredSpec.split(/\s+/)) {
-    const range = part.match(/^(\d+)-(\d+)$/)
-    if (range) {
-      for (let i = parseInt(range[1]); i <= parseInt(range[2]); i++) lineNums.push(i)
-    } else if (/^\d+$/.test(part)) {
-      lineNums.push(parseInt(part))
-    }
-  }
-
-  const exemptLines = computeExemptLines(src)
-  return lineNums.every(n => exemptLines.has(n))
-}
-
-// ---------------------------------------------------------------------------
-// Main — only when executed directly (the exports above are unit-tested)
-// ---------------------------------------------------------------------------
-
-if (process.argv[1] && import.meta.url === pathToFileURL(process.argv[1]).href) {
-  main()
-}
-
-function main() {
-  // Agent is ending its turn to wait for the user's answer (approval gate or a
-  // mid-flow pause) — let the turn end. The marker is consumed on the user's
-  // next prompt, so the gates return in full force afterwards.
-  if (fs.existsSync('.pulse-awaiting-approval')) process.exit(0)
-
-  // No test files → nothing to check
-  const hasTests = fs.existsSync('src/pages') && (function scan(d) {
-    for (const f of fs.readdirSync(d)) {
-      const p = `${d}/${f}`
-      if (fs.statSync(p).isDirectory()) { if (scan(p)) return true }
-      else if (f.endsWith('.test.js')) return true
-    }
-    return false
-  })('src/pages')
-
-  if (!hasTests) process.exit(0)
-
-  let out = ''
-  try {
-    out = execSync('npm run test:coverage 2>&1', { encoding: 'utf8', timeout: 60000 })
-  } catch (e) {
-    out = e.stdout || e.message
-  }
-
-  // Parse the coverage report — look for lines with uncovered line numbers
-  const lines = out.split('\n')
-  let inReport = false
-  const rawGaps = []
-
-  for (const line of lines) {
-    if (line.includes('start of coverage report')) { inReport = true; continue }
-    if (!inReport) continue
-
-    // Match: #  filename.js | line% | branch% | func% | 30-36 50
-    const m = line.match(/^[#ℹ]\s+([\w./[\]-]+\.js)\s*\|\s*[\d.]+\s*\|\s*[\d.]+\s*\|\s*[\d.]+\s*\|\s*([^|\n]+)$/)
-    if (m) {
-      const uncov = m[2].trim()
-      if (uncov && uncov !== 'uncovered lines') {
-        rawGaps.push({ file: m[1].trim(), uncovered: uncov })
-      }
-    }
-  }
-
-  const gaps = []
-  for (const { file, uncovered } of rawGaps) {
-    // Try to resolve relative to cwd (coverage reports use relative paths)
-    const candidates = [file, `src/pages/${file}`, file.replace(/^.*src\/pages\//, 'src/pages/')]
-    const resolved   = candidates.find(p => fs.existsSync(p))
-
-    if (resolved && allLinesExempt(resolved, uncovered)) continue  // auto-exempt
-
-    gaps.push(`  ${file} — uncovered lines: ${uncovered}`)
-  }
-
-  if (gaps.length) {
-    process.stdout.write(JSON.stringify({
-      decision: 'block',
-      reason: [
-        'COVERAGE GAPS detected. Add tests for these uncovered lines before finishing:',
-        ...gaps,
-        '',
-        'Run `npm run test:coverage` to see the full report.',
-        'Auto-exempt: server fetchers, action run(), guard, submit, sitemap, and meta blocks — these call real APIs and need no tests.',
-        'For anything else that genuinely cannot be tested, annotate it: /* c8 ignore next */ (or next N, or start/stop for a range) — this hook honours those comments even though Node\'s built-in coverage does not.',
-        'Everything else — view branches, mutations, onViewError, pure helper functions — must be covered.',
-      ].join('\n'),
-    }))
-  }
-}

package/docs/.claude/pulse-checklist.md

@@ -1,189 +0,0 @@
-## Spec review checklist
-
-Before finishing any spec, verify every point below. Fix anything that fails.
-
-### Critical
-
-- **`meta` must be a plain object — never a function.** Individual fields (`title`, `description`, `styles`) can be `async (ctx) => value` functions, but `meta` itself is always `{}`.
-
-  ```js
-  // WRONG — meta is not a function factory
-  meta: async (ctx) => ({ title: '...', styles: [...] })
-
-  // CORRECT — meta is a plain object; individual fields are functions
-  meta: {
-    title:       async (ctx) => (await post(ctx)).frontmatter.title,
-    description: async (ctx) => (await post(ctx)).frontmatter.description,
-    styles:      ['/pulse-ui.css', '/app.css'],
-  }
-  ```
-
-- **Do not set `hydrate` in specs.** It is auto-derived by the framework from the URL entry passed to `createServer`. Specs with `mutations`, `actions`, or `persist` are hydrated automatically. Purely server-rendered specs get zero JavaScript — no configuration needed.
-
-- **The default theme is DARK.** When `meta.theme` is unset, the page renders with the dark palette. If the design calls for a light page, set `meta.theme: 'light'` when you **first write the spec** — do not assume light and discover dark at the screenshot, which costs an edit → restart → re-approval cycle. Declare the theme in your plan/build brief, and ask the user if the brief doesn't say.
-
-- **Always restart the server and reload the browser after every file edit — before checking the result.** The dev server restarts on file changes but the browser tab stays stale. The required sequence is: `pulse_restart_server` → `navigate_page`. Never attempt to debug a visual problem without doing both steps first.
-
-### Components first — or creative override
-
-- **Before writing any HTML by hand, check `src/ui/index.js`.** There are 50+ components. Use `button`, `card`, `alert`, `input`, `spinner`, `badge`, `modal`, `nav`, `pagination`, `table`, etc. before writing equivalent HTML from scratch.
-- **Do not reinvent component patterns.** These patterns have dedicated components — never write custom HTML for them unless a creative override applies (see below):
-  - Hero sections → `hero({ title, subtitle, actions, image, ... })`
-  - Product/service cards → `card({ title, body, image, footer, ... })`
-  - Image + text two-column layouts → `media({ image, content, reverse })`
-  - Feature tiles → `feature({ icon, title, description })`
-  - Testimonials → `card({ content, footer })` with quote + avatar/name in the content slot
-  - CTAs → `cta({ title, subtitle, actions })`
-  - Navigation → `nav({ logo, links, actions })`
-  - Footers → `footer({ logo, links, columns, legal, ... })`
-
-- **Creative override — raw HTML throughout is permitted** when the design intent genuinely calls for it: a highly custom visual identity, an asymmetric or typographically-driven layout, a brutalist/editorial/retro/neon/paper vibe where components would constrain the expression, or a layout that requires features a component simply doesn't support (e.g. full-viewport height, custom gradient glows, clamp-scaled display type). This is a deliberate design decision, not a shortcut. When taking this path:
-  - **Declare it in a comment at the top of the spec** so the reviewer recognises it: `// component-free — creative override: <reason>`. This is the signal the review tool reads.
-  - Functional atoms (`button`, `input`, `badge`, `modal`) should still come from components unless there is a specific design reason not to.
-  - `/pulse-ui.css` is always required — it provides the token system your custom CSS will use.
-  - The quality gate replaces the component checklist: **Lighthouse 100 on Accessibility, Best Practices, and SEO — desktop and mobile — plus CLS 0.00 is the pass bar.** (Performance is reported but not gated; it varies with machine load.) A component-free page that passes every audit is correct. A component-heavy page that fails accessibility is not.
-
-- **When reviewing**: before flagging a class name like `.hero` as a violation, first ask whether the `hero()` component could actually reproduce the layout. If the answer is no, it is a creative override — check Lighthouse instead of refactoring. Do not flatten a good custom layout into a generic component just to clear a pattern-match.
-
-- **The review tool auto-detects creative override** from the spec comment. When detected, component pattern checks are shown as advisory (`⚡`) not as failures, and the Lighthouse gate is the stated pass bar.
-
-- **Never write App Store or Google Play download buttons by hand.** Always use `appBadge({ store: 'apple', href })` and `appBadge({ store: 'google', href })`. Raw `<a>` tags with badge images are incorrect — `appBadge` renders the correct accessible, styled badge for each store.
-
-  ```js
-  import { appBadge } from '@invisibleloop/pulse/ui'
-
-  // In a hero() actions slot:
-  ${hero({
-    actions: `
-      ${appBadge({ store: 'apple',  href: 'https://apps.apple.com/...' })}
-      ${appBadge({ store: 'google', href: 'https://play.google.com/...' })}
-    `,
-  })}
-  ```
-
-### Reuse (DRY)
-
-- **Extract a view helper when the same HTML pattern appears 3 or more times in a single spec.** A plain JS function returning an HTML string is sufficient — no framework needed:
-  ```js
-  const card = ({ title, body }) => `<div class="card"><h3>${title}</h3><p>${body}</p></div>`
-  ```
-- **Create a shared component in `src/components/` when the same pattern is needed across 2 or more different specs.** A named export that returns an HTML string — same shape as the `layout()` pattern in the routing guide. Never paste a section's HTML into a second spec: extract it at the second use, then import it from both. (`src/ui/` is the framework's own library inside the package — project-level shared code always goes in `src/components/`.)
-- **Do not abstract a pattern that appears only once.** Duplication is cheaper than the wrong abstraction. Within a single spec, wait until the third use before extracting a helper; across specs, extract at the second use.
-
-### Correctness
-
-- Mutations return plain partial-state objects and have no side effects (no fetch, no DOM access).
-- `persist` contains only serialisable state that should survive a page reload — not ephemeral UI state like a loading flag or temporary selection.
-- `e.target` assumptions in mutations are safe if the element has child nodes — use `e.target.closest('[data-index]')` rather than assuming `e.target` is the element with the attribute.
-- State shape is consistent — avoid a single field that is sometimes `null`, sometimes a string, sometimes a boolean. Use a dedicated `status` field instead.
-- **Never use `state.modalOpen` or conditional modal rendering.** This destroys the `<dialog>` on every render, breaking focus, animation, and native ESC handling. Instead, always render the `<dialog>` in the DOM and use `data-dialog-open="id"` to open it — the runtime handles this without any spec state:
-  ```html
-  <!-- always in the view, never conditional -->
-  ${modal({ id: 'confirm', title: 'Confirm', content: '...' })}
-  <!-- anywhere on the page — opens the dialog, no mutation needed -->
-  ${modalTrigger({ target: 'confirm', label: 'Open' })}
-  <!-- or inline: -->
-  <button data-dialog-open="confirm">Open</button>
-  ```
-  Close is handled natively by `<form method="dialog">` (inside the modal), ESC key, backdrop click, or `data-dialog-close` on any element.
-
-### Defensive data handling
-
-- **Always check `res.ok` before parsing fetch responses.** Never call `res.json()` on a response that may have failed. Never use `await res.text()` as an error message — on a 404 or 500, this returns raw HTML which surfaces directly in toasts and error alerts. The correct pattern:
-  ```js
-  const res = await fetch('/api/...')
-  if (!res.ok) {
-    let message = `Request failed: ${res.status}`
-    try { const j = await res.json(); message = j.message || j.error || message } catch {}
-    throw new Error(message)
-  }
-  return await res.json()
-  ```
-- **Never assume the shape of data from external APIs or server fetchers.** Use optional chaining (`?.`) and nullish coalescing (`??`) at every access point. If a server fetcher can return `null`, the view must handle it — `server.user?.name ?? 'Guest'` not `server.user.name`.
-- **Validate FormData fields before use.** `formData.get('email')` returns `null` if the field is missing. Check for null/empty before passing to an API or database.
-- **Do not trust URL params.** `ctx.params.id` is a raw string from the URL. Validate it before use — check it exists, is the right type, and refers to a real resource. Return a 404 or redirect if it doesn't.
-
-### CSS
-
-- **`app.css` must contain no hex values or raw colour values.** A lint hook enforces this and will block the build. Hex values belong in `public/theme.css` as token definitions; `app.css` references them via `var()` only.
-- **Load order in `meta.styles`:** `pulse-ui.css` → `theme.css` → `app.css`. Theme tokens must be defined before `app.css` references them.
-- **CSS for a shared section lives in the shared `app.css`, once.** Every spec that renders the section lists the same file in `meta.styles`. Never copy a CSS block into a second per-page stylesheet — two copies drift apart. Per-page stylesheets are for styles only one page uses.
-
-### Security
-
-- Any value from user input (URL params, form fields, external APIs) interpolated into view HTML must be escaped.
-- **Every `<form method="POST">` on a `submit` page includes `${server.csrf}`.** CSRF is enforced — a form without the hidden token field gets 403 on submit. Never set `csrf: false` to "fix" a 403; that disables the protection. `csrf: false` is only for endpoints with their own authentication (e.g. signed webhooks).
-- **`submit` returns `{ redirect }` after a successful mutation** (POST-redirect-GET). Rendering success directly from the POST means browser refresh resubmits the form.
-
-### Server-side forms & error pages
-
-- **Forms that must work without JavaScript use `spec.submit`** + `<form method="POST">` with `${server.csrf}` inside. Hydrated `data-action` on the same form is the enhancement, not the requirement.
-- On a validation re-render, show `server.form?.errors` and echo `server.form?.values` back into the inputs via `value=` — failed validation must not wipe what the user typed.
-- **Every site has a custom 404 page** — a spec with `route: '*'`, using the shared `layout()` so it carries the site's nav and footer. Without it, bad URLs show the framework's unbranded default.
-
-### Tests
-
-- Pure logic functions extracted from a spec (e.g. `checkResult`, `validate`, `formatPrice`) must have unit tests in a corresponding `.test.js` file.
-- **When fixing a bug, write a failing test first.** The test must reproduce the bug before the fix is applied, then pass after. This pins the behaviour so the bug cannot silently return. A fix without a regression test is incomplete.
-- **Use `renderSync` / `render` from `@invisibleloop/pulse/testing` to test view HTML output.** Do not test views with raw `html.includes()` — use the query helpers instead:
-  ```js
-  import { renderSync, render } from '@invisibleloop/pulse/testing'
-
-  // Sync — call view directly with mock state/server
-  const result = renderSync(mySpec, { state: { count: 5 }, server: { items: [] } })
-  assert(result.has('button'))
-  assert.equal(result.get('#count').text, '5')
-  assert.equal(result.count('li'), 0)
-
-  // Async — run real server fetchers (integration), or pass server to skip them
-  const result = await render(mySpec, { server: { product: mockProduct } })
-  assert.equal(result.get('h1').text, mockProduct.name)
-  assert.equal(result.attr('img', 'src'), mockProduct.image)
-  ```
-  Supported selectors: `tag`, `.class`, `#id`, `[attr]`, `[attr="value"]`, combinations (`button.primary[disabled]`), and **descendant combinators** (`result.count('.parent li')`, `result.find('tbody tr')`). Descendant selectors match the rightmost token within the ancestor context — they do not return 0 if the ancestor doesn't exist, they simply find no matching descendants.
-
-### Markdown
-
-- **Use `md()` from `@invisibleloop/pulse/md` for `.md` file content.** Never read and parse markdown manually. Pass the result's `html` to `prose()`.
-- **Call the same `md()` fetcher in both `meta` and `server`** — it caches on `ctx._mdCache` so the file is only read once per request. Do not create two separate fetchers for the same file.
-- **Always add `onViewError` on dynamic markdown routes** (routes with `:param` segments loading `.md` files). A missing file throws `{ status: 404 }` which must be caught gracefully.
-
-### View error handling
-
-- **Define `onViewError` on any page where the view could throw due to bad or missing data.** Without it, a runtime view error returns a 500 on the server and shows a generic inline message on the client. With it, the server returns 200 with your fallback HTML instead of a 500, and the client renders your fallback:
-  ```js
-  onViewError: (err, state, serverState) => `
-    <div class="u-p-4 u-text-center">
-      <p>Something went wrong. <a href="">Reload</a></p>
-    </div>
-  `
-  ```
-  Use this on pages that render data from external APIs or user-supplied content — any path where the view can encounter `null`, `undefined`, or unexpected shapes that would cause a crash. It is not required on simple pages with predictable data.
-
-### Store updates from actions
-
-- **Use `_storeUpdate` to push changes to the global store from an action.** Return it from `onSuccess` alongside the local state update — it is stripped from page state and forwarded to the store. All mounted pages that subscribe to the affected keys re-render immediately:
-  ```js
-  onSuccess: (state, theme) => ({
-    saved:        true,
-    _storeUpdate: { settings: { theme } },  // ← merged into store state
-  }),
-  ```
-  `_storeUpdate` only merges into the store — it does not appear in the page's own state. The rest of the return is merged into local state as normal. Use this instead of a full-page reload when a user action changes shared data (theme, cart count, user profile, etc.).
-
-### Accessibility
-
-- Interactive elements without visible text have an `aria-label`.
-- Disabled state is reflected with the `disabled` attribute, not just CSS.
-- The page has a `<main id="main-content">` landmark.
-- **Every element with `data-event`, `data-store-event`, `data-dialog-open`, or `data-dialog-close` is natively interactive (`button`, `a`, `input`, `select`, `textarea`, `summary`) or has `tabindex="0"`.** Non-interactive tags (`div`, `span`, `li`, `td`, etc.) with these attributes are not keyboard reachable. Prefer `<button>` — it is focusable, fires on Enter/Space, and carries the correct ARIA role for free. Only use `tabindex="0"` on a non-interactive element when a `<button>` genuinely cannot be used.
-- **Every interactive element communicates its purpose and state:**
-  - Buttons have visible text or `aria-label`. Links use descriptive text — "click here", "here", "read more" are failures.
-  - Form inputs have an associated `<label for="id">` or `aria-label`. `placeholder` alone is not a label.
-  - Toggle controls (open/close, show/hide, expand/collapse) carry `aria-expanded="true|false"` or `aria-pressed="true|false"`.
-  - While an action is in flight, the trigger button has `aria-busy="true"` or its label changes (e.g. "Saving…"). A spinner alone is not enough.
-  - Active nav items have `aria-current="page"`. Selected items in a list, tab set, or option group have `aria-selected="true"`.
-- **The page has a logical tab order:**
-  - No `tabindex` value greater than 0. Positive tabindex values override the natural DOM order and create a broken tab sequence. Remove them and reorder the DOM instead.
-  - Visually hidden interactive content (off-canvas menus, collapsed panels, `opacity:0` elements) is removed from the tab order with `tabindex="-1"` or the `inert` attribute — CSS alone does not remove an element from tab order.
-  - DOM order matches the visual reading order. When flexbox `order` or CSS grid placement visually reposition elements, the tab sequence still follows the DOM — author the DOM in the order a user would read and interact with the page.

package/docs/public/.pulse-ui-version

@@ -1 +0,0 @@
-0.14.2