Adom Wiki Skill Pack

@@ -94,7 +94,7 @@ important enough to state up front: | **wiki-anatomy** | The mental model: the six tools in one, and how the layers relate. | | **wiki-api** | The REST API + ``adom-wiki pkg`` CLI, the two storage layers, the publish workflow. | | **wiki-publish-safely** | The operational pitfalls as hard rules; the verify-in-pup gate. |-| **wiki-readme** | How to make a great README: `README.md` vs `readme.html`, sections, embeds, images. |+| **wiki-readme** | How to make a great README: `README.md` vs `readme.html`, sections, embeds (YouTube player via `::youtube{}`), images. | | **wiki-readme-html** | Build a custom `readme.html`: sandbox limits, shadowing, self-containment, theming, verify loop. | | **wiki-sub-readme** | Make a sub-readme: a 2nd doc in the page repo, linked from the README. The repo-push / relative-link / image-path gotchas. | | **wiki-visibility** | Public vs private source, public releases, the private readme, open vs closed pages. |@@ -120,6 +120,7 @@ important enough to state up front: - "Make a hero for this page" / "the hero disappeared" → wiki-hero - "Show/open hero studio" / "generate a hero" / HERO_STUDIO_REQUIRED → wiki-hero-studio (RUN the app, do not browse the page) - "Write a README for this page" → wiki-readme+- "Embed a YouTube video / demo video in the README" → wiki-readme (`::youtube{id="VIDEO_ID"}`) - "I want a custom HTML readme / tabs / designed layout" → wiki-readme-html - "Make a sub-readme" / "my README is too long, split it" / "link a deep-dive doc" → wiki-sub-readme - "Keep the source private but let people install it" → wiki-visibility

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

@@ -131,7 +131,7 @@       "prompt": "Before I create this wiki page, check whether the thing already has a home."     }   ],-  "version": "0.8.35",+  "version": "0.8.36",   "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",@@ -196,4 +196,4 @@     "email": "[email protected]"   },   "org": "adom"-}+}\ No newline at end of file

@@ -79,6 +79,10 @@ file **byte-for-byte, no sanitizer**. Consequences:   relying on it). - It is a full document of its own: include your own base styles; nothing   cascades in from the wiki.+- **YouTube does not play here.** A player nested in the sandboxed frame+  inherits the sandbox and renders black. For a page with a video, write a+  README.md and put `::youtube{id="VIDEO_ID"}` on its own line (see+  **wiki-readme**, Embeds), or link the video from the readme.html.  ## Self-containment (assets) 

@@ -13,7 +13,8 @@ description: >-   wiki page presentation, mandatory readme sections, readme renders blank, hero in   readme, embed hero, hero image in readme, hero in the body, hero shows twice,   duplicate hero, repeated hero, don't repeat the hero, readme hero image, add-  image to readme, readme screenshots.+  image to readme, readme screenshots, youtube video, embed youtube, youtube in+  readme, video player in readme, demo video, ::youtube. ---  Parent skill: **adom-wiki-skillpack**@@ -165,15 +166,35 @@ Inline image from the repo (blob endpoint), point at a NON-hero screenshot ![Results view](/blob/<type>/<slug>/screenshots/feature-1.png) ``` -Self-contained demo (bake sample data into the HTML, no fetch/WebSocket):+Self-contained HTML demo (bake sample data in, no fetch/WebSocket): README.md+strips `<iframe>`, so either make the whole page a `readme.html` (above), or link+the demo, which the wiki serves rendered: -```html-<iframe src="/blob/app/<slug>/demo/index.html" width="100%" height="500"-  frameborder="0" style="border-radius:8px;border:1px solid #333;"></iframe>+```markdown+[Open the live demo](/<owner>/<slug>/render/demo/index.html)+```++YouTube: put the built-in tag on its own line. The wiki shows YouTube's own+player inline (from youtube-nocookie.com, lazy-loaded, one click to play):++```markdown+::youtube{id="dQw4w9WgXcQ"}+::youtube{url="https://youtu.be/dQw4w9WgXcQ" start="1m30s" title="Product tour"} ``` +- `id` is the 11-character video id; `url` takes any YouTube link form (watch,+  youtu.be, shorts, live, embed). `start` is seconds or `1m30s`; `title` labels+  the frame for screen readers.+- Do NOT paste YouTube's `<iframe>` embed code: the sanitizer strips iframes in+  README.md, and in a readme.html the nested player inherits the sandbox and+  renders black. A plain YouTube link stays a link. Either way the push and+  publish answer `YOUTUBE_EMBED_AVAILABLE` with the exact tag to write; a tag that+  names no video answers `YOUTUBE_TAG_INVALID` and renders nothing.+- Works in the page README (the Overview tab), README.md and README.public.md.+  Folder READMEs do not render tags yet; link the video there.+ Video, local file from the repo (the blob endpoint supports Range, so seeking-works), or YouTube via `youtube-nocookie.com`, or Vimeo:+works):  ```html <video controls poster="/blob/app/<slug>/screenshots/hero.png">