# Quality checklist

Complete every applicable gate before delivery.

## Content fidelity

- Every page maps to supplied source content.
- Titles, numbers, quotes, attribution, and caveats remain accurate.
- The deck contains no invented claims, cases, sources, or modules.
- Example copy from the starter has been removed.
- Ambiguities are listed for the user instead of silently resolved.

## Visual quality

- The opening page is a cover and the last page is Q&A.
- Each page has one obvious primary communication task.
- No essential body copy is smaller than 20px on the base canvas.
- No text, connector, control, or decoration crosses the safe area.
- Diagrams communicate a real relationship and remain editable.
- Color semantics are consistent; risk red is not used decoratively.
- Notion-style pages contain ample whitespace and no prohibited effects.
- Three consecutive pages do not repeat the same composition.

## Browser behavior

- Previous, next, Home, End, arrow keys, and page indicators work.
- URL hash opens the intended slide and survives refresh.
- Fullscreen enters and exits cleanly without cropping.
- Only the active slide is exposed as the current page.
- No console errors, failed local assets, or unexpected network requests occur.

## Responsive and print

- Desktop canvas fits common 16:9 screens.
- Mobile content stacks without horizontal page overflow.
- Touch controls remain reachable and text remains readable.
- Print produces one complete slide per landscape page.
- Controls, assistant UI, dialogs, toasts, and focus outlines are hidden in print.

## Assistant

- The deck works with no assistant configuration.
- Base URL, API Key, and model can be saved and cleared.
- The request sends only current-page context and the visible conversation.
- A real API Key is absent from all source files.
- Missing configuration and network failures display helpful messages.
- Assistant responses are rendered as text, not injected HTML.

## Privacy and distribution

- Remove personal names, private organizations, internal identifiers, account handles, and chat identifiers unless the user explicitly supplied them for publication.
- Remove debug logs, temporary files, browser profiles, screenshots, and caches.
- Keep required fonts and assets local or document approved remote dependencies.
- Open the packaged entry point after extraction and repeat the smoke check.
