presentation-deck-qalisted

# Finalize the deck for delivery Use when `production-qa` is the current gate or when a deck needs final delivery. Author to the engine's technical rules (from its adapter). ## Engine This gate renders and exports, so it needs the **slide engine** chosen at the prototype gate. Resolve it before QA: - Read the engine from the status tracker via `node .agents/skills/make-presentation/scripts/status.mjs next <work-root>` (the JSON block in `STATUS.md` carries an `engine` field set at the prototype gate). Fall back to the `## Engine` line in `PRESENTATION-BRIEF.md` if the tracker has no engine recorded. - If no engine is recorded anywhere, ask the user now, one question, with a recommended default (see `adapters/`; the bundled reference adapter is `open-slide`). - Read `adapters/<engine>/qa.md` for that engine's preview surface, export command, export format(s), and inspection steps. The sections below are the engine-agnostic backbone; the adapter supplies the engine-specific surface and exports. ## Choose context - Use pipeline mode when `presentation-work/<deck-id>/` exists. Validate its status with the shipped helper. Read the current mode from `STATUS.md`. - Use standalone mode when pipeline artifacts and `STATUS.md` are absent. - In standalone mode, derive a minimal QA context from the deck and notes: purpose, likely audience, material claims, main/backup range, timing assumptions, and unresolved risks. - Do not create a pipeline work area solely for finalization; only