Rework an old SCORM training

Rework an existing SCORM training:

Change an existing interactive lesson (SCORM) in Juno without rebuilding it from scratch, and without losing what already works.

═══ ONE ROUND OF QUESTIONS ═══
Ask me in ONE message, then wait:
1. Which lesson. Find it by name in our library (search_lms_content) and confirm the match with me; never guess between two.
2. What should change: a content fix, a new section, a brand refresh, a translation, a broken interaction, or "make this editable here".
3. Whether the lesson was built in Juno, imported as a package from another authoring tool, or only available to us as a PDF export. If you cannot tell, open it and say what you found. A PDF export is source material, not a lesson: attach it and we build fresh with the create-lesson line instead.
4. Where it stops: preview only, or save when I approve.

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

═══ READ FIRST, THEN A PLAN ═══
Open the current lesson as a draft copy (draft_html_lesson from the saved unit) and read it before proposing anything. Show me a short plan: what stays exactly as it is, what changes, and what the change touches (text, media, tracking, styling). For a lesson built in Juno, the smallest edit that does the job; never regenerate the whole file for a small fix. If it was imported as a package, say plainly what that means: it cannot be edited in place, so you will rebuild it as a new Juno lesson that keeps the original content and media as far as they can be read, and the original stays untouched. Tell me what could not be carried over before you build. Wait for my yes.

═══ PREVIEW, THEN SAVE ═══
Make the approved change, preview it (preview_html_lesson), and show me the activity log proving tracking still fires, including resume. Then, on my explicit yes:
- Lesson built in Juno: save it as a new version (update_html_lesson). Every version stays and I can roll back; tell me how.
- Imported package: save the rebuild as a new lesson (create_html_lesson) with its card basics, and tell me the original is still there.
Saving is live at once; there is no separate publish step. Where learners are mid-way through the old version, say so before you save.

Rules throughout: read before you change; smallest edit that works; say what cannot be carried over; preview and prove tracking before any save; nothing saved without my yes; talk to me in product terms, not tool names.