> Aperture 0.1.0 — experimental, unpublished. [Package archive](/downloads/bolted-aperture-0.1.0.tgz).

# Integration verification

Report actual evidence, not inferred compatibility.

1. Confirm the installed package/version and correct entry point. Validate the exact supplied recipe with strict mode; compare it to the brief. Run the project's type check and production build.
2. Check host dimensions and zero padding; content is a direct child filling the host. Persistent controls remain outside the clip and reachable at phone widths.
3. Exercise open, close, rapid reversal and unmount during playback. Interrupted/destroyed promises must not trigger stale focus or navigation. No orphan SVG, ResizeObserver, animation driver, event listener or body scroll lock remains after cleanup.
4. Test keyboard activation. For dialogs: heading/content focus after successful opening, reachable close control, Escape, focus return and scroll restoration. For galleries: captions/alt text and working controls. For navigation: real destination, Cancel if supplied, ordinary and modified links, back/forward behavior.
5. Test system reduced motion or the `always` setting. Automatic transitions complete instantly. Test unsupported-capability fallback when practical. Keep meaningful no-JS navigation/content; do not gate essential information behind a decorative effect.
6. Inspect wide and narrow layouts, clipping, readable text, touch targets and browser console errors. Use a real Safari/iPhone pass before promising that device compatibility. Unit models alone do not certify SVG rendering, native focus or GPU performance.

If an environment limits a check, state that limitation. Avoid adding GSAP, Three.js, a registry, skill or MCP server merely to use a recipe; the normal API and these documents are sufficient.