@toon-protocol/rig 4.4.0 → 4.6.0

package/README.md

@@ -212,7 +212,7 @@ rig pr status <event-id> applied
 | `rig issue list` / `rig issue show <id>` | free | the repo's issues + comments from the terminal |
 | `rig pr list` / `rig pr show <id>` | free | the repo's patches/PRs; `show` prints the full patch text (pipe to `git am`) |
 | `rig issue create` | **paid** | file an issue (kind:1621) |
-| `rig comment <root-event-id>` | **paid** | comment (kind:1622) on an issue/patch |
+| `rig comment <target-event-id>` | **paid** | comment (NIP-22 kind:1111) on an issue/patch, or reply to a comment |
 | `rig pr create` | **paid** | publish a patch (kind:1617) from real `git format-patch` |
 | `rig pr status <event-id> <state>` | **paid** | set issue/patch status (kind:1630–1633) |
 | `rig site publish [ref]` | **paid** | deploy a pushed repo as a permaweb site: build the ar.io path manifest (repo paths → Arweave txids) and upload it as one paid store write; prints the gateway URL |
@@ -456,7 +456,7 @@ rig ci serve --relay wss://<relay> --repo <owner-npub>/<repo-id> [--repo …]
 | `--concurrency <n>` | `1` | bounded run slots — more pushes queue (`queue` rounds are published on the progress event) |
 | `--requester <npub\|hex>` | (none) | also accept Service Requests from this pubkey (NIP-C1 operator policy; repeatable) — for running your own coordinator against a repo you do not maintain; such runs show as `seen-in-network` |
 | `--timeout <secs>` | `1800` | wall clock per run; a hung run concludes `timed_out` |
-| `--gateway <url>` | rig's preferred Arweave gateway | prefix for log/artifact URLs (`<gateway>/raw/<txId>`) |
+| `--gateway <url>` | `RIG_ARWEAVE_GATEWAY`, else rig's preferred Arweave gateway | the gateway that serves the store's raw bytes: prefix for log/artifact URLs (`<gateway>/raw/<txId>`) **and** the first gateway the coordinator reads a commit's objects from (same `/raw/` route), ahead of the shared public list — name a private or local gateway (the sandbox's) and the coordinator needs nothing else to read |
 | `--act-bin <path>` | `act` on PATH (or `RIG_ACT_BIN`) | the act binary |
 | `--platform <label>=<image>` | `ubuntu-latest=catthehacker/ubuntu:act-latest` | `runs-on` label → Docker image (repeatable) |
 | `--workdir <dir>` | `<state-dir>/work` | where commits are materialized |
@@ -471,6 +471,11 @@ the decrypted secret inventory — lives under
 `$TOON_CLIENT_HOME/rig-ci/<coordinator-pubkey>/`, so a restart resumes where it
 left off and a relay blip loses no runs. The secrets key itself is never
 persisted and rotates every start (NIP-C1), so re-send secrets after a restart.
+Every value injected into a run — each line of a multi-line value, and its
+URL-encoded and JSON-escaped forms — is redacted (`***`) from that run's job
+logs before they are uploaded to the store and before the log tail goes into
+the Job Result (9841); an artifact whose bytes contain a value is not uploaded
+at all. Values shorter than 4 bytes are not redacted.
 When the wallet cannot pay for the writes a run needs, the coordinator says so on
 stderr and starts no run rather than half-publishing one.
 
@@ -502,6 +507,33 @@ docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -v rig-ci-state:/st
   rig-ci ci serve --relay wss://<relay> --repo <owner>/<repo-id>
 ```
 
+The entrypoint is `rig`, so every verb works (`docker run --rm rig-ci --version`),
+and every environment variable rig honours means the same inside the image
+(`TOON_CLIENT_HOME` is `/state`). act launches each job as a container on the
+daemon behind the mounted socket and copies the checkout in, so no host path
+has to match. Against the [sandbox](#dogfooding-rigs-own-ciyml-on-the-sandbox)
+on the same host, run on the host network with the sandbox's own `localhost`
+addresses — a client dials the endpoint a node **advertises**, and the sandbox
+hub advertises `http://127.0.0.1:3200/ilp` so host-run smokes can reach it
+(sandbox-only; a real connector advertises its public URL, which the default
+bridge network reaches fine):
+
+```sh
+docker run --rm --network host \
+  -v /var/run/docker.sock:/var/run/docker.sock -v rig-ci-state:/state \
+  -e RIG_MNEMONIC='<coordinator phrase>' \
+  -e TOON_CONNECTOR=http://localhost:3200 \
+  -e TOON_CLIENT_CHAIN=solana -e TOON_CLIENT_RPC_URL=http://localhost:8899 \
+  -e TOON_CLIENT_STORE_SEAL_TO=http://localhost:3210 \
+  -e RIG_ARWEAVE_GATEWAY=http://localhost:3000 \
+  rig-ci ci serve --relay ws://localhost:7100 --repo <maintainer-npub>/<repo-id>
+```
+
+`RIG_ARWEAVE_GATEWAY` (or `--gateway`) is both where the published log links
+point and the first gateway the coordinator reads a commit's objects through,
+which is what lets it materialize a commit whose objects live only on the
+sandbox's store.
+
 This is the shape a TOON workload will later spawn.
 
 ### Dogfooding: rig's own `ci.yml` on the sandbox
@@ -712,7 +744,12 @@ per-event fee is quoted and confirmed before publishing; `--yes` skips, `--json`
 without `--yes` is a free estimate:
 
 - `rig issue create --title <t> [--body <b> | --body-file <f> | stdin] [--label <l>]…` — kind:1621.
-- `rig comment <root-event-id> --body <b> [--parent-author <pubkey>] [--marker root|reply]` — kind:1622.
+- `rig comment <target-event-id> --body <b>` — NIP-22 kind:1111. The target is the
+  kind:1621 issue / kind:1617 patch (a top-level comment) or an existing kind:1111
+  comment (a reply). rig reads the target off the relay first, for free, so the
+  thread root's kind and author come from the wire: root scope is uppercase
+  `E`/`K`/`P`, the parent lowercase `e`/`k`/`p`, plus the repo `a` tag. Comments
+  published this way are invisible to rig releases older than 4.6.
 - `rig pr create --title <t> (--range <A..B> | --patch-file <f>) [--body <b> | --body-file <f>] [--branch <name>]` —
   kind:1617; `--range` runs real `git format-patch --stdout` locally and derives the
   `commit`/`parent-commit` tags. A multi-commit range publishes ONE event carrying
@@ -738,8 +775,9 @@ delta: only locally-missing objects are downloaded, and `refs/remotes/<remote>/*
 (tags → `refs/tags/*`) move with a `git fetch`-style report.
 
 `rig issue list|show` and `rig pr list|show` are pure relay reads (kind:1621/1617 by
-the repo `#a` tag; state from kind:1630-1633, latest wins; kind:1622 comments under
-`show`).
+the repo `#a` tag; state from kind:1630-1633, latest wins; comments under `show` —
+NIP-22 kind:1111 matched on the uppercase `E` root tag, merged with legacy kind:1622
+by `created_at`).
 
 ## Library
 
@@ -752,7 +790,9 @@ it — that stays behind the `Publisher` seam:
   a deprecated alias; it is no longer a cap).
 - `nip34-events.ts` — NIP-34 event builders returning `UnsignedEvent`:
   `buildRepoAnnouncement` (30617), `buildRepoRefs` (30618), `buildIssue` (1621),
-  `buildComment` (1622), `buildPatch` (1617), `buildStatus` (1630–1633).
+  `buildComment` (NIP-22 1111; `LEGACY_COMMENT_KIND` = 1622 stays exported for
+  READING old threads and is never written), `buildPatch` (1617),
+  `buildStatus` (1630–1633).
 - `repo-reader.ts` — `GitRepoReader`, read-only local-repo access via injection-safe
   `execFile` git plumbing.
 - `remote-state.ts` — `fetchRemoteState`, the "what does the remote have?" reader.