Adom Wiki
Public Made by Adomby adom
How the Adom Wiki (wiki.adom.inc) works and how to drive it with the adom-wiki CLI: the two storage layers (git page repo vs package registry), hosting source by pushing files (not a tarball), making packages, cutting per-platform releases, and the three-tier skill layout (user skills ship, dev-skills/ and publish-skills/ stay source-only). adom-wiki is the current tool; adompkg is deprecated. Read this first before publishing or installing.
Heavy GLB crashed component pages + host webviews; click-to-load gate shipped; kiosk-workcell needs republish
Incident, containment, and one republish ask.
What happened: adom/kiosk-workcell carried a 17.5 MB Draco GLB. Decoding it exhausted the browser renderer process, and because the component page embeds the 3D viewer in a same-origin iframe (one shared process), opening the page crashed the entire page and the Hydrogen webview hosting it. The page was deleted at 17:54 as a stopgap. That delete was a hard delete, so the row, the repo, and the model bytes are gone (repos are not in backups).
Containment, live on prod now: the 3D viewer shell no longer auto-initializes heavy models. Above 8 MB file size or 4M declared vertices (env knobs HEAVY_GLB_INLINE_BYTES / HEAVY_GLB_INLINE_VERTS), it renders an interstitial naming the size ("Large 3D model: N MB, M vertices") with explicit Load 3D model and Download GLB actions. A crash can now only follow a deliberate click, never a page visit. Vertex totals come from the GLB JSON chunk's declared accessor counts (they survive Draco), memoized per commit; the server never decodes geometry. Regression-tested in test/viewers/viewer-owner-routes.test.mjs and verified live on staging with a synthetic 99M-vertex fixture.
Republish ask (@drew2): kiosk-workcell needs republishing from the molecule pipeline. While regenerating, please also export a web-grade decimated GLB: under 8 MB / 4M vertices renders inline automatically; anything heavier is click-to-load. essemtec-puma at 1.1 MB is a good reference for what renders instantly.
Follow-up worth considering (separate, not urgent): a publish-time lint hint for models over the thresholds, so the pipeline learns the budget at publish rather than from the page.