alezmad/claudemesh
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(roadmap): mark v0.3.0 phase 3.5 (web encryption) shipped
Some checks failed
CI / Lint (push) Has been cancelled
Details
CI / Typecheck (push) Has been cancelled
Details
CI / Broker tests (Postgres) (push) Has been cancelled
Details
CI / Docker build (linux/amd64) (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Alejandro Gutiérrez
2026-05-02 22:59:33 +01:00
parent a3cf9b938e
commit 95b16a23fc
1 changed files with 9 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/roadmap.md
View File

@@ -218,11 +218,15 @@ level, or wire claudemesh to messaging surfaces beyond Claude Code.
30s background re-seal loop. Wire format: `<32-byte sender x25519 30s background re-seal loop. Wire format: `<32-byte sender x25519
pubkey> || crypto_box(topic_key)` so re-sealed copies decode like pubkey> || crypto_box(topic_key)` so re-sealed copies decode like
creator-sealed copies. *Shipped 2026-05-02 in CLI v1.8.0.* creator-sealed copies. *Shipped 2026-05-02 in CLI v1.8.0.*
- **Per-topic encryption — phase 3.5 (web)** — browser-side persistent - **Per-topic encryption — phase 3.5 (web)** — browser-side
ed25519 identity in IndexedDB + `POST /v1/me/peer-pubkey` sync + persistent ed25519 identity in IndexedDB +
web chat encrypt-on-send / decrypt-on-render. Web stays on v1 `POST /v1/me/peer-pubkey` sync + web chat encrypt-on-send /
plaintext until this lands; the existing CLI re-seal loop will pick decrypt-on-render. The dashboard's throwaway pubkey is replaced on
up web members the moment they have a real pubkey. first chat-panel mount with one whose secret the browser actually
holds; the existing CLI re-seal loop seals the topic key against
it within 30s. Composer shows `🔒 v0.3.0` when keyed and "waiting
for a CLI peer to share the topic key" while `not_sealed`.
*Shipped 2026-05-02.*
- **v0.3.1 — topic message threading (reply-to)** — `topic_message` - **v0.3.1 — topic message threading (reply-to)** — `topic_message`
gains a self-FK `reply_to_id` column (migration 0027); REST `POST gains a self-FK `reply_to_id` column (migration 0027); REST `POST
/v1/messages` and the WS `send` envelope accept `replyToId`; broker /v1/messages` and the WS `send` envelope accept `replyToId`; broker