feat!: replace Zen SEA with Ed25519 and sync the library over HTTP

[scobru]

Summary

• Identity: profile.html and sso.html derive and sign with vendor/identity.js (vendored from fid, WebCrypto Ed25519, same derivation as fid 5.0.0 — the same alias + passphrase gives the same key as the portal). vendor/zen.min.js, crypto.wasm, pen.wasm and window.ZEN_RELAY are gone.
• Library sync over HTTP (components/library-sync.js): the player mirrors favorites, artists and playlists to the TuneCamp instance the identity is linked to, through the new /api/auth/zen/library/:pub routes (scobru/tunecamp#1227, merged). Requests are signed with the identity key; private records are encrypted in the browser (AES-GCM, key derived from the identity key); shared playlists stay public. It reads on open, when the tab becomes visible, and once a minute; writes are debounced; last write wins by the record's own timestamp.
• New device: with no linked passport, the player asks the directory instances (config.js) which one holds an account for the key (GET .../:pub/account) and remembers it.
• Share links now name the instance: player.html?pl=<pub>.<id>@<host>. Old ?pl=<pub>.<id> links used the relay and stop resolving.
• README and site copy (about, ecosystem) no longer mention Zen SEA or a relay.

Behaviour changes to be aware of

• Every existing FID identity is re-keyed (see fid 5.0.0); users relink on their instance.
• The profile card (name, bio, avatar) and the linked-instance list now live in the browser only; the relay used to carry both. Nothing else read them.
• Sync needs an instance where the identity has an account; otherwise the player says so and the library stays local.

Test plan

• tests/library-sync.test.js (new, 24 assertions): encryption, share tokens, instance discovery, two devices through an in-process instance, tombstones, shared playlists, refusals. Plus library (50), instance-import (36), url-safety (15), check_syntax.js.
• tests/player.e2e.cjs in headless Chromium: 54 checks, including an unreachable instance reported honestly and a published playlist opened from its link. (It was already failing on a stale text assertion before this change; fixed.)
• Browser smoke: logging in on the profile page yields the pinned fid vector bE9DAycqb9gbxMJHTxh5RRxVQRPpG-wrCojHVl0s9sM; sso.html authorize posts a 64-byte Ed25519 signature with masterKeySource: { type: 'zen', pubKey }.
• Merge together with the tunecamp release that carries the library routes.

Based on main: the website's dev branch is a stale, heavily diverged branch (it lacks sso.html, the tests and utils.js), and every previous PR here targets main.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FeCp9YZh9dCEHXtRdpVeFe

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
tunecamp	Ready	Preview	Oct 6, 2026 4:14pm UTC