> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase04-session06-public-demo-media-parity-and-offline-loading/implementation_summary.md). # Implementation Summary **Session ID**: `phase04-session06-public-demo-media-parity-and-offline-loading` **Package**: cross-cutting **Completed**: 2026-05-29 **Duration**: about 25 minutes *** ## Overview Implemented public-demo media parity and offline-loading checks for the static demo artifact. The session added a deterministic `media:demo:check` gate, expanded app media catalog coverage for current demo speech, music, showcase, and install media, made lazy music policy explicit in the service worker, and updated browser validation for audio fallback and duplicate-start behavior. The public demo remains standalone: no workspace imports, no local server connections, no LLM endpoints, no War Room federation, and no `EXAMPLES/` promotion. *** ## Deliverables ### Files Created | File | Purpose | | ------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | `scripts/public-demo-media-config.mjs` | Declared public-demo inventory, cache policy, manifest expectations, lazy media exceptions, docs references, and catalog record IDs. | | `scripts/check-public-demo-media.mjs` | Root checker for media files, durations, manifest entries, service-worker policy, docs, catalog mapping, and standalone boundaries. | | `tests/publicDemoMedia.test.ts` | Vitest coverage for config, path rejection, manifest drift, cache drift, lazy media policy, catalog mapping, and workspace import guards. | | `.spec_system/specs/phase04-session06-public-demo-media-parity-and-offline-loading/implementation-notes.md` | Session progress and validation evidence. | | `.spec_system/specs/phase04-session06-public-demo-media-parity-and-offline-loading/security-compliance.md` | Privacy, quarantine, cache, and standalone-boundary review. | | `.spec_system/specs/phase04-session06-public-demo-media-parity-and-offline-loading/IMPLEMENTATION_SUMMARY.md` | Session summary. | ### Files Modified | File | Changes | | ------------------------------------------------- | ------------------------------------------------------------------------------- | | `package.json` | Added `media:demo:check`. | | `apps/web/src/data/mediaCatalog.ts` | Added conditional current public-demo speech, music, and showcase records. | | `apps/web/tests/mediaCatalog.test.ts` | Updated helper expectations and blocker coverage. | | `public-demo/index.html` | Added speech/music duplicate-start prevention and visible speech fallback copy. | | `public-demo/sw.js` | Added explicit lazy music list and install-time precache guard. | | `tests/e2e/public-demo.e2e.ts` | Added audio fallback and duplicate-start Playwright coverage. | | `scripts/README_scripts.md` | Documented checker usage and remediation. | | `docs/media-assets.md` | Documented Session 06 public-demo media parity and current paths. | | `public-demo/README_public-demo.md` | Documented checker, cache policy, and lazy music paths. | | `public-demo/docs_public-demo/static-artifact.md` | Documented lazy media and validation requirements. | | `public-demo/docs_public-demo/validation.md` | Added checked paths, cache version, and command set. | *** ## Validation | Command | Result | | ------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | | `npm run media:demo:check` | PASS | | `npm run battlefield:check` | PASS | | `npm run media:visual:check` | PASS with existing conditional media warnings | | `npm run media:drafts:check` | PASS | | `npx vitest run tests/publicDemoMedia.test.ts apps/web/tests/mediaCatalog.test.ts --config vitest.config.ts` | PASS, 18 tests | | `npm run test:e2e -- --project=public-demo-desktop --project=public-demo-mobile tests/e2e/public-demo.e2e.ts` | PASS, 12 passed and 2 skipped | | `npm run format:check` | PASS | | `npm run lint` | PASS | | `npm run typecheck --workspaces --if-present` | PASS | | `npm run security:secrets` | PASS | | `git diff --check` | PASS | *** ## Notes * `media:visual:check` still reports the expected conditional metadata and non-release blocker warnings from earlier Phase 04 work. * Background music remains lazy-loaded and excluded from `SHELL_ASSETS`. * Public-demo speech, music, showcase, portraits, and install icons remain conditional catalog records with release blockers. * No provider credentials, local absolute paths, raw prompts, or `EXAMPLES/` excerpts were added. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase04-session06-public-demo-media-parity-and-offline-loading/implementation_summary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.