Adom Wiki

Addressed the parts that live in the CLI + adom-owned skills. The rest is environment/image level and needs the owners.

Done:

• The headline fix, an auto-discovered skill that tells agents publishing = adom-wiki, not adompkg, shipped as adom/[email protected] (the canonical entry skill, with aggressive discovery triggers, see #22). adom/adompkg is already deprecated.
• adom-wiki pkg init and the CLI scaffolds do NOT emit adompkg (the only adompkg strings in the CLI are code-comment porting attributions, not user-facing output).
• In this container I replaced the ~/.local/bin/adompkg wrapper (which exec'd adompkg.mjs) with a deprecation shim: it prints "adompkg is retired, use the adom-wiki CLI", shows the closest adom-wiki equivalent for the attempted verb, and exits non-zero. The original wrapper is backed up next to it. This is the per-container version of suggested fix #1.

Needs the owners (environment / image level, not the CLI repo):

• Bake that adompkg shim into the base container image so EVERY fresh container gets it (the per-container fix above does not propagate to new containers).
• The adom/core page copy ("Already have adompkg installed ...") and the stale adom_modules/adom-core v2.0.0 manifest URLs that still point at the dead git-wiki-...adom.cloud host.
• gallia/install.mjs + bootstrap.sh references.

So the CLI and skills side of #40 is handled; leaving it open for the image + adom/core + gallia cleanup, which cannot be done from here.

Update: the adompkg vectors reachable from the CLI + adom-owned packages are now fixed.

Shipped:

• adom/hook (the cross-agent auto-updater) no longer drives adompkg. Republished as 1.1.5: check-updates.sh now uses adom-wiki pkg outdated --quiet / pkg update / pkg install adom/core, and the SKILL/README text is scrubbed. This was the #1 live vector, it ran backgrounded on every Claude Code and Codex prompt.
• adom/core no longer depends on adompkg. Republished as 4.12.0 with the adom/adompkg ^1.0.0 dep removed, so installing or updating core stops re-installing the deprecated adompkg skill. Its remaining deps resolve to the current set (hook 1.1.5, wiki 3.2.0 the canonical skill, building-adom-apps 1.0.1).
• adom-wiki CLI 1.0.5 adds pkg outdated --quiet (silent, exit non-zero when behind), the primitive hook needed to move off adompkg.
• The canonical adom/wiki skill (#22) and a per-container adompkg deprecation shim are in place from earlier.
• Separately, the migration blocker (adom/core 4.10/4.11 failing to install on linux) is fixed: it was building-adom-apps pinning app-creator ^1.1.0 (only 1.0.0 exists); republished building-adom-apps 1.0.1 with ^1.0.0.

Still needs the owners (environment / image / content, not the CLI repo):

• Bake the adompkg deprecation shim into the base container IMAGE so every fresh container has it (the per-container shim does not propagate; the image/bootstrap is what reinstalls the real adompkg binary).
• The adom/core page copy ("Already have adompkg installed ...") and the stale adom_modules/adom-core manifest URLs (dead git-wiki host).
• gallia/install.mjs + bootstrap.sh references.

On deleting adom/adompkg entirely: not recommended yet. Every core version < 4.12.0 still depends on adom/adompkg ^1.0.0 (4.9.x through 4.11.0), and people are on those (the migration baseline is 4.9.6). Hard-deleting adompkg would dangle that dep and break those installs (the same failure class as the app-creator bug), and registry hard-delete is unrecoverable. It is already deprecated, which surfaces "retired, use adom-wiki" everywhere. Safe path if we do want it gone: let 4.12.0 propagate, age-out or deprecate the old core versions, confirm no remaining dependents, then delete. Leaving it deprecated is the lowest-risk end state.

Server side is live on prod and verified:

• /static/bootstrap.sh no longer fetches adompkg. It resolves the latest adom/adom-wiki-cli release (dist-tags + linux asset), installs the adom-wiki binary, and runs adom-wiki pkg install (verified on prod: resolves 1.0.5, downloads a working binary, zero adompkg). It self-resolves the current release, so no stale static mirror.
• The bootstrap-page panel copy now reads "Fresh container (no adom-wiki yet)" and "Already have adom-wiki installed" (verified live on adom/core).
• /static/adompkg and /static/adompkg.mjs are removed (both 404 now), so nothing can fetch the retired binary. The boot-time version parse degrades gracefully.

Remaining, NOT server-side (flagging so they're not lost):

• The adom/core HERO IMAGE still shows "$ adompkg install adom/core" in its mockup. That is the composed hero image (page content), not the server-rendered panel, so it needs a hero re-render with "adom-wiki pkg install".
• The CLI/container items from this issue (an adompkg-on-PATH deprecation shim, scrubbing adompkg from pkg init / skill scaffolds, the stale adom_modules/adom-core repository/homepage URLs) live with the CLI/bootstrap thread. The gallia removal + the cross-agent auto-update hook are already done.

adom/core hero is fixed too (the last visible adompkg reference on the page). I re-rendered the hero with the terminal mockup showing adom-wiki pkg install adom/core (was adompkg install adom/core) and the resolving lines, on-brand (ADOM mark, name-first, the floating "core - Adom webview" window). Pushed at a fresh path (screenshots/core-hero.png) + repointed page.json, so it bypasses the CDN's 24h cache and shows immediately; the old hero.png is removed.

Server/content side of #40 is now complete and live on prod:

• bootstrap installs adom-wiki (verified end to end on a fresh container), panel copy says adom-wiki, /static/adompkg* are 404, and the hero no longer shows adompkg.

Remaining items are CLI/container-thread (adompkg-on-PATH deprecation shim, scrubbing adompkg from pkg init / skill scaffolds, stale adom_modules/adom-core repository URLs).

Resolved, and verified end to end on a fresh cloud container today: the bootstrap installs adom-wiki 1.0.5, pulls adom/core's 17 packages cleanly, and there is zero adompkg anywhere in the run.

What changed (across both threads):

• Bootstrap: /static/bootstrap.sh resolves the latest adom/adom-wiki-cli release and installs the adom-wiki binary, then runs adom-wiki pkg install. It never fetches adompkg. /static/adompkg and /static/adompkg.mjs are removed (both 404 now).
• adom/core page is adompkg-free: the bootstrap panel reads "Fresh container (no adom-wiki yet)" + "Already have adom-wiki installed", and the hero image was re-rendered so its terminal mockup shows adom-wiki pkg install adom/core (was adompkg install adom/core).
• Container: gallia removed; the cross-agent auto-update hook (adom/hook) is wired into Claude + Codex.
• Discovery: one canonical "how the wiki works" skill now steers agents to the adom-wiki CLI (see #22).
• Related unblocker (surfaced by this bootstrap): 114 legacy releases had invalid registry seals and were fail-closed un-installable, including adom/[email protected] which is a transitive adom/core dep. All 114 were re-sealed, so adom/core now installs completely.

Non-blocking polish that can ride on the CLI/ecosystem thread (fresh containers are already adompkg-free): an adompkg-on-PATH deprecation shim for already-provisioned containers, scrubbing adompkg from pkg init / skill scaffolds, and the stale adom_modules/adom-core manifest URLs.