No dedicated mobieusKnow article for cmi5 packages despite a full standalone admin surface + runtime

Area: mobieusLearn (audit p8) · Surface: mobieusLearn admin — cmi5 packages (/learn/cmi5-packages, /learn/cmi5/launch) · Dimension: documentation · Severity: minor

cmi5 (xAPI-native course packaging, an alternative to SCORM with its own upload/launch/fetch flow) shipped in mobieusLearn Phase 3 but has no dedicated how-to article. The single admin-overview guide gives it two passing sentences with no instructions on packaging requirements, the AU launch flow, the fetch/auth-token exchange, or troubleshooting. SCORM by contrast is documented in depth in the same guide and the api-learn article. A tenant admin trying to upload and launch a cmi5 package has no procedural documentation.

Evidence

cmi5 is a substantial standalone feature: admin CRUD surface (LearnCmi5Controller — /learn/cmi5-packages, /cmi5-packages/new, /{id}, /{id}/delete), a dedicated runtime controller (LearnCmi5RuntimeController — /learn/cmi5/launch/{auId}/start, /learn/api/cmi5/fetch), and templates learn/admin/cmi5/{index,new,show}.php + learn/play/cmi5-wrapper.php. Yet no dedicated wiki article exists: the full /know/index slug list (`grep -oE 'href="/know/[^"]*"'`) contains no cmi5 slug, and direct probes 404: `curl -o/dev/null -w '%{http_code}' /know/learn-cmi5` → 404, `/know/mobieuslearn-cmi5` → 404. The ONLY coverage anywhere is 2 sentences buried in the admin overview guide: `curl -s /know/mobieuslearn-admin-guide | strip | grep -i cmi5` → 'cmi5 packages (/admin/learn/cmi5-packages) — modern, xAPI-native replacement for SCORM' and 'Prefer cmi5 for new content where the authoring tool supports it'. (Compare: SCORM gets 6 mentions and a fuller treatment.)

Suggested fix. Write a /know/learn-cmi5 (or mobieuslearn-cmi5) article covering package format, upload, the AU launch + fetch-URL token exchange, xAPI statement flow, and SCORM-vs-cmi5 guidance; link it from the admin guide's Related articles.

Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.