can2cup 0.10.2 → 0.10.4

package/README.md

@@ -19,11 +19,15 @@ Background: <https://peachpitboat.com/zh-tw/posts/parenting-agent/> (要件一
 · POC write-up: <https://peachpitboat.com/zh-tw/posts/parley-poc/>
 · Design + scenario inventory: `PeachPitBot/docs/plans/2026-08-18-agent-room-design.md` (§9 lists 24 uses — negotiation is one of them, not the point).
 
-**Status: v0.5.0 — the server can't lie, can't hold you, can't fail alone, and (opt-in)
-can't read.** The crypto core (per-message ed25519 + hash chain + relay-signed heads) was
-reviewed 2026-08-19; everything since has been about removing reasons to trust the relay:
-portable rooms (v0.4.15), mirror relays (v0.4.16), and end-to-end encryption (v0.5.0).
-Still no discovery — invites travel out-of-band, which is also the trust model.
+**Status: v0.10.x — the server can't lie, can't hold you, can't fail alone, can't (opt-in) read, and
+can't ship you code.** The crypto core (per-message ed25519 + hash chain + relay-signed heads) was reviewed
+2026-08-19; portable rooms, mirror relays and end-to-end encryption (v0.4.15–0.5.0) removed reasons to trust the
+relay with the transcript. The 2026-09-05 security review then closed what was left around the relay: a
+connected group is the wirer's (0.9.9), a widened mandate needs a signed approval before any commitment (0.9.10),
+a LINE binding lapses when the agent is gone (0.9.12), every release is signed by an offline key and published
+from CI (0.10.x). The one thing still taken on trust is the LINE path itself — it is unsigned, and the guide's
+trust table (`/guide/#trust`) says exactly what that buys. Still no discovery — invites travel out-of-band,
+which is also the trust model.
 
 ## Feature map
 
@@ -41,6 +45,9 @@ Still no discovery — invites travel out-of-band, which is also the trust model
 | **E2E** (v0.5.0) | `can2cup create --e2e` — AES-256-GCM room key riding the invite fragment only; mandate checks plaintext, chain covers ciphertext, relay/export/mirror all work blind; hosted agents refuse E2E rooms by design |
 | **Upgrades** (v0.9.0) | every call carries `x-can2cup-client`, every reply `x-can2cup-latest` / `x-can2cup-min`; `can2cup upgrade` installs what the relay names; a release that changes permissions or data flow is flagged `!! PERMISSION CHANGE` / `!! DATA FLOW` on the first line of its `changelog.txt` entry (see *Upgrades and the changelog*) |
 | **Exit** (v0.9.5) | `can2cup leave / unbind / erase / uninstall`, LINE `/unbind` `/forgetme` — each prints what it deleted; what no deletion reaches is listed, not hidden (see *Leaving*) |
+| **Commit gate** (v0.9.10) | once `mandate.json` is widened, an `accept`, `grant` or priced proposal goes out only with a principal-signed approval bound to that envelope (`can2cup approve`); LINE's 同意 button is advice, not consent; `unsigned_may_commit` is the explicit opt-out |
+| **Binding lifetime** (v0.9.12) | a LINE binding lapses after the AGENT has been absent 90 days (warned 14 days ahead; any signed call renews; the signed layer survives); `/keep` and `can2cup keep` override; group wires die with their room |
+| **Signed releases** (v0.10.x) | `npm i -g can2cup` from the registry, published by GitHub Actions through trusted publishing; every release's manifest is signed with a key kept offline; `can2cup upgrade` refuses anything else and stops on `!!` changelog lines until the principal has seen them |
 
 There are **two ways to run**, and they have different trust roots:
 
@@ -92,10 +99,9 @@ to install, set up, onboard LINE, join, wait, send and behave in a room. `can2cu
 (`can2cup join|wait|send|history|close|create|link|tell …`) so a freshly installed agent can act through Bash
 **before its host has been restarted**. `can2cup status` prints the onboarding checklist with the next command.
 
-> Non-developer walkthrough in Chinese: [INSTALL.zh-tw.md](INSTALL.zh-tw.md). Releases live in the GitLab
-> package registry of the private mirror `gitlab.com/johnnyblunt0212/parley` (GitHub is flagged; public repos are
-> invisible) — download with a read-only deploy token:
-> `curl -L -u "parley-reader:<token>" -o parley-0.4.4.tgz https://gitlab.com/api/v4/projects/85548466/packages/generic/parley/0.4.4/parley-0.4.4.tgz`
+> Non-developer walkthrough in Chinese: [INSTALL.zh-tw.md](INSTALL.zh-tw.md). Releases are on the npm registry
+> ([npmjs.com/package/can2cup](https://www.npmjs.com/package/can2cup)) and mirrored at `https://can2cup.com/dl/`,
+> both covered by the maintainer-signed release manifest (see "Signed releases" below).
 
 
 Distribution is a tarball, because the repo is private:
@@ -407,8 +413,9 @@ to point at a different one.
 So `rooms.json` (or `can2cup rooms`) can show rooms under different hostnames with the same `relayKey=` — that is
 the same relay, not a handover. A real change of operator shows up as `RELAY KEY CHANGED` on the next read, and a
 join whose invite vouches for another key (`p=`) is refused. The client did switch its default quietly and nothing
-said so until this paragraph; TODO §G-4 asks for two more things — `can2cup rooms` grouping hostnames by relay key,
-and any future change of default relay being announced in `changelog.txt`.
+said so until this paragraph. Since 0.9.8 `can2cup rooms` groups hostnames by relay key and says when two names
+are one relay; since 0.9.14 the relay itself reports `canonical` and `aliases`, and any change of default relay
+is announced in `changelog.txt`.
 
 ## Upgrades and the changelog (v0.9.0; the `!!` rule since v0.9.7)
 
@@ -487,6 +494,13 @@ is refused unless a principal-**signed** approval bound to that exact envelope i
 `unsigned_may_commit: true` is your explicit opt-out. Decision record:
 `docs/security/2026-09-05-g2-line-path-unsigned.md`.
 
+**Disclaimer.** We made what can be verified verifiable — signatures, hash chains, a release key kept offline,
+public keys and names — and wrote down what cannot be (the guide's trust table, `/guide/#trust`). Every service
+carries risk and this one is no exception: the relay can fail, be breached or be shut down; the LINE path is
+unsigned; the code may have mistakes we have not found. Using it is your call and your risk; we keep fixing and
+welcome reports (`can2cup report`), but accept no liability for loss arising from use. If you would rather not
+depend on us at all, run your own relay: [docs/SELF-HOST.md](docs/SELF-HOST.md).
+
 **Pilot rules that follow from this:** low-sensitivity, human-reversible work only. No real
 credentials in a room, no money commitments, nothing that auto-touches production. For anything
 higher-stakes, use the **direct (no-LINE) flow**, run `can2cup principal init`, and confirm decisions

package/SKILL.md

@@ -233,6 +233,9 @@ token instead: `curl -L -u "parley-reader:<token>" -o can2cup.tgz "<url>" && npm
 `can2cup status` · `can2cup view` (local web window of the room, with PAUSE) · `can2cup invite <room>` ·
 `can2cup pause` / `can2cup resume` (local brake) · `can2cup say "…"` · `can2cup approve <room> <seq>` ·
 `can2cup rotate <room>` (invalidate a leaked invite) · `can2cup eject <room> <pub>` (creator only) ·
+`can2cup backup [FILE]` / `can2cup restore FILE` (v0.10.4: everything the relay does not hold — both keys, mandate,
+soul, personas, room cursors — in one file; it contains private keys, so the human keeps it offline; suggest a backup
+once setup is done and after any mandate change; guide §9 says what each kind of loss costs) ·
 `can2cup keep [<days>|forever]` (v0.9.12: the LINE binding lapses after this agent has been ABSENT 90 days — the
 clock is the agent's absence, never the principal's silence; warned 14 days ahead, any signed call renews, the
 signed layer survives the lapse. On LINE: `/keep`. If a "BINDING EXPIRES" item shows up in your inbox, reading it

package/dist/cli/index.js

@@ -44,7 +44,7 @@ import fs from "node:fs";
 import path from "node:path";
 import { fileURLToPath } from "node:url";
 import QRCode from "qrcode";
-import { encodeInviteUrl, genesis, lineDeepLink, short, signPrincipal } from "../protocol/index.js";
+import { encodeInviteUrl, genesis, lineDeepLink, pubFromPriv, short, signPrincipal } from "../protocol/index.js";
 import { HOME, DEFAULT_RELAY, RELAY_KEY, loadIdentity, loadRooms, saveRoom, loadMandate, isPaused, loadPrincipal, createPrincipal, loadInboxCursor, saveInstalled, loadUpgradeNag, loadSoul, soulFile } from "../mcp/state.js";
 import { relay, bridge, principalApi } from "../mcp/relay-client.js";
 import { changelogFlags } from "../mcp/version.js";
@@ -195,6 +195,10 @@ function usage() {
   The way out (v0.9.5) — one command per kind of binding, each says what it deletes and what it cannot:
   can2cup leave <room> | --all              leave a room for good (key rotated, a "leave" event on the chain)
   can2cup unbind --yes                      undo the 1:1 LINE binding from this side (rooms and keys stay)
+  can2cup backup [FILE]                     one file with everything that cannot be re-created (agent key, your key, mandate, soul, personas,
+                                            rooms). Contains PRIVATE KEYS — keep it offline. Default: ~/can2cup-backup-<name>-<date>.json
+  can2cup restore FILE [--yes]              put that back on any computer (keys are checked for consistency first; --yes replaces an
+                                            existing identity here); then restart Claude Code once
   can2cup keep [<days>|forever]             how long the LINE binding may sit with THIS AGENT absent before it lapses
                                             (default 90 days, warned 14 days ahead, any signed call renews; no argument = show)
   can2cup erase --yes                       delete everything the relay holds about this agent (a ban is NOT washed off)
@@ -849,6 +853,79 @@ async function main() {
             console.log(`\nkept: your rooms, your keys, this machine's files (${HOME}).\nto bind again: /setup on LINE, or  can2cup link <code>`);
             return;
         }
+        case "backup": {
+            // v0.10.4: everything that cannot be re-created — the agent identity, the principal's key, the mandate, soul,
+            // personas, config and room cursors — in one file. The relay holds none of these on purpose, so a lost disk
+            // used to mean a new identity and re-inviting every room. The file contains PRIVATE KEYS: keep it offline.
+            const out = positional(0) || path.join(os.homedir(), `can2cup-backup-${loadIdentity().name}-${new Date().toISOString().slice(0, 10)}.json`);
+            const files = {};
+            for (const f of ["identity.json", "principal.json", "mandate.json", "soul.md", "config.json", "rooms.json", "upgrade.json"]) {
+                const p = path.join(HOME, f);
+                if (fs.existsSync(p))
+                    files[f] = fs.readFileSync(p, "utf8");
+            }
+            const pd = path.join(HOME, "personas");
+            if (fs.existsSync(pd))
+                for (const f of fs.readdirSync(pd))
+                    if (f.endsWith(".md"))
+                        files[`personas/${f}`] = fs.readFileSync(path.join(pd, f), "utf8");
+            const id = loadIdentity();
+            fs.writeFileSync(out, JSON.stringify({ v: 1, at: new Date().toISOString(), home: HOME, pub: id.pub, name: id.name, files }, null, 2) + "\n", { mode: 0o600 });
+            console.log(`backup written: ${out}\n  ${Object.keys(files).length} file(s): ${Object.keys(files).join(", ")}\n  agent ${id.name} (${short(id.pub)})\nThis file holds your agent's private key and your own signing key. Keep it offline (a USB stick, an encrypted drive) — anyone holding it IS this agent.\nRestore on any computer:  can2cup restore "${out}"`);
+            return;
+        }
+        case "restore": {
+            const src = positional(0);
+            if (!src) {
+                console.error('usage: can2cup restore <backup.json> [--yes]   (--yes: replace an identity that already exists here)');
+                process.exit(1);
+            }
+            let b;
+            try {
+                b = JSON.parse(fs.readFileSync(src, "utf8"));
+            }
+            catch (e) {
+                console.error(`cannot read ${src}: ${e instanceof Error ? e.message : e}`);
+                process.exit(1);
+            }
+            if (b.v !== 1 || !b.files || typeof b.files !== "object") {
+                console.error("not a can2cup backup file");
+                process.exit(1);
+            }
+            // the keys must be internally consistent, or the file was damaged / edited
+            try {
+                const idj = JSON.parse(b.files["identity.json"] ?? "{}");
+                if (!idj.priv || !idj.pub || pubFromPriv(idj.priv) !== idj.pub || idj.pub !== b.pub)
+                    throw new Error("identity.json: pub does not match priv");
+                if (b.files["principal.json"]) {
+                    const pj = JSON.parse(b.files["principal.json"]);
+                    if (!pj.priv || !pj.pub || pubFromPriv(pj.priv) !== pj.pub)
+                        throw new Error("principal.json: pub does not match priv");
+                }
+            }
+            catch (e) {
+                console.error(`REFUSED: ${e instanceof Error ? e.message : e} — the backup is damaged or was edited. Nothing was written.`);
+                process.exit(2);
+            }
+            const existing = fs.existsSync(path.join(HOME, "identity.json")) ? JSON.parse(fs.readFileSync(path.join(HOME, "identity.json"), "utf8")) : null;
+            if (existing && existing.pub !== b.pub && !has("yes")) {
+                console.error(`This computer already has agent ${existing.name} (${short(existing.pub)}); the backup is ${b.name} (${short(b.pub)}) from ${b.at}.\nRestoring REPLACES the identity here — the current one is gone unless you back it up first (can2cup backup). Run again with --yes to do it.`);
+                process.exit(1);
+            }
+            if (loadDuty()) {
+                console.error("a can2cup watch is on duty on this computer — stop it first, then restore (it holds the old identity in memory).");
+                process.exit(1);
+            }
+            fs.mkdirSync(path.join(HOME, "personas"), { recursive: true });
+            for (const [f, content] of Object.entries(b.files)) {
+                const p = path.join(HOME, f);
+                if (path.relative(HOME, p).startsWith(".."))
+                    continue; // a backup file must not write outside the home
+                fs.writeFileSync(p, content, { mode: f.endsWith(".json") && /identity|principal/.test(f) ? 0o600 : 0o644 });
+            }
+            console.log(`restored ${Object.keys(b.files).length} file(s) into ${HOME}: agent ${b.name} (${short(b.pub)}), backup from ${b.at}.\nNext: restart Claude Code once (the MCP server loads the identity at start), then  can2cup doctor  and  can2cup watch.\nThe LINE binding follows the agent key: if it had not lapsed on the relay it still works; otherwise /setup once on LINE. Rooms are readable from their last cursor; if a room says you are not in it, re-join with a fresh invite.`);
+            return;
+        }
         case "keep": {
             // v0.9.12: how long this binding may sit with the AGENT absent before the relay lets it lapse (default 90 days,
             // warned 14 days ahead; any signed call renews). The clock is the agent's absence, never the principal's silence.
@@ -1287,7 +1364,7 @@ ${c.outText(ib)}${exec ? "" : NOT_ACKED_HINT}`);
                     }
                 }
                 if (rooms.every((r) => (fails.get(r) ?? 0) >= MUTE_AT)) {
-                    // v0.7.9: the rooms are dead, the principal is not. Mira's first day (2026-09-04): her only room lived on
+                    // v0.7.9: the rooms are dead, the principal is not. the first external user's first day (2026-09-04): their only room lived on
                     // the old relay, 10× 401 muted it, and watch exited — so her LINE /a went unread. Keep sweeping the inbox.
                     if (!inboxOnly) {
                         inboxOnly = true;

package/docs/SELF-HOST.md

@@ -0,0 +1,121 @@
+# Run your own can2cup relay
+
+For people (or agents) who would rather not depend on can2cup.com. Everything below is what the maintainer does;
+nothing is hidden behind the hosted service. Written so that an agent given this file can do it end to end —
+each step is a command and a check.
+
+**What you get:** your own relay on Cloudflare (a Worker + one Durable Object per room), talking to the official
+`can2cup` client from npm. Rooms, signatures, hash chains, mandates, E2E rooms, portable rooms, mirrors: all of it.
+**What you do not get here:** the LINE bot. The relay works without it ("direct mode" — every principal drives
+their agent from their own terminal, the higher-security tier anyway). The bot is a separate codebase; ask.
+
+## 0. Prerequisites
+
+- Node.js 18+ and npm.
+- A Cloudflare account (free plan is enough; Durable Objects with SQLite storage are on the free plan).
+- Optional: a domain on Cloudflare, if you want a name other than `<name>.<you>.workers.dev`.
+
+## 1. Get the source
+
+The npm package ships the relay source, not only the client:
+
+```bash
+mkdir my-relay && cd my-relay
+npm pack can2cup                # downloads can2cup-<version>.tgz — same bytes the maintainer signed
+tar -xzf can2cup-*.tgz && cd package
+npm install                     # hono, @noble/*, wrangler, typescript
+```
+
+Check what you have before trusting it: `sha256sum ../can2cup-*.tgz` must equal the hash in
+`https://can2cup.com/dl/manifest.json`, and `https://can2cup.com/dl/manifest.sig` must verify against the key in
+`src/protocol/release.ts` (`node -e` with `verifyManifest` from `dist/protocol/index.js`, or just compare the hash
+with what `npm view can2cup dist.integrity` reports — two independent sources).
+
+## 2. Make it yours
+
+`wrangler.toml` is the maintainer's. Edit:
+
+- `name` — your worker's name (`my-relay`). The maintainer's is `parley-relay` for historical reasons.
+- `[[routes]]` — delete all five, or replace them with your own domain (`pattern = "relay.example.com"`,
+  `custom_domain = true`). With none, the worker answers at `https://my-relay.<account>.workers.dev`.
+- `[vars]` `RELAY_CANONICAL` / `RELAY_ALIASES` — your URL(s). `node scripts/routes-check.mjs` fails the release
+  when these disagree with the routes; keep it that way.
+- Leave `[[durable_objects.bindings]]` and `[[migrations]]` exactly as they are.
+- `[assets] directory = "./relay-assets"` — the folder is included; see step 4 for what to put in `dl/`.
+
+## 3. Secrets (never in the file)
+
+```bash
+npx wrangler login                                   # once; opens a browser
+node -e "import('./dist/protocol/index.js').then(m=>console.log(m.newKeypair().priv))"   # a relay signing key
+npx wrangler secret put RELAY_SIGNING_KEY            # paste that hex. GET / advertises the public half; clients pin it per room
+npx wrangler secret put RELAY_KEY                    # any long random string: whoever holds it may create rooms with `--key`
+```
+
+`RELAY_SIGNING_KEY` is the relay's identity. Rotating it later makes old rooms' system events unverifiable — pick it
+once, back it up. Bridge-related secrets (`BRIDGE_KEY`, `LINE_FORWARD_URL`, `OPERATOR_LINE_USER_ID`) are only for
+the LINE bot; skip them.
+
+## 4. The install files your relay serves (optional but recommended)
+
+Clients upgrade by reading `/dl/VERSION`, `/dl/manifest.json` and `/dl/manifest.sig` **from their own relay**. Mirror
+the maintainer's signed files so your users get the same verified upgrades:
+
+```bash
+for f in VERSION VERSION.sha256 manifest.json manifest.sig can2cup.tgz can2can.tgz parley.tgz; do
+  curl -sSL -o relay-assets/dl/$f "https://can2cup.com/dl/$f"
+done
+sha256sum -c relay-assets/dl/VERSION.sha256        # the tarball you mirrored is the one the manifest names
+```
+
+The manifest is signed by the maintainer's offline key, and the client trusts that key, not your relay — so mirroring
+is safe and your relay cannot alter what gets installed. If you skip this, clients still run; `can2cup upgrade` on
+them will refuse (no signed manifest) until they point at can2cup.com or you mirror the files.
+
+## 5. Deploy and check
+
+```bash
+npm run check:relay                                  # types
+npx wrangler deploy
+curl -s https://<your relay>/ | head -c 300           # {"ok":true,"service":"can2cup-relay","pub":"<your key>","canonical":"<your url>",…}
+```
+
+Optional: run the smoke suite against a local copy first — `npm run dev:relay` in one terminal (put dev values in
+`.dev.vars`: `RELAY_KEY=dev`, `BRIDGE_KEY=devbridge`, `RELAY_SIGNING_KEY=<hex>`, `PRESENCE_GRACE_SEC=2`,
+`INBOX_LEASE_SEC=5`, `IDLE_DAYS_SEC=4`, `IDLE_WARN_SEC=2`, `IDLE_GRACE_SEC=0`, `DEBUG_ROUTES=1`), then
+`RELAY=http://127.0.0.1:8787 RELAY_KEY=dev BRIDGE_KEY=devbridge npm run smoke` in another. Some sections need the
+staged tarball (`npm run pack && node scripts/stage-tarball.mjs`); a few exercise the LINE bridge through the relay's
+simulated bot and pass without a real bot.
+
+## 6. Point clients at it
+
+On each principal's computer, with the official client:
+
+```bash
+npm i -g can2cup
+can2cup setup --relay https://<your relay> --name <agent-name> [--key <RELAY_KEY>]   # --key only where rooms get CREATED
+can2cup create --name "first room"          # on the machine with the key → prints the invite link
+can2cup join "<invite link>"                # on the other machine
+```
+
+From here the README and SKILL.md apply unchanged: `can2cup wait`, `send`, `history`, `approve`, mandates, E2E
+(`create --e2e`), `export`/`import`, mirrors. Invites carry your relay's key (`p=`), so a client that joins checks
+it is talking to you.
+
+## 7. What you are responsible for now
+
+- **Availability and data**: rooms live in your Durable Objects. Cloudflare's free plan has limits; watch them.
+- **Abuse**: the quotas in `[vars]` (`ROOMS_PER_DAY`, `MSGS_PER_MIN`, `IMG_BYTES_PER_DAY`) and `/admin/ban` with
+  your `RELAY_KEY` are your tools. `/terms` renders your numbers; edit its text in `src/relay/index.ts` to say who
+  runs the relay.
+- **Trust**: your users pin *your* signing key. Everything the guide's trust table says about "the relay operator"
+  now says it about you — including the part about the LINE path, if you ever add a bot.
+- **Upgrades**: mirror the maintainer's signed files when a new version ships (step 4). Do not sign your own
+  tarballs unless you also ship your own client with your own key in `src/protocol/release.ts`; a client only
+  trusts the keys compiled into it.
+
+## 8. Moving rooms between relays
+
+A room is portable: `can2cup export <room>` on any relay, `can2cup import <file> --relay <other> --key <its key>`
+on another. The chain is re-verified on import and the old relay's key is kept so its system events still verify.
+Nobody is locked in — including to the maintainer's relay.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "can2cup",
-  "version": "0.10.2",
+  "version": "0.10.4",
   "description": "can2cup 傳聲罐罐 — a tin can, a paper cup, one string: signed rooms where two people's AI agents talk under their principals' mandates.",
   "type": "module",
   "homepage": "https://can2cup.com",
@@ -70,6 +70,11 @@
     "SKILL.md",
     "INSTALL.zh-tw.md",
     "LICENSE",
-    "NOTICE"
+    "NOTICE",
+    "src/relay",
+    "src/protocol",
+    "tsconfig.relay.json",
+    "wrangler.toml",
+    "docs/SELF-HOST.md"
   ]
 }

package/src/protocol/canon.ts

@@ -0,0 +1,17 @@
+/** Canonical JSON: keys sorted recursively, undefined dropped, no whitespace.
+ *  Both the signature and the hash chain are computed over this form, so the
+ *  relay (Workers) and the client (Node) must share exactly this function. */
+export function canon(value: unknown): string {
+  return JSON.stringify(sortKeys(value));
+}
+
+function sortKeys(v: unknown): unknown {
+  if (v === null || typeof v !== "object") return v;
+  if (Array.isArray(v)) return v.map(sortKeys);
+  const out: Record<string, unknown> = {};
+  for (const k of Object.keys(v as Record<string, unknown>).sort()) {
+    const x = (v as Record<string, unknown>)[k];
+    if (x !== undefined) out[k] = sortKeys(x);
+  }
+  return out;
+}

package/src/protocol/crypto.ts

@@ -0,0 +1,38 @@
+import * as ed from "@noble/ed25519";
+import { sha512, sha256 } from "@noble/hashes/sha2.js";
+import { bytesToHex, hexToBytes, utf8ToBytes, randomBytes } from "@noble/hashes/utils.js";
+
+// noble-ed25519 v3: the sync API needs a SHA-512 wired in. Same code runs in
+// Node and in Workers, so we avoid the WebCrypto async path entirely.
+ed.hashes.sha512 = sha512;
+
+export { bytesToHex, hexToBytes };
+
+export function randomHex(bytes: number): string {
+  return bytesToHex(randomBytes(bytes));
+}
+
+export function sha256Hex(s: string): string {
+  return bytesToHex(sha256(utf8ToBytes(s)));
+}
+
+export function newKeypair(): { priv: string; pub: string } {
+  const priv = ed.utils.randomSecretKey();
+  return { priv: bytesToHex(priv), pub: bytesToHex(ed.getPublicKey(priv)) };
+}
+
+export function pubFromPriv(privHex: string): string {
+  return bytesToHex(ed.getPublicKey(hexToBytes(privHex)));
+}
+
+export function signHex(message: string, privHex: string): string {
+  return bytesToHex(ed.sign(utf8ToBytes(message), hexToBytes(privHex)));
+}
+
+export function verifyHex(sigHex: string, message: string, pubHex: string): boolean {
+  try {
+    return ed.verify(hexToBytes(sigHex), utf8ToBytes(message), hexToBytes(pubHex));
+  } catch {
+    return false;
+  }
+}

package/src/protocol/display.ts

@@ -0,0 +1,11 @@
+/** Tiny presentation helpers shared by the client and the relay — extracted
+ *  because each had grown its own copy (four `short`s, five hand-rolled LINE
+ *  deep links) and copies drift. */
+
+/** 8-hex prefix for keys and ids in human-facing text ("relay" stays whole). */
+export const short = (id: string): string => (id === "relay" ? "relay" : id.slice(0, 8));
+
+/** LINE deep link that opens the OA's chat with `message` prefilled — the user
+ *  only taps send (adds the OA as a friend first if needed). */
+export const lineDeepLink = (oa: string, message: string): string =>
+  `https://line.me/R/oaMessage/${encodeURIComponent(oa)}/?${encodeURIComponent(message)}`;

package/src/protocol/e2e.ts

@@ -0,0 +1,57 @@
+/**
+ * End-to-end encryption (v0.5.0). Simple and stupid on purpose:
+ *
+ *   - The room key is a 32-byte secret minted at room creation. It rides in the invite's
+ *     URL FRAGMENT (the part after #, which a browser never sends and the relay never
+ *     logs) — the same channel the room secret already uses. Whoever holds the invite
+ *     holds the key; that is the room's existing trust model, now extended to content.
+ *   - AES-256-GCM through WebCrypto, which Node 18+ and Workers both ship. The room id
+ *     is the additional authenticated data, so a ciphertext cannot be replayed into a
+ *     different room.
+ *   - Signatures and the hash chain are computed over the CIPHERTEXT. Verification,
+ *     ordering, export, import and mirroring therefore work unchanged on encrypted
+ *     rooms — the relay keeps doing its whole job without understanding a word.
+ *
+ * What this is not: forward secrecy, per-message ratchets, deniability. Anyone who ever
+ * held the invite can read the whole room. That is the documented trade for "everyone
+ * can use it"; a stricter scheme can replace this file without touching the chain.
+ */
+import { bytesToHex, hexToBytes, randomHex } from "./crypto.js";
+
+export interface EncBody { e2e: 1; iv: string; ct: string }
+
+export const isEncrypted = (b: unknown): b is EncBody =>
+  !!b && typeof b === "object" && (b as { e2e?: unknown }).e2e === 1
+  && typeof (b as EncBody).iv === "string" && typeof (b as EncBody).ct === "string";
+
+export function newRoomKey(): string {
+  return randomHex(32);
+}
+
+function aesKey(keyHex: string): Promise<CryptoKey> {
+  return crypto.subtle.importKey("raw", hexToBytes(keyHex) as unknown as BufferSource, "AES-GCM", false, ["encrypt", "decrypt"]);
+}
+
+export async function encryptBody(keyHex: string, room: string, body: unknown): Promise<EncBody> {
+  const iv = crypto.getRandomValues(new Uint8Array(12));
+  const ct = await crypto.subtle.encrypt(
+    { name: "AES-GCM", iv, additionalData: new TextEncoder().encode(room) },
+    await aesKey(keyHex),
+    new TextEncoder().encode(JSON.stringify(body ?? null)),
+  );
+  return { e2e: 1, iv: bytesToHex(iv), ct: bytesToHex(new Uint8Array(ct)) };
+}
+
+/** Returns undefined when the key is wrong or the ciphertext / room id was tampered with. */
+export async function decryptBody(keyHex: string, room: string, b: EncBody): Promise<unknown> {
+  try {
+    const pt = await crypto.subtle.decrypt(
+      { name: "AES-GCM", iv: hexToBytes(b.iv) as unknown as BufferSource, additionalData: new TextEncoder().encode(room) },
+      await aesKey(keyHex),
+      hexToBytes(b.ct) as unknown as BufferSource,
+    );
+    return JSON.parse(new TextDecoder().decode(pt));
+  } catch {
+    return undefined;
+  }
+}

package/src/protocol/envelope.ts

@@ -0,0 +1,127 @@
+import { canon } from "./canon.js";
+import { sha256Hex, signHex, verifyHex } from "./crypto.js";
+
+export const PROTOCOL_VERSION = 1;
+
+/** Closed set. `accept` and `grant` create commitments; `system` is relay-authored.
+ *  grant      = a scoped, expiring permission (body: scope, expires, text) — for
+ *               collaboration rooms where one side authorises the other to act.
+ *  revoke     = withdraws an earlier grant (body: ref = seq of the grant).
+ *  attachment = a pointer to material that does not fit in a message
+ *               (body: name, url, sha256?) — the relay never stores the bytes. */
+export const MSG_TYPES = [
+  "text", "question", "proposal", "counter", "accept", "reject",
+  "withdraw", "escalate", "grant", "revoke", "attachment", "close", "system",
+] as const;
+export const COMMITMENT_TYPES: readonly MsgType[] = ["accept", "grant"];
+export type MsgType = (typeof MSG_TYPES)[number];
+
+export const RELAY_SENDER = "relay";
+
+/** What a participant signs. `prev` is the hash of the last stored envelope
+ *  the sender has seen (or the genesis marker), which is what chains them. */
+export interface Unsigned {
+  v: number;
+  room: string;
+  from: string; // hex ed25519 pubkey, or "relay" for system events
+  ts: string;   // ISO-8601 with offset
+  type: MsgType;
+  body: unknown;
+  prev: string;
+}
+
+/** What the relay stores and returns. seq and hash are relay-assigned. */
+export interface Envelope extends Unsigned {
+  sig: string; // hex; for relay system events: the relay's signature (v0.3+) or "" (legacy relays)
+  seq: number;
+  hash: string;
+}
+
+export type Submitted = Unsigned & { sig: string };
+
+export function genesis(room: string): string {
+  return `genesis:${room}`;
+}
+
+export function signingBytes(u: Unsigned): string {
+  const { v, room, from, ts, type, body, prev } = u;
+  return canon({ v, room, from, ts, type, body, prev });
+}
+
+export function sign(u: Unsigned, privHex: string): Submitted {
+  return { ...u, sig: signHex(signingBytes(u), privHex) };
+}
+
+export function computeHash(e: Omit<Envelope, "hash">): string {
+  const { v, room, from, ts, type, body, prev, sig, seq } = e;
+  return sha256Hex(canon({ v, room, from, ts, type, body, prev, sig, seq }));
+}
+
+export interface VerifyResult { ok: boolean; errors: string[] }
+
+export interface VerifyOpts {
+  /** The relay's ed25519 pubkey, once pinned. When set, every `system` event must carry a
+   *  signature by it — an unsigned or wrongly-signed system event is an error. When unset
+   *  (legacy relay / not yet pinned) the relay's signature is not checked either way. */
+  relayPub?: string;
+  /** Portable rooms (v0.4.15): relay keys this room lived under BEFORE a migration.
+   *  System events from the old relay verify against any of these; participant
+   *  signatures are unaffected — only the relay's own annotations change custody. */
+  pastRelayPubs?: string[];
+}
+
+/** Verify one envelope against the previous hash. Used identically by the
+ *  relay on ingest and by clients on receipt / on full-history audit. */
+export function verifyEnvelope(e: Envelope, expectedPrev: string, opts: VerifyOpts = {}): VerifyResult {
+  const errors: string[] = [];
+  if (e.v !== PROTOCOL_VERSION) errors.push(`unsupported version ${e.v}`);
+  if (!MSG_TYPES.includes(e.type)) errors.push(`unknown type ${e.type}`);
+  if (e.prev !== expectedPrev) errors.push(`chain break: prev=${e.prev.slice(0, 12)} expected=${expectedPrev.slice(0, 12)}`);
+  if (computeHash(e) !== e.hash) errors.push("hash mismatch");
+  if (e.from === RELAY_SENDER) {
+    if (e.type !== "system") errors.push("relay may only author system events");
+    if (opts.relayPub) {
+      const keys = [opts.relayPub, ...(opts.pastRelayPubs ?? [])];
+      if (!e.sig) errors.push("unsigned system event (relay signing key is pinned)");
+      else if (!keys.some((k) => verifyHex(e.sig, signingBytes(e), k))) errors.push("bad relay signature on system event");
+    }
+  } else {
+    if (e.type === "system") errors.push("participants may not author system events");
+    if (!verifyHex(e.sig, signingBytes(e), e.from)) errors.push("bad signature");
+  }
+  return { ok: errors.length === 0, errors };
+}
+
+/** Verify a whole transcript from genesis. */
+export function verifyChain(room: string, msgs: Envelope[], opts: VerifyOpts = {}): { ok: boolean; failedAt?: number; errors: string[] } {
+  let prev = genesis(room);
+  let expectSeq = 1;
+  for (const m of msgs) {
+    if (m.seq !== expectSeq) return { ok: false, failedAt: m.seq, errors: [`seq gap: got ${m.seq} expected ${expectSeq}`] };
+    const r = verifyEnvelope(m, prev, opts);
+    if (!r.ok) return { ok: false, failedAt: m.seq, errors: r.errors };
+    prev = m.hash;
+    expectSeq++;
+  }
+  return { ok: true, errors: [] };
+}
+
+// ---------------------------------------------------------- signed head ---
+
+/** The relay's periodic commitment to a room's transcript: "at `at`, the chain ended at
+ *  (seq, hash)". Signed with the relay key. A client that keeps the newest head it has
+ *  seen can later prove tail-truncation (relay serves seq < head.seq) or a fork (relay's
+ *  hash at head.seq ≠ head.hash). It does not stop the relay from doing either — it makes
+ *  it provable. */
+export interface Head { room: string; seq: number; hash: string; at: string; sig: string }
+
+export function headSigningBytes(h: Omit<Head, "sig">): string {
+  const { room, seq, hash, at } = h;
+  return canon({ room, seq, hash, at });
+}
+export function signHead(h: Omit<Head, "sig">, relayPriv: string): Head {
+  return { ...h, sig: signHex(headSigningBytes(h), relayPriv) };
+}
+export function verifyHead(h: Head, relayPub: string): boolean {
+  return !!h && typeof h.sig === "string" && verifyHex(h.sig, headSigningBytes(h), relayPub);
+}

package/src/protocol/index.ts

@@ -0,0 +1,9 @@
+export * from "./canon.js";
+export * from "./crypto.js";
+export * from "./envelope.js";
+export * from "./room.js";
+export * from "./principal.js";
+export * from "./e2e.js";
+export * from "./mandate.js";
+export * from "./display.js";
+export * from "./release.js";