Peerly & core 1.15.1
Security and reliability fixes from the repository-wide review, released together as Peerly and @peerly/core 1.15.1.
- Public lobby presence uses short-lived device-bound certificates instead of exposing OIDC tokens.
- Device revocation cuts off existing account, content, and lobby sessions; failed revocations remain queued for retry.
- Encrypted channel definitions and deletion records survive rolling chat retention.
- Workspace and DM text is saved to a persistent outbox before the composer clears, with stable IDs across retries.
- History write failures are visible and recoverable through export; temporary server errors no longer replace the working offline shell.
- Updated deployment/rollback instructions and technical privacy descriptions.
Upgrade: Consumers of the core Durable Object channel factories must deploy the current gateway and channel implementations together, including the documented session headers and bindings. Older clients must reconnect/refresh. Channel state and deletion records are retained separately from chat history. The release keeps the configured production backend in place.
Changes: #102. Version alignment: #104.
Validation includes unit and Workers suites, Chromium app/DO E2E suites, CodeQL, dependency/secret scans, mutation testing, and Cloudflare build checks.