v0.2.0

Reborn with a new mission: hub operations. The v0.1.x registry-curation
commands stay in awescholar
(awescholar updater add | enrich | backfill --agentx,
awescholar verify --agentx); this CLI is now the operations supplement —
the commands that need the hub website or its deployments. Every command
wraps the website's own script or workflow; nothing is reimplemented.

Highlights

• agentx sync [--remote] — land data/agents-snapshot.json in the hub
  database. Local mode runs the website checkout's db:apply-snapshot
  (the same Prisma-coupled reconcile the server's boot apply uses);
  --remote dispatches the hub repo's sync-db workflow with its
  production secrets.
• agentx moderate [--approve <id> | --reject <id>] — operate the pending
  verified-run review queue; bare invocation lists it. Passthrough to the
  website's reviews:moderate script.
• agentx mirror — dispatch the hub repo's sync-public workflow, the
  allowlisted bridge to the public agentx-hub repo.
• Config by environment: AGENTX_WEBSITE_DIR (local checkout),
  AGENTX_HUB_REPO (dispatch target), GITHUB_TOKEN/GH_TOKEN
  (dispatch auth). Zero runtime dependencies.

v0.1.2

Final release — the package is deprecated; the registry commands now live
in awescholar (see the README
deprecation notice).

Batch intake from the literature pipeline, and an explicit awescholar
compatibility gate.

Highlights

• agentx add --from-json <file> — batch intake of an
  awescholar render agentx candidate file (snapshot-shaped
  {"agents": [...]} or a bare record array). The file is data, not
  decisions: every record passes the same category/tag validation and one
  live GitHub fetch (stale metrics in the file are ignored),
  already-registered repos are skipped with a notice, and the batch is
  all-or-nothing — nothing is written unless every new record passes.
• awescholar compatibility is detected by output shape, not version
  strings: search records missing the authors/citations keys (installs
  older than 0.2.2) fail with a pip install -U "awescholar>=0.2.2" hint,
  and a missing binary now raises the same hint as a CliError — no silent
  degradation in snapshot, enrich-papers, or refresh-citations.