cascrow-cli 3.0.0 → 3.1.0

package/CHANGELOG.md

@@ -1,6 +1,23 @@
 # Changelog
 
-## 3.0.0 — unreleased (owner publishes)
+## 3.1.0 — 2026-10-20
+
+Prepared as 3.0.1 (texts only) and never published; new options made it a minor release.
+
+- **New command `cascrow human-review --contract <id> [--milestone <id>] [--reason "…"]`** (either party asks a person at cascrow to review a verification outcome, Art. 22(3) GDPR; decided within one month, both parties receive the decision with its reasons) **and `cascrow human-review --contract <id> --list`** (the requests and their decisions). A request already open prints its deadline and exits 0. A refused call's error now carries the server's body.
+- The review-queue help no longer says an undecided milestone completes after 48 h or 14 days: it completes when its window closes only when the panel's own YES opened the review and the contract's terms let silence count; any other review goes to cascrow's human review.
+- **`cascrow create` takes `--review-days <n>`** (your review window, 2–30 days, default 14; under 7 only if both parties registered as businesses) **and `--panel-alone`** (the panel decides alone: YES above 85 % completes, anything else is a rejection the builder can resubmit against). The server validates both and answers with its own sentence.
+- `cascrow verify` says "5 AI models run by 5 different providers" (was "5 independent AI models").
+- New hint for **`SCREENING_UNAVAILABLE`** (the new-money sanctions screen fails closed — nothing was created; retry), and the V3 text table carries the no-arbiter veto sentence.
+
+The 3.0.1 notes, unchanged:
+
+- The wallet-linking instructions (the custody-path refusal and the builder agent) follow cascrow's Sign-In with Ethereum challenge: `GET /api/user/wallet/challenge?address=<your wallet>`, sign the returned message with that wallet, `POST /api/user/wallet` — or `npx cascrow-signer@0.2.0 link`. The old one-line challenge is refused by the server.
+- `cascrow v3 sign` runs the pinned `cascrow-signer@0.2.0`; 0.1.0 can no longer link a wallet.
+- The builder agent names the panel's OpenAI model correctly (GPT-4o-mini).
+- The package now carries its MIT `LICENSE` and ships only `index.js`, `README.md`, `CHANGELOG.md` and `LICENSE`. `builder-agent.js`, a demo agent that no command runs, stays in the repository.
+
+## 3.0.0 — 2026-09-27
 
 - **`cascrow join` says what the builder can do now**: a $0 verification contract is active at once; a contract with an amount waits for the payer's MilestoneEscrowV3 offer, accepted with your own key (`npx cascrow-signer@0.1.0 accept --milestone <id>`). The JSON carries the server's `status` and `activated`. The builder agent prints the same.
 - **`cascrow review --decision APPROVE`** says "approved and completed (a verification-only contract: no money moves)" and prints the contract status; the "escrow is being released" line and the "Release tx" it never received are gone.
@@ -11,12 +28,12 @@
 - A COMPLETED milestone no longer reads "funds released": the line says whether no money was held (verification only) or a MilestoneEscrowV3 escrow paid out on chain. `review` / `review-queue` describe a verdict that completes or hands back a verification-only milestone and moves no money.
 - The builder agent (`builder-agent.js`) waits for the milestone to be active rather than "funded", and its demo deliverable describes the product as it is now.
 
-## 2.1.0 — unreleased (owner publishes)
+## 2.1.0 — not published on its own, released as part of 3.0.0
 
 - `cascrow v3 offer | acceptance | accept-submit | prepare | report-tx | attestation | claims` — the MilestoneEscrowV3 remote calls. `cascrow v3 sign <command…>` runs the PINNED local signer (`npx cascrow-signer@0.1.0`) with this terminal attached; the CLI itself stays dependency-free and never sees a key.
 - `cascrow fund` refuses a MilestoneEscrowV3 milestone with the way to fund it; every V3 refusal code prints what can be done about it; a V3 verification reads as a recommendation that moves no money.
 
-## 2.0.0 — unreleased (owner publishes)
+## 2.0.0 — not published on its own, released as part of 3.0.0
 
 - **Breaking: `cascrow escrow-fund --private-key` is removed.** It sent your EVM private key to cascrow, which signed the deposit server-side; cascrow no longer accepts, stores or signs with anyone's key. Fund a v2 escrow by signing locally: `GET /api/agent/escrow-prepare` returns the two unsigned transactions, you sign and broadcast them with your own wallet, then `POST /api/escrow/sync`. Funding a MilestoneEscrowV3 contract from an API client is not available yet. **If you ever passed a private key to this command, treat that key as exposed and move its funds to a new wallet.**
 - `cascrow register` no longer receives a generated wallet: registration returns `wallet: null` and a note on how to link your own (`GET /api/user/wallet/challenge` → sign → `POST /api/user/wallet`).

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Cascrow
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -2,7 +2,7 @@
 
 Command-line interface for [Cascrow](https://cascrow.com) — trust infrastructure for the agent economy (AI verification, on-chain reputation, and a non-custodial milestone escrow in native XRP), for shells, CI pipelines, and subprocesses.
 
-AI agents and their operators use Cascrow to create milestone-based contracts, submit proof of completion, and get verified by a **5-model AI majority vote**, anchored on the XRP Ledger. For paid work the AI verdict is a signed, non-binding recommendation: the money sits in a MilestoneEscrowV3 smart contract that only the parties (or an arbiter they chose) can move — cascrow holds no key and never signs.
+AI agents and their operators use Cascrow to create milestone-based contracts, submit proof of completion, and get verified by a **5-model AI majority vote**, anchored on the XRP Ledger. For paid work the AI verdict is a signed, non-binding recommendation: the money sits in a MilestoneEscrowV3 smart contract that only the parties (or an arbiter they chose) can move — cascrow holds no key that can move escrowed funds and never signs an escrow transaction.
 
 ## Install
 
@@ -60,8 +60,9 @@ is never anchored.
 | `review-queue` | As funder: list milestones still waiting for your verdict | Yes |
 | `v3-claims` | As payer: list MilestoneEscrowV3 claims you can still object to on chain | Yes |
 | `v3 offer \| acceptance \| accept-submit \| prepare \| report-tx \| attestation \| claims` | MilestoneEscrowV3, remote half — cascrow prepares and reads, you sign | Yes |
-| `v3 sign <command…>` | Runs the pinned local signer, `npx cascrow-signer@0.1.0 <command…>` — your key stays on your machine | Signer's own |
+| `v3 sign <command…>` | Runs the pinned local signer, `npx cascrow-signer@0.2.0 <command…>` — your key stays on your machine | Signer's own |
 | `review` | As funder: approve or reject a milestone under manual review | Yes |
+| `human-review` | Either party: ask a person at cascrow to review a verification outcome (Art. 22(3) GDPR), `--list` its decisions | Yes |
 | `me` | Print this agent's ID | Yes |
 
 Run `cascrow --help` (or `cascrow`) any time for the full, always-current option reference.
@@ -166,8 +167,8 @@ No options.
 No options. Lists the contracts on which you, as funder, still owe a manual
 verdict on a verification-only contract — the pull behind the
 `manual_review.required` webhook. A webhook nobody received is a decision nobody
-makes; cascrow completes an undecided milestone when its review window closes —
-48 hours under review mode `MANUAL_AUTO` or `AUTO`, 14 days otherwise. A verdict completes or hands back the milestone and moves no money.
+makes; cascrow completes an undecided milestone when its review window closes
+only when the panel's own verdict opened the review with a YES — any other review goes to cascrow's human review instead; the window is the contract's `reviewWindowDays` (default 14 days; 48h on an agent contract created before 2026-10-20 in review mode `MANUAL_AUTO` or `AUTO`). A verdict completes or hands back the milestone and moves no money.
 
 ### `review`
 
@@ -228,7 +229,7 @@ cascrow verify --contract <contractId> --proof "API live at https://api.example.
 # The verdict is a recommendation. The builder claims on chain; the payer releases or objects.
 ```
 
-`cascrow v3 sign …` runs the pinned local signer (`npx cascrow-signer@0.1.0`), which keeps
+`cascrow v3 sign …` runs the pinned local signer (`npx cascrow-signer@0.2.0`), which keeps
 your key on your machine. This CLI never takes a private key (`escrow-fund`, which did, was
 removed in 2.0.0 — if you ever passed a key to it, treat that key as exposed and move its funds).
 

package/index.js

@@ -16,7 +16,7 @@ const API_KEY  = process.env.CASCROW_API_KEY ?? "";
 // app). v3-client-text-parity.test.ts holds the copy equal to the owner.
 // BEGIN v3-client-text
 const V3_CLIENT_TEXT = {
-  "signerPin": "cascrow-signer@0.1.0",
+  "signerPin": "cascrow-signer@0.2.0",
   "remoteTools": [
     "cascrow_v3_offer",
     "cascrow_v3_acceptance_get",
@@ -27,17 +27,18 @@ const V3_CLIENT_TEXT = {
     "cascrow_v3_claims"
   ],
   "codeHints": {
-    "V3_DISABLED": "MilestoneEscrowV3 is switched off for NEW money right now (offers, acceptances, funding). An escrow that already exists is never locked: object, release, refund, claim and withdraw keep working (cascrow_v3_prepare, or npx cascrow-signer@0.1.0 without cascrow at all).",
+    "V3_DISABLED": "MilestoneEscrowV3 is switched off for NEW money right now (offers, acceptances, funding). An escrow that already exists is never locked: object, release, refund, claim and withdraw keep working (cascrow_v3_prepare, or npx cascrow-signer@0.2.0 without cascrow at all).",
     "RATE_UNAVAILABLE": "cascrow could not get a consistent XRP/USD rate from its two sources, so no offer can be priced. Nothing was created; retry in a minute.",
+    "SCREENING_UNAVAILABLE": "cascrow could not complete the sanctions screening this new-escrow step needs (offer, acceptance or funding), so nothing was created or prepared. This is a condition on cascrow's side, not a finding about you or your counterparty — retry in a few minutes. It does not touch escrows that already exist: their actions keep working (cascrow_v3_prepare, or npx cascrow-signer@0.2.0).",
     "V3_NOT_OFFERED": "The payer has not offered MilestoneEscrowV3 terms for this milestone yet — only the payer can (cascrow_v3_offer). The payer has been notified.",
     "OFFER_EXISTS": "An open offer already exists for this milestone and stays valid until it expires. Wait for the payee's acceptance or for the offer to lapse; sending the same inputs again returns the same offer.",
-    "V3_OFFER_OPEN": "An open MilestoneEscrowV3 offer, or a signed acceptance that is not funded yet, is bound to this milestone or wallet, so it cannot change now. Wait until the payer funds the escrow from their own machine (npx cascrow-signer@0.1.0 fund --milestone <milestoneId>) or the offer or acceptance lapses.",
+    "V3_OFFER_OPEN": "An open MilestoneEscrowV3 offer, or a signed acceptance that is not funded yet, is bound to this milestone or wallet, so it cannot change now. Wait until the payer funds the escrow from their own machine (npx cascrow-signer@0.2.0 fund --milestone <milestoneId>) or the offer or acceptance lapses.",
     "ATTESTATION_PENDING": "The AI panel has not finished on this claim. Its result is a non-binding recommendation — as payer you can object NOW, before the objection deadline, without waiting for it.",
     "CLAIM_PROOF_UNKNOWN": "This claim's proofHash matches no evidence submitted to cascrow, so there is no AI recommendation for it. As payer, judge the delivery yourself and object before the objection deadline if it is not what was agreed.",
-    "V3_ESCROW": "This milestone is held in a MilestoneEscrowV3 escrow: only its payer, payee or arbiter moves that money, on chain, with their own key. Get the unsigned transaction with cascrow_v3_prepare, or sign locally with npx cascrow-signer@0.1.0.",
+    "V3_ESCROW": "This milestone is held in a MilestoneEscrowV3 escrow: only its payer, payee or arbiter moves that money, on chain, with their own key. Get the unsigned transaction with cascrow_v3_prepare, or sign locally with npx cascrow-signer@0.2.0.",
     "V2_ESCROW_PRESENT": "This milestone or its contract still carries data of the retired v2 (RLUSD) escrow, so it cannot become a MilestoneEscrowV3 escrow. Nothing was changed; contact support.",
-    "INVALID_SIGNATURE": "The acceptance signature does not verify for your linked wallet over these exact terms (EIP-712, low-s, from an ordinary account). Sign the terms returned by cascrow_v3_acceptance_get again — npx cascrow-signer@0.1.0 accept does it and checks them first.",
-    "V3_INDEX_STALE": "cascrow's index of the chain is behind. Read the escrow from the chain directly (npx cascrow-signer@0.1.0 claims, or getEscrow / ClaimSubmitted); every deadline, above all an objection window, runs on chain regardless.",
+    "INVALID_SIGNATURE": "The acceptance signature does not verify for your linked wallet over these exact terms (EIP-712, low-s, from an ordinary account). Sign the terms returned by cascrow_v3_acceptance_get again — npx cascrow-signer@0.2.0 accept does it and checks them first.",
+    "V3_INDEX_STALE": "cascrow's index of the chain is behind. Read the escrow from the chain directly (npx cascrow-signer@0.2.0 claims, or getEscrow / ClaimSubmitted); every deadline, above all an objection window, runs on chain regardless.",
     "ACCEPTANCE_LAPSED": "The acceptance expired without funding, so the milestone is closed — this is not a failure of either party. A new attempt is a new milestone.",
     "NOT_COMPLETABLE_WITHOUT_ESCROW": "The work was approved, but this milestone carries an amount without a MilestoneEscrowV3 escrow, and the previous escrow system has been removed — nothing can complete or pay it, so it was left as it was and NO money moved. cascrow has opened a case for it; contact support@cascrow.com with the contract ID. Do not resubmit: your evidence is recorded.",
     "RELEASE_HOLD_REMOVED": "releaseHoldHours was removed with the previous escrow system; send the contract without it. A MilestoneEscrowV3 escrow's review period is agreed in the payer's offer (cascrow_v3_offer), and a $0 verification contract has no payout to delay.",
@@ -47,14 +48,15 @@ const V3_CLIENT_TEXT = {
   },
   "joined": {
     "active": "Joined as Builder. This is a $0 verification contract, so it is active now — submit proof for a milestone (cascrow_submit_proof). No money is held or moved.",
-    "awaitingOffer": "Joined as Builder. The milestones carry an amount, so nothing is funded yet: wait for the payer's MilestoneEscrowV3 offer, then accept it with your own wallet key — npx cascrow-signer@0.1.0 accept --milestone <milestoneId>, or on the contract page. cascrow never signs for you. Submit proof once the payer has funded the milestone.",
+    "awaitingOffer": "Joined as Builder. The milestones carry an amount, so nothing is funded yet: wait for the payer's MilestoneEscrowV3 offer, then accept it with your own wallet key — npx cascrow-signer@0.2.0 accept --milestone <milestoneId>, or on the contract page. cascrow never signs for you. Submit proof once the payer has funded the milestone.",
     "unknown": "Joined as Builder. The server did not say whether the contract is active — check it with cascrow_get_contract before submitting proof."
   },
   "payeeHints": {
-    "CLAIM_PROOF_UNKNOWN": "This manifest is not a sealed submission of this milestone, so cascrow will not confirm it and nothing was signed. As payee, claim with the manifestHash the evidence door returned (the upload's answer, or cascrow_get_proof_status): npx cascrow-signer@0.1.0 submit-claim --milestone <milestoneId> --proof-hash <manifestHash>."
+    "CLAIM_PROOF_UNKNOWN": "This manifest is not a sealed submission of this milestone, so cascrow will not confirm it and nothing was signed. As payee, claim with the manifestHash the evidence door returned (the upload's answer, or cascrow_get_proof_status): npx cascrow-signer@0.2.0 submit-claim --milestone <milestoneId> --proof-hash <manifestHash>."
   },
-  "fundRemoved": "cascrow_fund_milestone was removed (and with it fundMilestone in cascrow-sdk and `cascrow fund`). A $0 verification contract is active by itself once the builder has joined — there is nothing to fund. A milestone with an amount is a MilestoneEscrowV3 escrow in native XRP: the payer offers terms (cascrow_v3_offer), the builder accepts with their own key, and the payer funds it with one transaction from their own machine — npx cascrow-signer@0.1.0 fund --milestone <milestoneId>. cascrow never signs or sends for you.",
-  "recommendation": "🧭 AI RECOMMENDATION {verdict} for this MilestoneEscrowV3 submission ({confidence}% confidence on this file) — this verdict moves NO money. The submission is YES only when every file in it has a definite AI yes; only then is it claim-ready. As payee: claim on chain with the submission's manifestHash (npx cascrow-signer@0.1.0 submit-claim --milestone <milestoneId> --proof-hash <manifestHash>). As payer: release, or object before the objection deadline.",
+  "fundRemoved": "cascrow_fund_milestone was removed (and with it fundMilestone in cascrow-sdk and `cascrow fund`). A $0 verification contract is active by itself once the builder has joined — there is nothing to fund. A milestone with an amount is a MilestoneEscrowV3 escrow in native XRP: the payer offers terms (cascrow_v3_offer), the builder accepts with their own key, and the payer funds it with one transaction from their own machine — npx cascrow-signer@0.2.0 fund --milestone <milestoneId>. cascrow never signs or sends for you.",
+  "recommendation": "🧭 AI RECOMMENDATION {verdict} for this MilestoneEscrowV3 submission ({confidence}% confidence on this file) — this verdict moves NO money. The submission is YES only when every file in it has a definite AI yes; only then is it claim-ready. As payee: claim on chain with the submission's manifestHash (npx cascrow-signer@0.2.0 submit-claim --milestone <milestoneId> --proof-hash <manifestHash>). As payer: release, or object before the objection deadline.",
+  "noArbiterVeto": "No arbiter is named. The payer can object to every claim at no cost, and after the deadline an objected claim ends in a refund to the payer. This escrow protects you only against an inactive payer, not a dishonest one.",
   "reportTxOnlyHash": "cascrow_v3_report_tx takes a transaction HASH (0x + 64 hex characters) and nothing else. cascrow never accepts a signed transaction — broadcast it yourself to the chain's public RPC."
 };
 // END v3-client-text
@@ -175,7 +177,7 @@ async function fetchJson(method, path, { json, form, key = API_KEY, deadlineMs =
           (v3RefusalDetail(data) ? ` — ${v3RefusalDetail(data)}` : "") +
           (v3HintFor(code, data) ? `\n\n${v3HintFor(code, data)}` : "")
       ),
-      { status: res.status, code, retryAfterSeconds }
+      { status: res.status, code, retryAfterSeconds, body: data }
     );
   }
   return data;
@@ -552,9 +554,10 @@ Commands:
   check-invites Check pending contract invites for this agent
   review-queue  As funder: list milestones still waiting for your verdict
   review        As funder: approve or reject a milestone under manual review
+  human-review  As funder or builder: ask a person at cascrow to review a verification outcome (Art. 22(3) GDPR), or --list the requests
   v3-claims     As payer: list MilestoneEscrowV3 claims you can still object to on chain
   v3 <sub>      MilestoneEscrowV3, remote half: offer | acceptance | accept-submit | prepare | report-tx | attestation | claims
-                and "v3 sign <cascrow-signer command…>" — runs the pinned local signer (npx cascrow-signer@0.1.0),
+                and "v3 sign <cascrow-signer command…>" — runs the pinned local signer (npx cascrow-signer@0.2.0),
                 which holds your key on YOUR machine. cascrow never signs, sends or relays for you.
   me            Print this agent's ID
 
@@ -589,6 +592,11 @@ Options for each command:
     --criteria-file <path>  optional  the same, read from a file
     --checklist-file <path> optional  JSON array of { title, severity?, id? } (max 20) scored item by item on text proofs
     --review-mode <mode>    optional  AUTO | MANUAL | MANUAL_AUTO — what happens when the panel is unsure (60–85%)
+    --review-days <n>       optional  your review window, 2–30 days (default 14; under 7 only if both parties
+                                      registered as businesses). Without your decision a milestone completes
+                                      only if the panel's own verdict was YES; otherwise cascrow's human review decides
+    --panel-alone           optional  the panel decides alone: YES above 85 % completes, anything else is a
+                                      rejection the builder can resubmit against — you do not review
 
   submit  [or use verify for text proof in one call]
     --milestone <id>        required
@@ -645,13 +653,18 @@ Examples:
 
   # As the funder: decide what the AI panel could not (confidence 60-85)
   # Poll this — a manual_review.required webhook you missed is a decision nobody
-  # makes; an undecided milestone completes automatically after 48h under review mode
-  # MANUAL_AUTO or AUTO, 14 days otherwise.
+  # makes; an undecided milestone completes automatically when its review window
+  # closes only when the panel's own YES opened the review and the contract's terms let
+  # silence count. Any other review goes to cascrow's human review.
   # Verification-only contracts: a verdict completes or hands back, and moves no money.
   cascrow review-queue
   cascrow review --contract <contractId> --decision APPROVE
   cascrow review --contract <contractId> --decision REJECT --milestone <milestoneId>
 
+  # Either party: a person at cascrow reviews a verification outcome (decided within a month)
+  cascrow human-review --contract <contractId> [--milestone <milestoneId>] [--reason "why"]
+  cascrow human-review --contract <contractId> --list
+
   # As the payer of a MilestoneEscrowV3 escrow: claims release unless YOUR wallet
   # calls object(escrowId) before the deadline — cascrow cannot object for you.
   cascrow v3-claims
@@ -790,7 +803,7 @@ async function cmdVerifyWork(args) {
     }
   }
 
-  process.stderr.write("\nVerifying with 5 independent AI models (no escrow, no account needed)...\n\n");
+  process.stderr.write("\nVerifying with 5 AI models run by 5 different providers (no escrow, no account needed)...\n\n");
 
   let data;
   if (args.image) {
@@ -1060,6 +1073,10 @@ async function cmdCreate(args) {
   if (reviewMode !== undefined && !["AUTO", "MANUAL", "MANUAL_AUTO"].includes(reviewMode)) {
     err("--review-mode must be AUTO, MANUAL or MANUAL_AUTO");
   }
+  // The range is the server's (review-terms.ts); only a non-number is refused here.
+  const reviewDays = args["review-days"] !== undefined ? Number(args["review-days"]) : undefined;
+  if (reviewDays !== undefined && !Number.isInteger(reviewDays)) err("--review-days must be a whole number of days");
+  const panelAlone = args["panel-alone"] === true || args["panel-alone"] === "true" ? true : undefined;
   let criteria, checklist;
   try {
     criteria = normalizeCriteria(criteriaRaw);
@@ -1077,6 +1094,8 @@ async function cmdCreate(args) {
       ...(checklist !== undefined ? { verificationChecklist: checklist } : {}),
     }],
     ...(reviewMode !== undefined ? { agentReviewMode: reviewMode } : {}),
+    ...(reviewDays !== undefined ? { reviewWindowDays: reviewDays } : {}),
+    ...(panelAlone !== undefined ? { panelDecidesAlone: panelAlone } : {}),
   });
 
   const contractUrl = `${BASE_URL}/contract/${data.contractId}`;
@@ -1102,8 +1121,8 @@ function cmdEscrowFundRemoved() {
     "escrow-fund was removed in cascrow-cli 2.0.0: cascrow never accepts, creates, stores or signs with private keys. " +
       "A $0 verification contract needs no funding — it is active once the builder has joined. A milestone with an amount " +
       "is a MilestoneEscrowV3 escrow in native XRP, funded by the payer with one transaction from their own machine: first link " +
-      "the wallet you will fund from (GET /api/user/wallet/challenge, sign the message, POST /api/user/wallet), then run " +
-      "npx cascrow-signer@0.1.0 fund --milestone <milestoneId>. If you ever passed a private key to this command (it is also in your shell history), " +
+      "the wallet you will fund from (GET /api/user/wallet/challenge?address=<your wallet>, sign the message with that wallet, POST /api/user/wallet), then run " +
+      "npx cascrow-signer@0.2.0 fund --milestone <milestoneId>. If you ever passed a private key to this command (it is also in your shell history), " +
       "treat that key as exposed and move its funds to a new wallet. [CUSTODY_PATH_REMOVED]"
   );
 }
@@ -1337,6 +1356,42 @@ async function cmdReview(args) {
   process.stderr.write(`\nMilestone ${what}.${data.status ? ` Contract status: ${data.status}.` : ""}\n\n`);
 }
 
+/**
+ * `cascrow human-review` — the request (POST /api/human-review) or, with --list, the
+ * requests on a contract with their decisions (vp1-5, 2026-10-20). A request already
+ * open on that milestone is not an error: it prints the deadline and exits 0.
+ */
+async function cmdHumanReview(args) {
+  if (!API_KEY) err("CASCROW_API_KEY is not set");
+  const contractId = args.contract;
+  if (!contractId) err("--contract <id> is required");
+  if (args.list) {
+    const data = await apiGet(`/api/human-review?contractId=${encodeURIComponent(contractId)}`);
+    print(data);
+    const requests = Array.isArray(data.requests) ? data.requests : [];
+    process.stderr.write(
+      requests.length === 0
+        ? "\nNo human-review requests on this contract.\n\n"
+        : `\n${requests.map((r) => `  ${r.id} [${r.status}] ${r.outcome ? `outcome ${r.outcome}` : `decision due by ${r.dueAt}`}`).join("\n")}\n\n`
+    );
+    return;
+  }
+  const body = { contractId, ...(args.milestone ? { milestoneId: args.milestone } : {}), ...(typeof args.reason === "string" && args.reason ? { reason: args.reason } : {}) };
+  try {
+    const data = await apiPost("/api/human-review", body);
+    print(data);
+    process.stderr.write(`\nHuman review requested (${data.requestId}). A person at cascrow decides by ${data.dueAt}; both parties receive the decision with its reasons.\n\n`);
+  } catch (e) {
+    if (e && e.code === "HUMAN_REVIEW_ALREADY_OPEN") {
+      const dueAt = e.body && typeof e.body.dueAt === "string" ? e.body.dueAt : null;
+      print({ status: "ALREADY_OPEN", dueAt });
+      process.stderr.write(`\nA human review of this milestone is already open${dueAt ? `; a person at cascrow decides by ${dueAt}` : ""}. No need to ask again.\n\n`);
+      return;
+    }
+    throw e;
+  }
+}
+
 async function cmdMe() {
   if (!API_KEY) err("CASCROW_API_KEY is not set");
   const data = await apiGet("/api/agent/me");
@@ -1369,6 +1424,7 @@ try {
     case "check-invites": await cmdCheckInvites();      break;
     case "review-queue":  await cmdReviewQueue();       break;
     case "review":        await cmdReview(args);        break;
+    case "human-review":  await cmdHumanReview(args);   break;
     case "v3-claims":     await cmdV3Claims();          break;
     case "v3":            await cmdV3(rest[0], parseArgs(rest.slice(1)), rest.slice(1)); break;
     case "me":            await cmdMe();                break;

package/package.json

@@ -1,9 +1,15 @@
 {
   "name": "cascrow-cli",
-  "version": "3.0.0",
+  "version": "3.1.0",
   "description": "CLI for Cascrow — trust infrastructure for the agent economy: AI verification, on-chain reputation, and non-custodial milestone escrow (MilestoneEscrowV3, native XRP)",
   "type": "module",
   "main": "index.js",
+  "files": [
+    "index.js",
+    "README.md",
+    "CHANGELOG.md",
+    "LICENSE"
+  ],
   "bin": {
     "cascrow": "index.js"
   },

package/builder-agent.js

@@ -1,453 +0,0 @@
-#!/usr/bin/env node
-/**
- * Cascrow Builder Agent
- * Polls for pending contract invites, then automatically:
- * joins → waits until the milestone is active → submits proof → triggers AI verification
- */
-
-const BASE_URL = process.env.CASCROW_BASE_URL ?? "https://cascrow.com";
-const API_KEY  = process.env.CASCROW_API_KEY ?? "";
-const AGENT_EVM_WALLET = process.env.AGENT_EVM_WALLET ?? "";
-const POLL_INTERVAL_MS = 3000;
-
-if (!API_KEY) {
-  console.error("ERROR: CASCROW_API_KEY is not set");
-  process.exit(1);
-}
-
-// Every call reads the body as text and parses it in a try (an HTML 502 used to
-// crash the agent as "Unexpected token '<'"), carries a deadline over the body
-// read, and throws an Error with `status` and `code` (T11-A4). Upload's deadline
-// mirrors UPLOAD_CLIENT_ABORT_MS in src/lib/latency-budget.ts.
-const UPLOAD_CLIENT_ABORT_MS = 120_000;
-const REQUEST_CLIENT_ABORT_MS = 300_000;
-
-async function readJsonSafe(res) {
-  const text = await res.text();
-  if (!text) return {};
-  try {
-    return JSON.parse(text);
-  } catch {
-    return { error: `HTTP ${res.status} (non-JSON response from server)`, code: "UPSTREAM_NON_JSON" };
-  }
-}
-
-async function fetchJson(method, path, { json, form, deadlineMs = REQUEST_CLIENT_ABORT_MS } = {}) {
-  const controller = new AbortController();
-  const timer = setTimeout(() => controller.abort(), deadlineMs);
-  let res;
-  let data;
-  try {
-    res = await fetch(`${BASE_URL}${path}`, {
-      method,
-      headers: { "Authorization": `Bearer ${API_KEY}`, ...(json !== undefined ? { "Content-Type": "application/json" } : {}) },
-      ...(json !== undefined ? { body: JSON.stringify(json) } : form !== undefined ? { body: form } : {}),
-      signal: controller.signal,
-    });
-    data = await readJsonSafe(res);
-  } catch (e) {
-    if (e && e.name === "AbortError") {
-      throw Object.assign(new Error(`No answer from ${path} within ${Math.round(deadlineMs / 1000)} s [CLIENT_TIMEOUT]`), { status: 0, code: "CLIENT_TIMEOUT" });
-    }
-    throw e;
-  } finally {
-    clearTimeout(timer);
-  }
-  if (!res.ok || data.code === "UPSTREAM_NON_JSON") {
-    const code = typeof data.code === "string" ? data.code : null;
-    throw Object.assign(new Error(`${data.error ?? `HTTP ${res.status}`}${code ? ` [${code}]` : ""}`), { status: res.status, code });
-  }
-  return data;
-}
-
-async function apiPost(path, body) {
-  return fetchJson("POST", path, { json: body });
-}
-
-async function apiGet(path) {
-  return fetchJson("GET", path);
-}
-
-async function uploadProof(milestoneId, content) {
-  const blob = new Blob([content], { type: "text/plain" });
-  const form = new FormData();
-  form.append("file", blob, "proof-report.txt");
-  form.append("milestoneId", milestoneId);
-  return fetchJson("POST", "/api/proof/upload", { form, deadlineMs: UPLOAD_CLIENT_ABORT_MS });
-}
-
-// SEC-073. The FIFTH client door of `/api/verify`, and until 2026-09-22 the only
-// one with no deadline at all: it was invisible to `latency-budget.test.ts`,
-// whose client list was three hand-typed files — and this file lives inside one
-// of the three packages already on that list, so the subject was PACKAGES where
-// the population is FILES (F-30).
-//
-// 235_000 — one step below the route's 240 s `maxDuration`, NOT "above the
-// worst case": the tail (pre-stream + a 15 s blob read + the 205 s ladder + the
-// bounded EVM retry) reaches ~239 s, so no value is both above it and below the
-// cap. See VERIFY_TAIL_WORST_CASE_MS in src/lib/latency-budget.ts. Cleared after
-// the READ LOOP rather than at the `fetch`: `fetch` resolves on response headers about 12 s in, and the whole
-// retry ladder arrives afterwards out of `res.body`.
-async function streamVerify(proofId) {
-  const controller = new AbortController();
-  const timeout = setTimeout(() => controller.abort(), 235_000);
-  let res;
-  try {
-    res = await fetch(`${BASE_URL}/api/verify`, {
-      method: "POST",
-      headers: {
-        "Authorization": `Bearer ${API_KEY}`,
-        "Content-Type": "application/json",
-        "Accept": "text/event-stream",
-      },
-      body: JSON.stringify({ proofId }),
-      signal: controller.signal,
-    });
-  } catch (e) {
-    clearTimeout(timeout);
-    // SEC-073. Now that the deadline is live it can actually fire, and a raw
-    // `DOMException: This operation was aborted` names no remedy — worse, per
-    // the tail arithmetic in latency-budget.ts the abort can land AFTER the
-    // verdict was written, so "it failed" may be false.
-    if (e && e.name === "AbortError") {
-      throw new Error(
-        "Verification is still running on the server — this client stopped waiting, it did not fail. " +
-        `Poll GET /api/agent/proof-status/${proofId} for the verdict.`
-      );
-    }
-    throw e;
-  }
-  if (!res.ok) {
-    clearTimeout(timeout);
-    const data = await readJsonSafe(res);
-    // T01-8. Upload starts verification by itself, and this agent then starts it
-    // again — so losing the claim to a RUNNING run is the normal case, not a failure.
-    // The caller's polling path waits for that run; `alreadyRunning` sends it there.
-    // Never read this 409's Retry-After as a wait: it is the ~1 h takeover cutoff.
-    if (res.status === 409 && data.code === "VERIFICATION_IN_PROGRESS" && data.phase === "running") {
-      throw Object.assign(new Error("A verification of this proof is already running (the one upload started)."), { alreadyRunning: true });
-    }
-    const code = typeof data.code === "string" ? data.code : null;
-    throw Object.assign(new Error(`${data.error ?? `HTTP ${res.status}`}${code ? ` [${code}]` : ""}`), { status: res.status, code });
-  }
-  if (!res.body) {
-    clearTimeout(timeout);
-    throw new Error("Verification stream had no body");
-  }
-
-  const reader = res.body.getReader();
-  const decoder = new TextDecoder();
-  let buffer = "";
-
-  try {
-  while (true) {
-    const { done, value } = await reader.read();
-    if (done) break;
-    buffer += decoder.decode(value, { stream: true });
-    const lines = buffer.split("\n");
-    buffer = lines.pop() ?? "";
-    for (const line of lines) {
-      if (!line.startsWith("data:")) continue;
-      const raw = line.slice(5).trim();
-      if (!raw) continue;
-      try {
-        const msg = JSON.parse(raw);
-        if (msg.type === "model_vote") {
-          const icon = msg.decision === "YES" ? "✅" : "❌";
-          console.log(`  ${icon} ${msg.model}: ${msg.decision} (${msg.confidence}%)`);
-        } else if (msg.type === "complete") {
-          return msg;
-        } else if (msg.type === "error") {
-          throw new Error(msg.message);
-        }
-      } catch (e) {
-        if (e instanceof SyntaxError) continue;
-        throw e;
-      }
-    }
-  }
-  } catch (e) {
-    // The deadline can now fire DURING the read — that is the whole point of
-    // clearing it below the loop rather than at the fetch. Same translation as
-    // the fetch-side catch above.
-    if (e && e.name === "AbortError") {
-      throw new Error(
-        "Verification is still running on the server — this client stopped waiting, it did not fail. " +
-        `Poll GET /api/agent/proof-status/${proofId} for the verdict.`
-      );
-    }
-    throw e;
-  } finally {
-    clearTimeout(timeout);
-    reader.cancel().catch(() => {});
-  }
-  throw new Error("Stream ended without complete event");
-}
-
-async function handleInvite(invite) {
-  console.log(`\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━`);
-  console.log(`📨 New contract received!`);
-  console.log(`   Contract: ${invite.contractId}`);
-  if (invite.message) console.log(`   Task: ${invite.message}`);
-  console.log(`━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n`);
-
-  // 1. Join contract
-  console.log("🔗 Joining contract...");
-  const joined = await apiPost("/api/contracts/join", { inviteCode: invite.inviteCode });
-  console.log(`   ✓ Joined. Contract ID: ${joined.contractId}`);
-  // The join's own activation result: a $0 contract is active now; a money contract
-  // waits for the payer's MilestoneEscrowV3 offer, which this agent must accept with
-  // its OWN key — cascrow never signs for it.
-  if (joined.activated === true) console.log("   ✓ Verification-only contract — active now.");
-  else if (joined.activated === false)
-    console.log("   ⏳ Paid contract — waiting for the payer's MilestoneEscrowV3 offer. Accept it with your own key: npx cascrow-signer@0.1.0 accept --milestone <milestoneId>.");
-
-  // 2. Wait until the milestone is active. A verification-only ($0) contract is active
-  // as soon as the builder has joined; a paid one once the payer has funded its
-  // MilestoneEscrowV3 escrow from their own wallet. Either way the status is FUNDED.
-  console.log("⏳ Waiting for the milestone to be active...");
-  let fundedMilestoneId = null;
-  for (let i = 0; i < 40; i++) {
-    const contract = await apiGet(`/api/contracts/${joined.contractId}`);
-    const funded = (contract.milestones ?? []).find((m) => m.status === "FUNDED");
-    if (funded) {
-      fundedMilestoneId = funded.id;
-      console.log(`   ✓ Milestone active. ID: ${fundedMilestoneId}`);
-      break;
-    }
-    await new Promise((r) => setTimeout(r, 3000));
-  }
-  if (!fundedMilestoneId) throw new Error("Timed out waiting for the milestone to be active");
-
-  // 3. Do the work — generate proof based on the task message
-  console.log("🤖 Performing task...");
-  const task = invite.message ?? "Complete the assigned milestone";
-  const bio = `cascrow is trust infrastructure for the agent economy. It checks whether delivered work meets the bar that was agreed for it, and it keeps a verifiable record of the answer.
-
-Every submission is judged in parallel by five AI models from different vendors — Claude, GPT-4o, Gemini, Mistral and Cerebras — and three approvals make a YES. Each verdict is anchored on the XRP Ledger, completed milestones earn an NFT certificate, and the results build a portable on-chain reputation for the builder.
-
-For paid work, cascrow supports a non-custodial escrow in native XRP: the funds sit in a smart contract that only the two parties, or an arbiter they chose, can move. The AI verdict is a signed recommendation; cascrow never holds funds or keys.
-
-Agents use a REST API, an MCP server and a CLI to create contracts, submit proof and read reputation programmatically. Live at cascrow.com.`;
-
-  const proof = `PROOF OF COMPLETION
-═══════════════════════════════════════
-
-Task: ${task}
-Contract ID: ${invite.contractId}
-Milestone ID: ${fundedMilestoneId}
-Completed at: ${new Date().toISOString()}
-
-DELIVERABLE (${bio.split(/\s+/).filter(Boolean).length} words):
-${bio}
-
-VERIFICATION CRITERIA MET:
-✓ Professional third-person tone throughout
-✓ ${bio.split(/\s+/).filter(Boolean).length} words — within the 120–160 word range
-✓ Clearly explains what cascrow does (AI verification, on-chain reputation, non-custodial escrow)
-✓ Highlights AI verification mechanism (5-model majority vote, named models)
-✓ Addresses agent economy angle (autonomous agents, programmatic interfaces)
-✓ No placeholder text
-✓ Suitable for About page or press kit`;
-
-  console.log(`   ✓ Task complete.`);
-
-  // 4. Submit proof
-  console.log("📤 Submitting proof...");
-  const proofData = await uploadProof(fundedMilestoneId, proof);
-  console.log(`   ✓ Proof submitted. ID: ${proofData.proofId}`);
-
-  // 5. Trigger verification
-  console.log("\n🔍 Triggering AI verification (5 models)...\n");
-  let result;
-  try {
-    result = await streamVerify(proofData.proofId);
-  } catch (streamErr) {
-    // Stream disconnected before complete event (e.g. Vercel 150s timeout).
-    // The verification is still running server-side — just poll for the result,
-    // do NOT call streamVerify again (would trigger duplicate AI verification).
-    // Two ways here, and the loop below serves both: the stream dropped mid-run, or
-    // it never opened because upload's own run already held the claim (T01-8).
-    if (streamErr && streamErr.alreadyRunning) {
-      console.log(`   ℹ️  Verification was already running (upload starts it) — waiting for its result...`);
-    } else if (streamErr && (streamErr.status === 401 || streamErr.status === 403 || streamErr.status === 404)) {
-      throw streamErr;
-    } else {
-      console.log(`   ⚠️  Stream ended early, polling for result...`);
-    }
-    // SEC-076. This polled `contract.status`, and that column answers a different
-    // question than the one asked here. It is a single slot with nine writers:
-    // funding a SIBLING milestone writes `contractStatusAfterFunding(...)` over
-    // it under `status: { notIn: ["COMPLETED","EXPIRED"] }`, so it fails both
-    // ways. False negative: the pin is overwritten with FUNDED, no terminal value
-    // ever appears, and this loop dies after five minutes on "Timed out waiting
-    // for verification result" for a proof that was in fact decided. False
-    // positive: the contract reads VERIFIED/COMPLETED because ANOTHER milestone
-    // settled, and the builder is handed a verdict that is not their proof's -
-    // `decision` below is derived from it.
-    //
-    // `GET /api/contracts/{id}` returns `milestones: [{ id, status, … }]`, and we
-    // funded a specific one, so the honest read is that row. The contract-level
-    // read is kept only for the legacy population that has no milestone rows at
-    // all (proofs written via the contractId-only path).
-    //
-    // EXPIRED is terminal too. Since 2026-09-23 `/api/verify` no longer reopens a
-    // milestone that went EXPIRED while its panel ran, so without it this loop polled a
-    // closed row for five minutes and then threw "Timed out" — and it must never be
-    // mapped to a YES: the milestone moved no funds through this verification.
-    const TERMINAL_PROOF_STATES = ["VERIFIED", "COMPLETED", "REJECTED", "PENDING_REVIEW", "EXPIRED"];
-    for (let i = 0; i < 60; i++) {
-      await new Promise((r) => setTimeout(r, 5000));
-      let contract;
-      try {
-        contract = await apiGet(`/api/contracts/${joined.contractId}`);
-      } catch (e) {
-        // 401/403/404 do not change by waiting; anything else is transient. One
-        // dropped poll used to end the whole run.
-        if (e && (e.status === 401 || e.status === 403 || e.status === 404)) throw e;
-        continue;
-      }
-      const mine = (contract.milestones ?? []).find((m) => m.id === fundedMilestoneId);
-      const observed = mine ? mine.status : (contract.milestones ?? []).length === 0 ? contract.status : null;
-      if (observed && TERMINAL_PROOF_STATES.includes(observed)) {
-        if (observed === "EXPIRED") {
-          // No verdict is read on this path: the stream that carried it dropped, and
-          // the row says only that it is closed.
-          result = { decision: null, confidence: 0, action: "EXPIRED", milestoneClosed: true };
-          console.log(`   ✓ Got result via polling: ${observed}`);
-          break;
-        }
-        const decision = ["VERIFIED", "COMPLETED"].includes(observed) ? "YES" : "NO";
-        result = { decision, confidence: 0, action: observed };
-        console.log(`   ✓ Got result via polling: ${observed}`);
-        break;
-      }
-    }
-    if (!result) throw new Error("Timed out waiting for verification result");
-  }
-
-  // SEC-055/058/059. This re-implemented the three-tier rule from the PROOF's verdict
-  // (`decision === "YES" && confidence >= 85`), so `COMPLETED`, `SUPERSEDED`, a
-  // compliance block and a release hold all printed "✅ VERIFIED", and a panel outage
-  // (`decision: "PENDING"`, confidence 0) printed "❌ NOT VERIFIED — 0% confidence" —
-  // our own outage read back to the builder as a rejection of their work.
-  //
-  // `passed` now means FUNDS MOVED, and only `COMPLETED` says that. The polling
-  // fallback above already derives `action` from the funded MILESTONE's status
-  // (SEC-076; it read the contract row until 2026-09-22), so both paths reach this
-  // with the same vocabulary.
-  const released = result.action === "COMPLETED";
-  const passed = released;
-  console.log(`\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━`);
-  if (result.action === "V3_RECOMMENDATION") {
-    // MilestoneEscrowV3: a recommendation that moves nothing — asked first, so no arm
-    // below can read it as a payout or a rejection. The claim is judged by the
-    // SUBMISSION's verdict, never by `decision` (the panel on this one file).
-    const verdict = result.submissionVerdict === "YES" || result.submissionVerdict === "NO" ? result.submissionVerdict : "PENDING";
-    console.log(
-      `🧭 AI RECOMMENDATION ${verdict} on a MilestoneEscrowV3 submission — this verdict moves NO money. ` +
-        (verdict === "YES"
-          ? `Claim on chain with proofHash ${result.manifestHash ?? "(the upload's manifestHash)"} from your own key (npx cascrow-signer submit-claim).`
-          : verdict === "NO"
-            ? `Not claim-ready: the payer can object to a claim made with this evidence.`
-            : `The submission's verdict is still pending; poll the proof status.`)
-    );
-  } else if (result.milestoneClosed === true && result.action === "EXPIRED") {
-    // `GET /api/contracts/{id}` does not return the milestone's `terminalReason`, so this
-    // cannot say whether the funder was refunded or the builder was paid on-chain, and
-    // does not guess.
-    console.log(
-      `⛔ CLOSED — the milestone was closed (EXPIRED) while the panel ran or after it decided, so this verification moved no funds. ` +
-        `The reason is not available here — check the contract page before assuming where the funds are. Do not resubmit to it.`
-    );
-  } else if (result.action === "SUPERSEDED") {
-    console.log(
-      result.settledAs
-        ? `ℹ️ SUPERSEDED — this milestone was closed (${result.settledAs}) before this verification could settle it; it changed nothing and moved no funds. Do not resubmit to it.`
-        : `ℹ️ SUPERSEDED — another proof on this milestone was decided first; this changed nothing.`
-    );
-  } else if (released) {
-    console.log(
-      result.alreadyReleased === true
-        ? `✅ COMPLETED — another request completed this milestone first; no money was held (verification-only contract). Do not resubmit.`
-        : `✅ COMPLETED — ${result.confidence}% confidence; no money was held (verification-only contract).`
-    );
-  } else if (result.complianceBlocked === true) {
-    console.log(`⏸️ VERIFIED — payout on hold pending compliance review. No funds moved.`);
-  } else if (result.action === "NOT_COMPLETABLE_WITHOUT_ESCROW") {
-    // Approved, but the milestone carries an amount without a MilestoneEscrowV3 escrow,
-    // so nothing completed it. Do not resubmit: the next verdict meets the same row.
-    console.log(`⛔ NOT COMPLETED — ${result.remedy ?? "contact support@cascrow.com; do not resubmit."} ${result.error ?? ""}`.trim());
-  } else if (result.action === "VERIFIED") {
-    console.log(`⚠️ VERIFIED — approved, but the milestone was NOT completed. No money moved; if it stays VERIFIED, contact support@cascrow.com.`);
-  } else if (result.timedOut === true) {
-    console.log(`⏳ PENDING_REVIEW — the panel did not answer (too few models). NOT a rejection; a human decides.`);
-  } else if (result.action === "PENDING_REVIEW") {
-    console.log(`⏳ PENDING_REVIEW — ${result.confidence}% confidence, manual review required.`);
-  } else if (result.action === "REJECTED") {
-    console.log(`❌ REJECTED — ${result.confidence}% confidence.`);
-  } else {
-    console.log(`⚠️ Outcome not recognised by this version (action: ${result.action}). No conclusion drawn.`);
-  }
-  console.log(`   Decision: ${result.decision ?? "none read (the stream dropped before it)"}`);
-  console.log(`   View contract: ${BASE_URL}/contract/${invite.contractId}`);
-  console.log(`━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n`);
-}
-
-async function getAgentId() {
-  const data = await apiGet("/api/agent/me");
-  return data.agentId;
-}
-
-async function main() {
-  const agentId = await getAgentId();
-  console.log(`\n🤖 Cascrow Builder Agent started`);
-  console.log(`   Agent ID: ${agentId}`);
-  console.log(`   Share this ID with the Requester agent`);
-  console.log(`   Polling for work every ${POLL_INTERVAL_MS / 1000}s...\n`);
-
-  // Register EVM wallet address so Requester can fund real escrow to this agent.
-  //
-  // POST /api/user/wallet proves key possession: it wants a challenge token from
-  // GET /api/user/wallet/challenge plus a signature over the nonce it carries.
-  // This CLI is deliberately dependency-free and Node's crypto cannot produce an
-  // EIP-191 signature (no keccak256, no recovery id), so it cannot complete that
-  // flow on its own — and posting the address alone has been answered with 400
-  // since the check went in. Say so plainly instead of warning past it: a
-  // builder whose wallet is not linked is not discoverable and cannot be paid,
-  // which is worth more than one line of yellow text.
-  if (AGENT_EVM_WALLET) {
-    try {
-      await apiPost("/api/user/wallet", { walletAddress: AGENT_EVM_WALLET });
-      console.log(`   💳 EVM wallet registered: ${AGENT_EVM_WALLET}\n`);
-    } catch (e) {
-      console.warn(
-        `   ⚠️  Wallet NOT linked (${e.message}).\n` +
-          `      ${AGENT_EVM_WALLET} is unusable until it is: escrow cannot be funded to it\n` +
-          `      and this agent will not appear in /api/agent/discover.\n` +
-          `      Link it once, from a signer that holds the key:\n` +
-          `        1. GET  ${BASE_URL}/api/user/wallet/challenge   (Bearer <your API key>)\n` +
-          `        2. sign the nonce in the returned token with the wallet's key\n` +
-          `        3. POST ${BASE_URL}/api/user/wallet { walletAddress, signature, token }\n`
-      );
-    }
-  }
-
-  while (true) {
-    try {
-      const data = await apiGet("/api/agent/pending-invites");
-      const invites = data.invites ?? [];
-      for (const invite of invites) {
-        await handleInvite(invite);
-      }
-    } catch (err) {
-      console.error(`[poll error] ${err.message}`);
-    }
-    await new Promise((r) => setTimeout(r, POLL_INTERVAL_MS));
-  }
-}
-
-main().catch((err) => {
-  console.error("Fatal:", err.message);
-  process.exit(1);
-});