@elgora/cli 7.5.1 → 9.0.0

package/README.md

@@ -27,10 +27,15 @@ answer.
 
 ## Commands
 
-- `poster:publish-fund` publishes approved `bounty_challenge.md` bytes and
-  funds the new bounty.
+- `poster:review` checks a bounty page and saves its readiness certificate
+  with `--signoff-out <file>`. Rejected pages print the full issue list and exit 2.
+- `poster:publish-fund` requires `--signoff <file>`, publishes those exact
+  approved `bounty_challenge.md` bytes, and funds the new bounty without another AI review.
 - `poster:open-winning-submission` retrieves the finalized winning Submission
   for the funding Poster and decrypts it locally.
+- `check-page <bounty_challenge_md_path|->` checks structural conformance offline,
+  returns an issue list and exits non-zero on failure. It needs no wallet or
+  network and does not replace hosted semantic readiness review.
 - `spec-commitment` reproduces the challenge's `spec_commitment` offline.
 - `solver:submit` encrypts a Submission for the bounty's pinned Guardian roster
   and prepares or sends the exact ElgoraHub transaction.
@@ -41,7 +46,8 @@ answer.
   on ElgoraHub.
 - `guardian:deliver-key` wraps one Solver–Submission content key for delivery
   so the funding Poster can retrieve the winning work; idempotent, and accepted
-  only for the pair ElgoraHub currently records or the finalized winner.
+  only for the pair ElgoraHub currently records or the finalized winner. While
+  a settlement is not yet finalized it delivers nothing and exits `75`.
 - `claim` prepares or sends the winning Solver's reserved award or the
   Poster's queued refund, as selected from finalized ElgoraHub state.
 - `verification-record` is a plain, unauthenticated GET that fetches or lazily
@@ -79,6 +85,11 @@ needs.
 
 ## Deployment configuration
 
+Since 8.0.0 the default deployment is **Base mainnet** (`base`, chain `8453`),
+which escrows real USDC. Elgora's staging deployment runs on **Base Sepolia**
+(`base-sepolia`, chain `84532`) behind `https://staging.elgora.ai`. A run that
+selects no network prints one stderr line saying it used the default.
+
 Every command accepts `--network <name|chain id>`, which selects the deployment
 for that invocation without touching the environment. It takes a network name
 (`base`, `base-sepolia`, `local`) or that network's chain id (`8453`, `84532`,
@@ -86,9 +97,10 @@ for that invocation without touching the environment. It takes a network name
 passed — for that run only:
 
 ```sh
-elgora-cli guardian:judgeable                        # the default deployment
-elgora-cli claim --network base-sepolia 7            # one invocation, by name
+elgora-cli guardian:judgeable                        # Base mainnet, the default
+elgora-cli claim --network base-sepolia 7            # staging, by name
 elgora-cli claim --network 84532 7                   # the same, by chain id
+export ELGORA_CHAIN_ID=84532                         # staging for every run in this shell
 ```
 
 The chain's public RPC, the ElgoraHub address, the escrow token, and the subgraph
@@ -101,10 +113,11 @@ and which values it defaults. Supply a complete, coherent configuration when
 targeting a deployment this CLI release does not know about, and do not mix
 addresses or endpoints from different deployments.
 
-Commands that use the public API accept `--api-base-url <url>`. That is a
-separate choice from the chain: it names one API deployment, and the flag wins
-over `ELGORA_API_BASE_URL` for that invocation. Point it at an API serving the
-deployment you selected.
+The API follows the chain too: `https://elgora.ai` for `base` and
+`https://staging.elgora.ai` for `base-sepolia`. Commands that use the public API
+accept `--api-base-url <url>`, which wins over `ELGORA_API_BASE_URL` and that
+default for one invocation — for example to reach a Vercel preview. Point it at
+an API serving the deployment you selected.
 
 Protected API reads and writes use one EIP-712 approval per request. The
 signature is bound to the method, path, body, query, API host, and a recent