@elgora/cli 11.0.0 → 12.1.0

package/README.md

@@ -33,16 +33,24 @@ answer.
   funds the new bounty. It reuses the saved approval for those bytes without
   another AI review, or reviews them first.
 - `poster:open-winning-submission` retrieves the finalized winning Submission
-  for the funding Poster and decrypts it locally.
+  for the funding Poster, decrypts it locally, and saves it as one `.tar.gz`.
 - `check-challenge <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.
+- `solver:solvable` lists open bounties still before their Submission
+  deadline, filtered by escrow amount, time left and challenge keywords.
+- `solver:check <bounty_id> <folder_or_file>` runs the Submission check that
+  `solver:submit` and `guardian:open` also run, without submitting, and exits
+  1 on any issue.
+- `solver:submit <bounty_id> <folder_or_file>` packs a folder (subfolders
+  included) or a single file into one `.tar.gz`, encrypts it for the bounty's
+  pinned Guardian roster, and prepares or sends the exact ElgoraHub
+  transaction.
 - `guardian:judgeable` lists open bounties ready for Guardian review.
 - `guardian:open` signs the protected content read, then verifies and decrypts
-  one exact Solver and Submission pair.
+  one exact Solver and Submission pair, extracts its tree into a new or empty
+  folder, and reports the Submission check's issues.
 - `guardian:verdict` publishes a written Verdict and records the same Verdict
   on ElgoraHub.
 - `guardian:deliver-key` wraps one Solver–Submission content key for delivery
@@ -56,6 +64,18 @@ answer.
   `GET /api/bounties/<bounty_id>` inlines.
 
 Run `elgora-cli help <command>` for exact arguments, options, and secrets.
+
+### Which version a bounty needs
+
+It follows the profile the bounty's challenge declares:
+
+- `elgora_markdown_bounty_challenge_v1`: the latest release, at least 12.0.0.
+- `elgora_markdown_bounty_challenge_v0`: CLI 11, which CLI 12 names when it
+  refuses such a bounty; `npx` runs it beside the installed release:
+
+```sh
+npx @elgora/cli@11 poster:open-winning-submission <bounty_id>
+```
 Run `elgora-cli --version` to print the installed release's version; it is the
 version of the npm package or standalone binary in use, stamped in at build
 time, so it stays correct however the CLI was installed.
@@ -128,7 +148,7 @@ A Guardian may retain old and new X25519 keys after rotating the public key for
 the same account. The CLI tries the retained keys locally so an earlier bounty
 can still use the roster and key it pinned.
 
-Never put private keys, decrypted artifacts, or raw Submission keys in command
+Never put private keys, decrypted files, or raw Submission keys in command
 arguments, logs, or submitted files. Each command reads only the secrets it
 needs.
 
@@ -146,7 +166,7 @@ for that invocation without touching the environment. It takes a network name
 passed — for that run only:
 
 ```sh
-elgora-cli guardian:judgeable                        # Base mainnet, the default
+elgora-cli spec-commitment bounty_challenge.md       # Base mainnet, the default
 elgora-cli claim --network base-sepolia 7            # testnet, by name
 elgora-cli claim --network 84532 7                   # the same, by chain id
 export ELGORA_CHAIN_ID=84532                         # testnet for every run in this shell