2 Commits

Include renames

Author	SHA1	Message	Date
archipelagoandClaude Opus 5	90884e6259	feat(01-02): chat mutations mutate demo state instead of acking (FED-04) ... Reactions, replies, read-receipts, edits, deletes, forwards and channel sends shared one bare `{ ok: true, sent: true }` case, so none of them rendered on the demo — the UI derives reaction chips and reply quotes from the message store, and there was nothing in it to derive from. Each now mirrors its daemon counterpart. Reactions/replies/receipts push typed messages carrying the { sender_pubkey, sender_seq } target key Mesh.vue's reactionIndex and replyTargetPreview read. Edits rewrite the text and set edited_at; deletes tombstone IN PLACE (plaintext, typed_payload.deleted, message_type 'delete') because that is what mesh/mod.rs apply_local_delete does — it does not remove the row. Edits and deletes go through a per-session overrides overlay keyed by sender_seq, because mesh.messages rebuilds its seed array on every read, so in-place mutation would only ever work for messages sent this session. mesh.refresh and mesh.reboot-radio stay acknowledgements on purpose — the daemon's handlers have no message-store effect either — with a comment saying so, so a later reader does not "fix" them into divergence. Also completes the phase bookkeeping for 01-02/03/11/12/13/14/15 and lands the orphaned 01-12/01-14 SUMMARYs. Verified: parity harness 17/17 live assertions; full frontend suite 102 files / 822 tests green. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-01 06:37:00 -04:00
archipelagoandClaude Opus 5	b8979f3687	feat(01-02): demo answers every mesh/federation RPC the UI calls (FED-04) ... Ten methods the UI calls had no case at all in mock-backend.js, so the demo answered them with "Method not found" and the frontend swallowed it in a try/catch — peer renaming, scheduling, clear-all, the assistant panel and two federation actions were all silently inert on the demo. Each new handler mirrors its daemon counterpart and cites the Rust source it mirrors, per the house convention above mesh.transport-advice: mesh.contacts-list/-save typed_messages.rs (contacts merged over peers by pubkey_hex; absent params leave stored fields) mesh.clear-all status.rs ({ status: "cleared" }) mesh.schedule/list/cancel assistant.rs + scheduler.rs ScheduledMessage mesh.assistant-status/-configure assistant.rs (key-presence semantics) federation.cancel-request handlers.rs (outbound+sent only, notify defaults true) — plus an outbound seed request, since without one the demo's cancel path was unexercisable federation.notify-did-change handlers.rs ({ notified, failed, results }) mesh.peers and mesh.contacts-list now share one DEMO_MESH_PEERS list so they cannot disagree about who is on the mesh, and the peer with no pubkey_hex is omitted from contacts exactly as the daemon omits it. scripts/mock-rpc-parity.mjs cross-references UI call sites against mock cases and then drives a live scripted RPC sequence against an ephemeral-port instance (MOCK_BACKEND_PORT). It matches only `method: '<x>'`, NOT bare string literals: Mesh.vue and Federation.vue use the same dotted names as resource-cache keys, and matching those would report permanent phantom gaps. Fail-first proof: disabling the mesh.clear-all case makes the harness exit 1 naming the gap; restored, it exits 0 twice in a row with no stray listener. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-01 06:25:59 -04:00