@elgora/cli 11.0.0 → 12.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +23 -5
- package/dist/cli.js +1486 -747
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -33,16 +33,22 @@ answer.
|
|
|
33
33
|
funds the new bounty. It reuses the saved approval for those bytes without
|
|
34
34
|
another AI review, or reviews them first.
|
|
35
35
|
- `poster:open-winning-submission` retrieves the finalized winning Submission
|
|
36
|
-
for the funding Poster and
|
|
36
|
+
for the funding Poster, decrypts it locally, and saves it as one `.tar.gz`.
|
|
37
37
|
- `check-challenge <bounty_challenge_md_path|->` checks structural conformance offline,
|
|
38
38
|
returns an issue list and exits non-zero on failure. It needs no wallet or
|
|
39
39
|
network and does not replace hosted semantic readiness review.
|
|
40
40
|
- `spec-commitment` reproduces the challenge's `spec_commitment` offline.
|
|
41
|
-
- `solver:
|
|
42
|
-
and
|
|
41
|
+
- `solver:check <bounty_id> <folder_or_file>` runs the Submission check that
|
|
42
|
+
`solver:submit` and `guardian:open` also run, without submitting, and exits
|
|
43
|
+
1 on any issue.
|
|
44
|
+
- `solver:submit <bounty_id> <folder_or_file>` packs a folder (subfolders
|
|
45
|
+
included) or a single file into one `.tar.gz`, encrypts it for the bounty's
|
|
46
|
+
pinned Guardian roster, and prepares or sends the exact ElgoraHub
|
|
47
|
+
transaction.
|
|
43
48
|
- `guardian:judgeable` lists open bounties ready for Guardian review.
|
|
44
49
|
- `guardian:open` signs the protected content read, then verifies and decrypts
|
|
45
|
-
one exact Solver and Submission pair
|
|
50
|
+
one exact Solver and Submission pair, extracts its tree into a new or empty
|
|
51
|
+
folder, and reports the Submission check's issues.
|
|
46
52
|
- `guardian:verdict` publishes a written Verdict and records the same Verdict
|
|
47
53
|
on ElgoraHub.
|
|
48
54
|
- `guardian:deliver-key` wraps one Solver–Submission content key for delivery
|
|
@@ -56,6 +62,18 @@ answer.
|
|
|
56
62
|
`GET /api/bounties/<bounty_id>` inlines.
|
|
57
63
|
|
|
58
64
|
Run `elgora-cli help <command>` for exact arguments, options, and secrets.
|
|
65
|
+
|
|
66
|
+
### Which version a bounty needs
|
|
67
|
+
|
|
68
|
+
It follows the profile the bounty's challenge declares:
|
|
69
|
+
|
|
70
|
+
- `elgora_markdown_bounty_challenge_v1`: the latest release, at least 12.0.0.
|
|
71
|
+
- `elgora_markdown_bounty_challenge_v0`: CLI 11, which CLI 12 names when it
|
|
72
|
+
refuses such a bounty; `npx` runs it beside the installed release:
|
|
73
|
+
|
|
74
|
+
```sh
|
|
75
|
+
npx @elgora/cli@11 poster:open-winning-submission <bounty_id>
|
|
76
|
+
```
|
|
59
77
|
Run `elgora-cli --version` to print the installed release's version; it is the
|
|
60
78
|
version of the npm package or standalone binary in use, stamped in at build
|
|
61
79
|
time, so it stays correct however the CLI was installed.
|
|
@@ -128,7 +146,7 @@ A Guardian may retain old and new X25519 keys after rotating the public key for
|
|
|
128
146
|
the same account. The CLI tries the retained keys locally so an earlier bounty
|
|
129
147
|
can still use the roster and key it pinned.
|
|
130
148
|
|
|
131
|
-
Never put private keys, decrypted
|
|
149
|
+
Never put private keys, decrypted files, or raw Submission keys in command
|
|
132
150
|
arguments, logs, or submitted files. Each command reads only the secrets it
|
|
133
151
|
needs.
|
|
134
152
|
|