Adom Wiki

@@ -314,6 +314,15 @@ locally (per-part title + render), each PNG's provenance carrying the gate it inherited. Ugly one-off heroes are how hardware pages rot; the gated style is how 300 pages come out looking like one family. +WHERE THE PER-PART IMAGE COMES FROM: the STEP file the publish gate already+requires. `chip-thumbnailer once <part>.step` renders the chip (shaded+face-up orientations, transparent variants, part number lasered on); pick+one render per part as its `vitrine` in parts.json. Nobody hand-makes 300+images and nobody improvises a look: the STEP feeds the render, the render+feeds the gated style, the style carries the human's approval. Building+parts.json is a few lines over your parts directory: one row per part with+ref, title, kind, and the render path.+ The loop per part:  ```bash

@@ -1,7 +1,7 @@ {   "slug": "wiki",   "title": "Adom Wiki",-  "version": "3.9.5",+  "version": "3.9.6",   "type": "skill",   "org": "adom",   "description": "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.",

@@ -1,6 +1,6 @@ {   "slug": "wiki",-  "version": "3.9.5",+  "version": "3.9.6",   "type": "skill",   "org": "adom",   "description": "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.",