Adom Wiki Skill Pack

@@ -1,7 +1,7 @@ {   "slug": "adom-wiki-skillpack",   "title": "Adom Wiki Skill Pack",-  "version": "0.8.14",+  "version": "0.8.15",   "type": "skill",   "hero": {     "path": "screenshots/hero.png"

@@ -105,9 +105,16 @@     "coarse-first board viewer",     "3D board GPU memory freeze",     "reviewed chip artwork in assembled board",+    "hero GLB versus board LOD",+    "footprint or silkscreen baked into high LOD",+    "image-first component LOD previews",     "shared workspace",+    "project workspace",     "hydrogen/workspace.json",-    "workspace apply"+    "workspace apply",+    "workspace export",+    "ship my hydrogen layout",+    "open in hydrogen"   ],   "discovery_pitch": "Anything touching wiki.adom.inc: publishing, page archetypes, readmes, heroes, discovery, and the wiki-bloat rule (find where a thing already lives before creating any page).",   "sample_prompts": [@@ -124,8 +131,8 @@       "prompt": "Before I create this wiki page, check whether the thing already has a home."     }   ],-  "version": "0.8.14",-  "description": "The Adom Wiki Skill Pack : one main skill plus the focused sub-skills that teach the AI to publish to wiki.adom.inc without breaking pages, name the wiki repo archetypes (Page, Skillpack, Family), and publish rich component pages (chips, molecules, boards). The wiki is six tools in one: git, package manager, releases, discussions, pull requests, and discovery. One package manager install drops the whole set onto your container.",+  "version": "0.8.15",+  "description": "The Adom Wiki Skill Pack : one main skill plus the focused sub-skills that teach the AI to publish to wiki.adom.inc without breaking pages, name the wiki repo archetypes (Page, Skillpack, Family), and publish rich component pages (chips, molecules, boards). The wiki is six tools in one: git, package manager, releases, discussions, pull requests, and discovery. One package manager install drops the whole set onto your container. Includes reviewed Z-up component artwork, surface-selected MPN marking, reusable thumbnail caches and component-page widgets.",   "dependencies": {     "adom/adom-wiki-hero-image": "^0.2.2",     "adom/component-widgets": "^1.1.12"

@@ -176,21 +176,21 @@ Video, local file from the repo (the blob endpoint supports Range, so seeking works), or YouTube via `youtube-nocookie.com`, or Vimeo:  ```html-<video width="1080" controls poster="/blob/app/<slug>/screenshots/hero.png">+<video controls poster="/blob/app/<slug>/screenshots/hero.png">   <source src="/blob/app/<slug>/demo/walkthrough.webm" type="video/webm"></video> ``` -Video rules the sanitizer forces on you:+Video rules (wiki 2026-09-14 and later): -- **A video needs a numeric `width` attribute** (`width="1080"`, not a-  percentage): the sanitizer keeps `controls` / `preload` / `poster` / `src` /-  `width` but strips `style`, and the markdown stylesheet constrains `img` but-  not `video`, so an unsized video renders at its intrinsic width and runs off-  the column (adom/wiki#205 tracks a CSS rule).-- The repo-root path rule applies to video `src` and `poster` exactly like-  images: write the full path from the page root, even (especially) from a-  README inside a folder (`project-workspaces/README.md` must write-  `project-workspaces/demo.mp4`, never `demo.mp4`).+- The sanitizer keeps `controls` / `preload` / `poster` / `src` / `width` and+  strips `style`. A video, audio or iframe is capped at the column width like+  an image, so a `width` attribute is optional; a numeric one still works as a+  fixed size.+- Paths in `src` and `poster` follow the same rule as images. A README inside a+  folder resolves a relative path from its own folder first, then from the page+  root (`project-workspaces/README.md` may write `demo.mp4` for a file that sits+  next to it, or `project-workspaces/demo.mp4`; both resolve). The push answers+  `README_ASSET_UNRESOLVED` when a referenced file exists in neither place. - Verify the rendered page after pushing, same as images.  The full record-and-publish checklist lives in the `demo-video-publishing`

@@ -104,11 +104,12 @@ written** (it does NOT resolve relative to the doc's own folder). So from `docs/ **Reference images by their repo-root-relative path, `docs/img/x.png`, and commit the image at that path.** Then push both the doc and the image with `repo push`. -The same rule covers **video `src` and `poster`**: a README inside a folder writes the full path-from the page root (`project-workspaces/README.md` must write `project-workspaces/demo.mp4`, never-`demo.mp4`). And a video needs a **numeric `width` attribute** (`width="1080"`): the sanitizer-strips `style` and the stylesheet constrains `img` but not `video`, so an unsized video renders at-its intrinsic width and runs off the column. Full checklist: the `demo-video-publishing` skill+The same rule covers **video `src` and `poster`**. Since wiki 2026-09-14 a README inside a folder+resolves a relative path from its own folder first, then from the page root, so+`project-workspaces/README.md` may write `demo.mp4` for a file next to it or the full+`project-workspaces/demo.mp4`; the push answers `README_ASSET_UNRESOLVED` when a referenced file+exists in neither place. Video, audio and iframes are capped at the column width like images, so+a `width` attribute is optional. Full checklist: the `demo-video-publishing` skill (adom/demo-authoring-skillpack).  ## VERIFY BY LOOKING, not by curling