@weaveprotocol/cli 0.2.0 → 0.2.2

package/README.md

@@ -30,7 +30,7 @@ To have `weave` everywhere:
 npm install -g @weaveprotocol/cli            # or run it without installing: npx @weaveprotocol/cli <command>
 ```
 
-From this repo: `npm install` at the repo root (the CLI is a workspace), then `cd cli && npm run bundle && npm link`, or a
+From this repo: `npm install` at the repo root (the CLI is a workspace), then `cd packages/cli && npm run bundle && npm link`, or a
 binary with no Node at all: `bun build.ts --native`.
 
 ```bash
@@ -215,3 +215,20 @@ space anywhere leaves it everywhere.
 
 - **WebRTC on the node.** Browsers reach it over WebSocket. `node-datachannel`
   plugs into the same transport seam if measurement says it is needed.
+- **Publishing.** `weave-protocol-cli` on npm (or a built JS package), and
+  trying the Bun binary with `node-datachannel`.
+- **Hosting, before it's offered to anyone.**
+  - A load test with 1,000 spaces, with metrics. Check the pricing against those numbers, and decide on TURN from them.
+  - A real Stripe test-mode run end to end, and a decision on Stripe Tax or a merchant of record.
+  - A breach plan.
+- **The pay page.**
+  - A real Base Sepolia wallet payment.
+  - A Lightning route (BTCPay), and gasless USDC (EIP-3009).
+  - An optional email for reminders: SMTP, with double opt-in.
+- **TURN.** Run coturn with `use-auth-secret` and quotas, and set
+  `TURN_SECRET` and `TURN_URLS` on the relay and the node. Then test calls
+  across real networks, behind a strict NAT, in Safari, and on a phone
+  switching apps.
+
+What the protocol still has planned is in [the spec](../../spec/README.md),
+under **Planned** in each part.