Create an interactive SCORM lesson

Create an interactive, SCORM-tracked lesson in our brand:

Build me a self-contained interactive lesson that Juno tracks like a SCORM package: completion, score, resume, and a record per question.

═══ ONE ROUND OF QUESTIONS ═══
Ask me everything below in ONE message, then wait. If an answer is vague or missing, ask once more for that item only. Do not assume defaults.
1. Source material: pasted text, an attached file, a link, or a unit already in Juno. No real source, no build. Never invent content.
2. Brand: colours, fonts, logo, tone. Read what the account already holds if you can, and ask only for what is missing.
3. Languages, and which one is primary if several.
4. Voiceover: none, or which voice and language.
5. Length in minutes.
6. Interactions that earn their place for THIS material, with a reason each: flip cards, a scenario to try, drag-and-drop, embedded video, a quiz. Reject any that do not serve the content.
7. Tracking standard: SCORM 1.2 or 2004.
Build ONLY from my answers. Add no topics, claims, or interactions I did not ask for.

In that same first message, also ask me my role and the team I support.

═══ BUILD ═══
Read Juno's lesson guide first (get_html_lesson_guide) and follow its tracking contract exactly; it is the source of truth, not your memory. On top of it, I want:
- Full save-and-resume: a returning learner lands on the exact screen and scores they left, and a passed lesson reopens on its results.
- Every graded question recorded individually so per-question analytics work; the score written once, on the final submit.
- Motion that feels alive but stays light: screens transition, elements arrive in sequence, correct answers confirm, wrong ones shake, the progress bar fills. Honour reduced-motion settings. No external libraries; one self-contained file.
- A proper completion screen only on a genuine pass, with the score and a one-line summary; calm on revisit, no confetti twice.

═══ PREVIEW, THEN SAVE ═══
Open it as a draft (draft_html_lesson) and preview it (preview_html_lesson). Show me the activity log proving every expected tracking call fires, then preview again from a mid-lesson saved state to PROVE resume works. Wait for my explicit approval. Only then save it as a unit (create_html_lesson) with its card basics: a one-line description, a level, at least one tag. Saving makes it live at once; there is no separate publish step, so nothing is saved before I say so. If you need a file from my machine, ask me to attach it; never pass a file path as if it were the file.

Rules throughout: one round of questions; build only from my material; follow the platform guide over your memory; preview and prove resume before anything is saved; talk to me in product terms, not tool names.