skill

Adom Wiki

Public Made by Adom

by adom

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.

wikiclipackagesregistrypublishingguide
Overview Files Skills Discover Packages Releases Dependencies Issues8 Breadcrumbs Pull Requests Activity
Closed general

Org transfer drops hero provenance: long-published page now blocked by HERO_STUDIO_REQUIRED on republish

John Lauer · 2mo ago ·closed by John Lauer

Repro (live, 2026-07-24)

  1. adom-wiki-skillpack (published continuously since June, hero set 2026-06-21, pkg 0.7.6/0.7.7 published fine, 0.7.7 THIS morning) is transferred: adom-wiki repo transfer adom-wiki-skillpack --to-org adom -> ok, owner now adom.
  2. Next adom-wiki pkg publish --version 0.7.8 -> 400 HERO_STUDIO_REQUIRED, reason: no_hero.
  3. But the hero is fine: adom-wiki page hero adom-wiki-skillpack shows it linked and serving at the NEW owner path (/api/pages/adom/adom-wiki-skillpack/files/screenshots/hero.png, 897 KB, sha a172e1aa..., updated 2026-06-21).
  4. Re-linking (page hero --image screenshots/hero.png) also refuses: "The hero PNG does not carry Hero Studio provenance."

The bug

The transfer appears to drop the page's hero REGISTRATION (or its grandfathered status), and the publish validator then treats a June-era hero as a NEW hero, which now must come from Hero Studio. Net effect: transferring any pre-Hero-Studio page bricks its ability to publish until a human redoes the hero in the studio.

Asks

  • Transfer should carry the hero registration/provenance (or grandfather flag) with the page.
  • page hero re-link of the SAME sha256 already registered to the page should not require new provenance; nothing changed but the owner.
  • If intended, the transfer output should warn loudly that publishing will be blocked until a Hero Studio session.

Page in this state right now: adom/adom-wiki-skillpack (content updated via repo push; pkg stuck at 0.7.7 pending a hero).

Filed by Claude on John's behalf.

1 Reply

John Lauer · 2mo ago

Retracting this, I had it backwards. John's call: the Hero Studio requirement is intended and welcome, wiki heroes have been looking rough and pre-studio ones SHOULD get remade in the studio rather than grandfathered through. So a transfer surfacing an old hero for a redo is a feature, not a regression. We'll run Hero Studio for this page and republish. Sorry for the noise, and the duplicate-guard point in #68 noted, I'll search before filing next time.

Log in to reply.