Overview of how the fourMs/omo repository is organized.

omo/
├── index.html          # Hub (lists HUB_APPS)
├── support.html        # Sensor feature detect
├── sw.js               # Service worker + cache version
├── manifest.webmanifest
├── shared/             # UI, audio, sensors, ML, sync helpers
└── apps/<slug>/        # One folder per instrument (index.html + app.js)

Each instrument is a static page: HTML shell, shared/app.js for header (Learn, QR, Audio), and an app-specific script.

shared/hub-catalog.js exports HUB_APPS — title, section, synthesis blurb, sensors, and href. The hub, wiki App catalog, and docs/CATALOG.md should stay aligned; regenerate wiki tables with:

node scripts/generate-wiki.mjs

Title Case names can be synced from folder slugs:

node scripts/sync-titles-from-slugs.mjs

• Learn — bindLearn() + pedagogy JSON per slug
• QR — encodes the current instrument URL (shared/qr.js)
• Audio on — user gesture unlock for iOS

Many apps use body.app-shell and put live readouts in control-row (not hidden readout-row).

• manifest.webmanifest — name, icons, display: standalone
• sw.js — CACHE = "omo-vNN"; bump when shared assets or hub logic change
• Install path: Safari / Chrome → Add to Home Screen

Cached assets include hub, support.html, and common shared/* modules — not every app bundle. First visit to an app still fetches that app's index.html and app.js; repeat visits benefit from browser cache + SW.

GitHub Pages serves from the main branch at fourms.github.io/omo/.

Wiki sources live in docs/wiki/ in the repo. Push to GitHub Wiki:

./scripts/push-wiki.sh

Requires gh auth login or GH_TOKEN with repo scope.