Adom Wiki

@@ -84,6 +84,33 @@ push the source to the repo; publish the package (manifest + scripts + skills); <installer>`. A Linux consumer installs the package (CLI + skills) and never pulls the Windows installer; the laptop downloads the Windows asset directly by URL. +## Dependencies on the page come from the PUBLISHED package (not repo push)++The Dependencies tab/graph and the "Used by" list are fed ONLY by the+`dependencies` in the last PUBLISHED package version. Declaring dependencies in+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+depending on a part):++```bash+# 1. the TARGET part page must be published (a page that exists only as a repo+#    is not a package the resolver can see)+cd part/ && adom-wiki pkg publish --org adom++# 2. declare the dep in the DEPENDENT board's package.json, owner-qualified:+#    "dependencies": { "adom/<part-slug>": "^1.0.0" }++# 3. publish the board -- THIS is what draws the edge+cd board/ && adom-wiki pkg publish --org adom+```++After step 3 the board's Dependencies graph shows the part, and the part's+page lists the board under Dependents. Re-publish after any dependency change;+repo-pushing the edited package.json alone changes nothing on the graph.+ ## Make a package and cut a release (exact verbs)  ```bash@@ -208,6 +235,18 @@ 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.+- 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`.+ ## Decision table  | You want to | Do this |

@@ -1,7 +1,7 @@ {   "slug": "wiki",   "title": "Adom Wiki",-  "version": "3.7.0",+  "version": "3.8.0",   "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.6.0",+  "version": "3.8.0",   "type": "skill",   "org": "adom",   "org_id": "681d18d2a224243b0d62c9b2",