@adia-ai/adia-ui-factory 0.8.0 → 0.8.2

package/references/verification.md

@@ -1,35 +0,0 @@
-# Verification — the exit gate
-
-Mode-independent. A surface is done when it passes the **browser gate** + the a11y check — not when it compiles and not when unit tests pass. "Tests pass, ship it" is the anti-pattern: unit tests are necessary, not sufficient (happy-dom/vitest pass for components that render broken in real browsers).
-
-## The browser gate (the real gate)
-
-Render the surface in a real (headless) browser and assert four things:
-
-1. **Zero `console.error` / `pageerror` on load** — collect them during navigation; any is a failure.
-2. **Non-zero bounding boxes** on the key elements — catches the "upgraded but never sized" 0×0 host, where the element exists but renders nothing.
-3. **Read the screenshot** — capture at `deviceScaleFactor: 2` and actually look at it. Content can be present in the DOM yet visually clipped, overlapped, or off-canvas; only the pixels catch that. A probe that screenshots but doesn't read it hasn't verified anything.
-4. **Re-probe after every structural change** — a stale screenshot lies.
-
-Minimal probe shape (Playwright; works against a Vite static host or an SSR dev URL):
-
-```js
-const errors = [];
-page.on('console', m => m.type() === 'error' && errors.push(m.text()));
-page.on('pageerror', e => errors.push(String(e)));
-await page.goto(url, { waitUntil: 'networkidle' });
-const box = await page.locator('my-surface').boundingBox();   // expect non-zero w/h
-await page.screenshot({ path: 'probe.png', scale: 'device' }); // then READ probe.png
-// gate: errors.length === 0 && box.width > 0 && box.height > 0 && (you read the image)
-```
-
-## Diagnosing the "renders empty, zero console errors" page
-
-`customElements.whenDefined(name)` never rejects — if `name` is never imported, its Promise never resolves, so a `Promise.all([...]).then(bootstrap)` gate hangs forever on one dead await. Shell chrome still renders (tag-keyed CSS), the page body is just empty, and nothing errors. Check every awaited tag actually has a registering import before suspecting anything else.
-
-## Accessibility (the adia-ui-specific checks)
-
-Standard a11y applies (labelled landmarks, keyboard paths, AA contrast). The kit-specific traps:
-
-- **Overlays** — drive `<modal-ui>` / `<drawer-ui>` via the `.open` property; a hardcoded `open` attribute on a `showModal` overlay bricks the whole page, and only a live click/`elementFromPoint` probe catches it.
-- **Roles** — a presentational `text-ui variant="heading"` needs a real heading role or `<h*>` wrapper; don't use deprecated `aria-grabbed`.