Adom Wiki

@@ -1,7 +1,7 @@ --- name: adom-wiki user-invocable: true-description: "How the Adom Wiki (wiki.adom.inc) actually works, and how to drive it end to end with the adom-wiki CLI. READ THIS FIRST before publishing, hosting source, sharing a tool, or installing from the wiki. Covers the two storage layers (git page repo vs package registry, which are NOT synced), how to host source (push files, never a tarball), how to make a package and cut per-platform releases, the three-tier skill layout (user skills ship; dev-skills/ and publish-skills/ stay source-only), and a decision table. adom-wiki is the current tool; adompkg and any wiki-v1/v2 or *.adom.cloud slug host are DEPRECATED and dead. Triggers: publish to wiki, host source, share/distribute a tool or CLI or skill, make a package, cut a release, Files tab, clone a wiki page, how does the wiki work, wiki.adom.inc, adompkg, dev skills, publish skills, user skills, dev-skills, publish-skills, keep skills out of the tarball, how to structure skills, why won't my skill publish, dev skill blocked on publish, confirmed_user_skills, skill in the wrong folder, make a skill for my app, standalone skill package, skill in app repo vs separate package."+description: "How the Adom Wiki (wiki.adom.inc) actually works, and how to drive it end to end with the adom-wiki CLI. READ THIS FIRST before publishing, hosting source, sharing a tool, or installing from the wiki. Covers the two storage layers (git page repo vs package registry, which are NOT synced), how to host source (push files, never a tarball), how to make a package and cut per-platform releases, the three-tier skill layout (user skills ship; dev-skills/ and publish-skills/ stay source-only), and a decision table. adom-wiki is the current tool; adompkg and any wiki-v1/v2 or *.adom.cloud slug host are DEPRECATED and dead. Triggers: publish to wiki, host source, share/distribute a tool or CLI or skill, make a package, cut a release, Files tab, clone a wiki page, how does the wiki work, wiki.adom.inc, adompkg, dev skills, publish skills, user skills, dev-skills, publish-skills, keep skills out of the tarball, how to structure skills, why won't my skill publish, dev skill blocked on publish, confirmed_user_skills, skill in the wrong folder, make a skill for my app, standalone skill package, skill in app repo vs separate package, embed a widget, widget tags, ::adom-pinout, pinout diagram on a page, interactive diagram in a README, add a widget to a part page, adom/widgets registry, register a new widget, /api/widgets." ---  # How the Adom Wiki works@@ -435,10 +435,14 @@ a declared file missing from the repo warns with `SECTION_SOURCE_MISSING`. **Widgets from plain markdown**: `::adom-pinout{src="/OWNER/SLUG/render/pins.json"}` on its own line in any README renders a widget from the reviewed registry at **adom/widgets** (widgets.json) as a sandboxed frame: no readme.html needed, so-one widget reaches every page. Unregistered tags render as NOTHING for readers and-a `WIDGET_TAG_UNREGISTERED` push hint for you. Pass data via absolute wiki paths-(usually your own page's `/render/` route); attributes are allowlisted per the-registry entry. Registering a new widget = one reviewed edit to adom/widgets.+one widget reaches every page. `GET /api/widgets` lists every registered widget+with its allowlisted attributes and a paste-ready tag skeleton; start there+instead of guessing names (a `WIDGETS_AVAILABLE` hint on README pushes points+the same way). Unregistered tags render as NOTHING for readers and a+`WIDGET_TAG_UNREGISTERED` push hint for you. Pass data via absolute wiki paths+(usually your own page's `/render/` route: the widget stays generic, the data is+per-page); non-allowlisted attributes are dropped. Registering a new widget =+one reviewed edit to adom/widgets (script URL, element name, attr allowlist).  ## Sensitive pages: the flag and the human-approval gate