Adom Wiki

@@ -110,7 +110,7 @@ package.json and `repo push`-ing it does NOT populate the graph ("Depends on 0") -- the repo layer is your source, the registry layer is what the graph reads. To make an edge appear you must `pkg publish`. -Worked recipe -- link one component page as a dependency of another (a board+Worked recipe -- link one hardware page as a dependency of another (a board depending on a part):  ```bash@@ -133,7 +133,7 @@ repo-pushing the edited package.json alone changes nothing on the graph.  ```bash # 1. scaffold or edit a package dir (package.json + README + SKILL.md + scripts)-adom-wiki pkg init <slug> --type app        # app | skill | component | bootstrap+adom-wiki pkg init <slug> --type app        # app | skill | hardware | bootstrap  # 2. publish a version (metadata comes from package.json; no flags to re-supply) adom-wiki pkg publish [--org <org>]          # bump package.json "version" to re-publish@@ -253,17 +253,32 @@ SKILL.md), per-skill: - Keep dev/publish descriptions concrete about the source task ("run `cargo test`   and read the failures", not "testing"). -## Component pages: publish gates and the type is forever--- `pkg publish` of a `component` is HARD-GATED server-side (not bypassable-  with `--skip-lint`): the tarball must include a hero screenshot image AND at-  least one 3D source file (`.step`, `.stp`, or `.glb`). A schematic-only-  board with no layout still needs a placeholder 3D file to publish at all.+## Hardware pages: the type, its kinds, and the publish gates++- The page type is `hardware` (renamed from `component` at the 2026-08+  taxonomy launch, adom/wiki#111). The old spelling is accepted on input+  forever and survives as a KIND; the API emits `hardware`, and /components+  301s to /hardware. Every hardware page carries a `kind`:+  `component` (purchasable part), `molecule` (Adom-built module),+  `project` (factory scaffold layout from the 3D editor; `board` is an+  accepted alias), `equipment` (factory gear).+- `pkg publish` gates are KIND-AWARE and hard (not bypassable with+  `--skip-lint`): component and molecule kinds must ship a hero screenshot+  AND at least one 3D source (`.step`, `.stp`, `.glb`); PROJECTS are exempt+  from the CAD set but should ship at least one layout JSON (the 3D editor's+  molecules-and-wires shape; molecules are keyed as a JSON OBJECT by instance+  name, not an array) or the publish warns PROJECT_MISSING_LAYOUT; equipment+  is exempt (documentation pages).+- Only the purchasable-part kind requires an MPN; project, molecule, and+  equipment identifiers derive from the slug when absent.+- PROJECTS ARE NOT INSTALLABLE: consume them with+  `adom-wiki repo download <ref> --extract` and open the layout in the 3D+  editor (`pkg install` explains this if you try). - A page's `type` is IMMUTABLE after creation. There is no convert; a page   created as the wrong type must be hard-deleted and recreated. Tools that-  filter by type (e.g. the board browser lists only `type=component`) will-  never see a mis-typed page, so create it as `component` from the start:-  `adom-wiki pkg init <slug> --type component`.+  filter by type (the /hardware browser) never see a mis-typed page, so+  create it as `hardware` from the start:+  `adom-wiki pkg init <slug> --type hardware --kind <kind>`.  ## Decision table 

@@ -1,7 +1,7 @@ {   "slug": "wiki",   "title": "Adom Wiki",-  "version": "3.9.0",+  "version": "3.9.1",   "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.0",+  "version": "3.9.1",   "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.",