Demos 04 and 05 work fine locally — operator has assets/X Bot.fbx
present. On the gh-pages deploy the FBX is intentionally absent
(Mixamo license boundary, .gitignored) and the previous onError
handler just logged 'FBX load failed' to the console and left a
stuck '⚠ Load failed — see console' message in the overlay.
Replaces both onError handlers with an in-page card that:
- Explains why the asset is missing (license boundary, not a bug)
- Tells you exactly how to run it locally (Mixamo download path,
where to drop the file, the serve-demo.py command)
- Links to Mixamo + the repo source + back to the gallery
- Lets the ADR-097 helpers scene keep rendering behind it
- Logs at warn (not error) — no more uncaught console.error noise
The success branch is untouched, so local development is identical
to before. 6a2b2bdcbf
Adds a new GitHub Pages workflow that publishes the ADR-097 three.js
demo gallery alongside the existing observatory/, pose-fusion/,
pointcloud/, and nvsim/ deployments. Uses keep_files: true so the
other deployments are preserved.
What ships:
* `examples/three.js/index.html` — new landing page that lists all 5
demos with screenshots, "standalone" vs "needs FBX" badges, and an
honest note explaining the Mixamo X Bot.fbx license boundary
(demos 04 and 05 need a local download from mixamo.com; demos
01-03 run standalone in any modern browser).
* `.github/workflows/threejs-pages.yml` — staged copy of demos/,
screenshots/, README.md, and the new index.html into
`_site/three.js/`. Drops an `assets/README.txt` placeholder
explaining the FBX-not-shipped policy. Triggered on changes to
examples/three.js/** or the workflow itself.
* README.md — adds the live link to the existing demo row
(`▶ three.js Demos (5)`) plus a one-line callout describing the
gallery and the FBX caveat.
After this PR merges, the workflow runs and publishes:
https://ruvnet.github.io/RuView/three.js/d67d9872c1
Adds 'Try it yourself' interactive section to the Ghost Murmur view:
distance + heart-moment sliders that drive nvsim::Pipeline live via the
new runTransient WASM export. Per-tier detectability bars compare
predicted |B| vs each transport's noise floor (NV-ensemble lab, COTS
DNV-B1, SQUID, 60 GHz mmWave, WiFi CSI). Witness for the transient
run is shown alongside the canonical reference witness.
Powered by ADR-093 gap analysis. Live at
https://ruvnet.github.io/RuView/nvsim/
Inspector and Witness rail buttons now switch the inspector tab; Ghost
Murmur button opens a new research view summarising the publicly-
reported April 2026 CIA program and RuView's 3-tier mesh equivalent.
Verified end-to-end with agent-browser. ADR-092 §14b.
Worker now reads import.meta.env.BASE_URL from main thread instead of
self.location.origin so /nvsim-pkg/ resolves under /RuView/nvsim/ on
GitHub Pages instead of bare origin.
Remove non-web content (firmware, rust-port target, claude-flow state,
duplicate ui/ copies) that was causing GitHub Pages builds to error.
Branch now contains only static web assets (~600KB vs ~11GB before).
Co-Authored-By: claude-flow <ruv@ruv.net>
Jekyll ignores files starting with underscore and may fail on
binary WASM files. The .nojekyll file tells GitHub Pages to
serve files directly without Jekyll processing.
Co-Authored-By: claude-flow <ruv@ruv.net>
Changed ambient light from dark 0x446688 to bright 0xccccdd with 5x
multiplier. Bumped SETTINGS_VERSION to 6.
Co-Authored-By: claude-flow <ruv@ruv.net>
ruvnet
github-actions[bot]
ruv