@heyanon-arp/cli 0.0.14 → 0.0.16

package/README.md

@@ -200,15 +200,19 @@ RPC URL and the server's deploy cluster MUST agree, otherwise
 `create_lock` tx.
 
 When a delegation's `settlement = escrow` is offered:
-1. The buyer builds an on-chain lock for the agreed amount using
+1. The buyer builds + signs an on-chain lock for the agreed amount with
    `heyarp wallet create-lock` (the CLI auto-discovers the program id
-   from the server).
-2. The lock is attached to the delegation offer.
-3. After the payee responds + buyer co-signs the receipt, the server's
-   relayer submits `release_lock` (or `partial_release` / `refund_lock`)
-   on chain.
+   from the server), then funds it after the worker accepts via
+   `heyarp delegation fund`.
+2. The worker accepts the lock on-chain (`heyarp escrow accept`,
+   staking the worker stake) and marks delivery with
+   `heyarp escrow submit-work`.
+3. The buyer approves payment by sending `claim_work_payment` on chain
+   (`heyarp escrow claim`); the payee is paid in full minus the
+   protocol fee. Refunds go through `cancel_lock` (before accept) or
+   `claim_expired_work` (work window lapsed).
 4. `heyarp wallet verify-release --json` confirms the on-chain state
-   (`released_clean`, `released_partial`, or `released_refunded`).
+   (`released: true`, `status: paid`).
 
 ## Compatibility
 

package/bin/heyarp.cjs

@@ -0,0 +1,47 @@
+#!/usr/bin/env node
+'use strict';
+
+/*
+ * heyarp launcher shim.
+ *
+ * Its ONLY job is to gate on the Node.js version BEFORE requiring the real
+ * bundle (dist/cli.js). The bundle is built for modern Node (tsup target
+ * node22) and uses ES2020 syntax such as optional chaining; on an old Node
+ * that syntax throws a cryptic `SyntaxError: Unexpected token .` at PARSE
+ * time — before any in-bundle version check could ever run. A user whose
+ * `#!/usr/bin/env node` resolves to a stale Node on their PATH (a common
+ * macOS footgun: an old /usr/local/bin/node shadowing a newer
+ * /opt/homebrew/bin/node) would otherwise see that opaque error instead of
+ * a clear "upgrade Node" message.
+ *
+ * Therefore this file is INTENTIONALLY written in pre-ES2020 style so it
+ * parses on any realistic Node and can print a helpful diagnostic. Do NOT
+ * introduce optional chaining (`?.`), nullish coalescing (`??`), or other
+ * ES2020+ syntax here — that would defeat the entire purpose. (It also
+ * means the `engines.node` minimum is read defensively without `?.`.)
+ */
+
+const pkg = require('../package.json');
+const engines = pkg.engines || {};
+const declared = typeof engines.node === 'string' ? engines.node : '>=22';
+const declaredMatch = declared.match(/\d+/);
+const required = declaredMatch ? parseInt(declaredMatch[0], 10) : 22;
+
+const current = String(process.versions.node);
+const currentMajor = parseInt(current.split('.')[0], 10);
+
+if (Number.isNaN(currentMajor) || currentMajor < required) {
+	process.stderr.write(
+		`\n  heyarp requires Node.js >= ${required}, but this process is Node ${current}.\n\n` +
+			`  The \`node\` resolved by the shebang is:\n    ${process.execPath}\n\n` +
+			`  A stale Node earlier on your PATH is the usual cause (e.g. an old\n` +
+			`  /usr/local/bin/node shadowing a newer one). Fix it with one of:\n` +
+			`    - nvm install ${required} && nvm alias default ${required}\n` +
+			`    - put your Node >= ${required} directory first on $PATH\n` +
+			`    - reinstall heyarp under a modern Node\n\n` +
+			`  Tip: \`which -a node\` lists every node on your PATH.\n\n`,
+	);
+	process.exit(1);
+}
+
+require('../dist/cli.js');