Brooklyn Nicholson 7d92056c49 feat(gateway): iMessage-style message reactions — storage, RPC, agent tool, model context ... Reactions live in the existing messages.display_metadata JSON column (no new table), with iOS Tapback semantics enforced DB-side: one reaction per author per message, re-tap retracts, different emoji replaces. The desktop catches up to the reaction contract five platform adapters already ship. - SessionDB: set/get_message_reaction, latest_message_row_id (role + offset + require_text so invisible tool-call-only rows are never targeted), take_unseen_reactions (announce-exactly-once), get_message_role - message.react RPC: accepts row_id or newest_role for live messages that haven't learned their durable id yet - react_to_message tool: desktop-gated (check_fn), defaults to the user's latest visible message, messages_back for retroactive reactions - Model context rides run_message only (beside the speech-interrupted note): the persisted prompt stays clean, so no [The user reacted …] scaffolding in transcripts, and no cached prefix ever changes - Resume projection forwards row_id + reactions; _row_id is stripped from outgoing API copies next to display_metadata		2026-07-30 00:08:28 -05:00
..
message-reactions.md	feat(gateway): iMessage-style message reactions — storage, RPC, agent tool, model context	2026-07-30 00:08:28 -05:00
openai-api-server.md	Merge PR #724: feat: --yolo flag to bypass all approval prompts	2026-03-10 20:56:30 -07:00
streaming-support.md	Merge PR #724: feat: --yolo flag to bypass all approval prompts	2026-03-10 20:56:30 -07:00