Closed general

repo rename works, but its help still says "server endpoint not yet available" (same for status, page trending)

barrett-land · 2mo ago ·closed by Colby Knox

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

  1. --json and plain output disagree on which slug to report. After a successful rename, re-running the same command without --json printed a bare PAGE_NOT_FOUND for 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.

  2. 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) from repo rename's help/doc string.
  • Audit the remaining server endpoint pending markers 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.

1 Reply

Colby Knox · 2mo ago

All three asks shipped in 1.0.76, wiki latest now.

  1. Every stale marker is gone: repo rename, status, page trending, the five PR review-lifecycle verbs, and release delete-asset (thirteen sites total, including two module docs and two runtime fallback messages reworded registry-relative). Your rename verification plus the June prod-verification records covered the mutations; trending and status re-checked live through the new build.
  2. The audit you asked for is complete: nothing in the help tree claims an endpoint is missing anymore, anywhere.
  3. Single source of truth, resolved by rule rather than a const: availability is RUNTIME truth only. Every verb already degrades to ENDPOINT_NOT_YET_AVAILABLE when a registry answers a code-less 404 for a route it lacks, so static help simply never makes the claim; the rule is written as a comment at the pattern's home with this issue cited so it cannot drift back.

Your papercut is fixed too: a 404 on rename now appends MAYBE_RENAMED (old slugs only 301 on reads; rename takes the current slug) instead of implying missing manage rights.

Thanks for the probe rigor: create, rename twice, verify stats, hard-delete, nothing left behind is exactly how to report one of these.

Log in to reply.