Adom Wiki Skill Pack

@@ -1,7 +1,7 @@ {   "slug": "adom-wiki-skillpack",   "title": "Adom Wiki Skill Pack",-  "version": "0.8.34",+  "version": "0.8.35",   "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.34",+  "version": "0.8.35",   "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",

@@ -714,6 +714,13 @@ from the datasheet and redistribute it, but it must be exact: - Keep the builder and its data in `provenance/tools/`, the previous model in `provenance/`, and say in the   README that the model is AI-generated from the datasheet. +## Component widgets live in the adom org++Widgets meant for every component page (`adom-verified`, `adom-models`, `adom-footprint-variants`, pinout,+chip thumbnail, heat-sink via, molecule, table) live in **adom/component-widgets**, with the tools that write their+JSON in its `tools/`, and are registered in adom/widgets. Never host an ecosystem widget on a personal page+(john/...): build it there and move it before anyone embeds it (John, 2026-10-04).+ ## Every 3D file described: `models.json` and the `::adom-models` widget  A component page soon carries several STEPs and GLBs (the maker's or datasheet-built original, an etched copy, an@@ -727,10 +734,13 @@ archive), `derived_from`, `source`, `sha256`, `git_blob`, `bytes`, `thumb`.  - AIs: read `models.json` before choosing or describing a 3D file; never guess from names. Look at the thumbnails   before writing `unique`: a stale assumption about what a GLB contains is easy to write and wrong.-- Build it with `tools/models_json.py` on john/component-verification inside a page clone: `scan` (adds new files+- Build it with `tools/models_json.py` on adom/component-widgets inside a page clone: `scan` (adds new files   with guessed roles, refreshes hashes, drops vanished ones), `set PATH key=value ...` (describe each file),-  `thumbs` (STEP through the step2glb service, GLB through local headless Chromium + three.js; up axis = the-  model's thinnest axis, glow shells hidden), then push `models.json` and `docs/models/*.png`.+  `thumbs` (each STEP converted on the step2glb service and shot TOP, framed on the wall the part number faces,+  `front` in models.json, and BOTTOM, pads and polarity mark; each GLB one view; up axis = the model's thinnest+  axis, glow shells hidden, the page's own `provenance/tools/glb_post_*.py` applied), then push `models.json` and+  `docs/models/*.png`. The widget opens on a STEP tab (the CAD files people come for) beside a GLB tab.+- Drop superseded models WE built (bloat); keep only a maker's original STEP for anyone who prefers it unmarked. - Show it with `::adom-models{src="/OWNER/SLUG/render/models.json"}` in a `## 3D models` section above the 3D model   provenance: a card per file (thumbnail, STEP/GLB, etched or unmarked and where the part number sits, the   `unique` line, derived-from, a download through the files API), previous versions folded away. It checks each@@ -791,11 +801,11 @@ and shows it near the top with: ::adom-verified{src="/OWNER/SLUG/render/verification.json"} ``` -The widget (john/component-verification) shows a big green check with who verified the page and when, a card+The widget (adom/component-widgets) shows a big green check with who verified the page and when, a card per ordering variant with what has been verified for it, and the full log: each entry's checks, evidence links (overlay images, datasheet pages, IPC references) and the SHA-256 of every verified file. It re-hashes those files in the reader's browser and turns amber when one changed after it was verified, so trust cannot-outlive what was checked. Add entries with `tools/verify_log.py` from john/component-verification; record+outlive what was checked. Add entries with `tools/verify_log.py` from adom/component-widgets; record open questions as `--status open` entries rather than leaving them out. Anyone who verifies something adds their own entry.