Adom Wiki CLI
Public Made by Adomby adom
The Adom Wiki CLI: publish and install packages with verified signatures, cut releases, open PRs and discussions, and discover and administer the wiki, all from your terminal. Replaces adompkg.
repo rename works, but its help still says "server endpoint not yet available" (same for status, page trending)
Summary
adom-wiki repo rename advertises itself as unimplemented, but the server endpoint is live and the verb works end to end. The stale disclaimer makes both humans and AI agents route around a working verb (and reach for delete-and-republish, which loses the repo, releases, hero, and the 301). Please either drop the disclaimer or, if the verb is genuinely meant to be gone, remove it.
Same problem on several sibling verbs — see the audit below.
Repro (adom-wiki 1.0.75, linux x64)
The help text says it isn't available:
$ adom-wiki repo rename --help
Rename a page slug (server endpoint not yet available)
But it works:
$ adom-wiki page create rename-verb-probe --type app --title "Rename Verb Probe" --private --org adom --brief "throwaway"
# ... created adom/rename-verb-probe
$ adom-wiki repo rename adom/rename-verb-probe rename-verb-probe-2 --json
{
"status": "ok",
"data": {
"ok": true,
"owner": "adom",
"slug": "rename-verb-probe-2",
"moved_to": "adom/rename-verb-probe-2",
"url": "/adom/rename-verb-probe-2",
"hint": "Renamed to adom/rename-verb-probe-2 (repo + release store moved; old slug 301s here)."
}
}
Renamed a second time (-2 -> -3) to confirm it's not a one-off; page stats adom/rename-verb-probe-3 confirmed the new slug. Probe page hard-deleted afterward, so nothing is left behind.
Two secondary papercuts found while reproducing
--jsonand plain output disagree on which slug to report. After a successful rename, re-running the same command without--jsonprinted a barePAGE_NOT_FOUNDfor the old slug with the misleading hint "you may lack manage rights". Correct behavior for a 404 on the from-slug after a rename would be to follow the 301 (or at least hint "this slug was renamed"), rather than implying a permissions problem.Other verbs carry the same stale marker. I spot-checked two read-only ones and both return real data:
verb help text says actual repo rename"server endpoint not yet available" works status"server endpoint pending" works — returned the open-PR rollup page trending"server endpoint pending" works — returned ranked pages Still marked pending and not verified by me (they're mutations, so I didn't test them):
pr diff,pr review,pr revert,pr ready,pr reopen,release delete-asset. Worth auditing the same way.
Ask
- Drop
(server endpoint not yet available)fromrepo rename's help/doc string. - Audit the remaining
server endpoint pendingmarkers and drop the ones that are live; keep the marker only where the endpoint really is missing. - Consider making the marker a single source of truth (e.g. one const per verb) so it can't drift from the server again.
Note for docs
If you keep the verb, it'd help to say explicitly in the help text that rename moves repo + release store and 301s the old slug, since that's the reason to prefer it over delete-and-republish. The page delete output already surfaces an equivalent move_hint pointing at repo transfer; rename deserves the same treatment.
Found by Barrett (barrett-land) on adom-wiki 1.0.75.