make-presentationlisted

# Make a presentation product Read repo instructions first. Route the project from the earliest unresolved gate instead of recreating work. ## Workspace - Derive or confirm `deck-id`, then use `presentation-work/<deck-id>/`. - Original presentation source folders are read-only by default. - Inspect existing artifacts in the source folder, work area, and slide folder before creating anything new. - Reuse equivalent artifacts when they already satisfy the current gate. - **Writing artifacts:** every gate that says "Write X from `templates/X.md`" means create that file in the work area using your runtime's file-write tool (the `Write`/`Edit` tool, or shell redirection if that is all you have). Start from the named template, fill it with real content for this deck, and write it to the path the gate specifies. There is no separate build script — file creation is your responsibility. ## Status - Use the shipped helper at `.agents/skills/make-presentation/scripts/status.mjs`. - If `presentation-work/<deck-id>/STATUS.md` exists, run `node .agents/skills/make-presentation/scripts/status.mjs validate presentation-work/<deck-id>`. - Otherwise initialize it with `node .agents/skills/make-presentation/scripts/status.mjs init <work-root> <deck-id> <source-root> <mode> <mode-reason>`. - Never reset an existing status file unless the user explicitly requests a reset; only then append `--force`. - Treat artifact existence as a clue, not proof that a gate passed. - Run `node .agents/skill