[Feature Request] MCP protocol needs push-style edit notifications for IDE integrations

Experimenting with a claude-code-ide.el fork for Emacs and hit a gap in the IDE protocol.

Observation: In acceptEdits permission mode for in-project files, the CLI writes directly to disk
without emitting any MCP signal to the connected IDE. Verified via WebSocket trace — no openDiff,
no openFile, no notification. Only getDiagnostics pings around the edit.

This forces IDE integrations to fall back to OS-level file watchers, losing semantic context
(which tool, what changed, what the diff was).

Verification:

• Reverse-engineered the compiled CLI binary (2.1.118, Mach-O) via string analysis
• Extracted the official VS Code extension and confirmed all 12 MCP tool registrations: openDiff,

openFile, close_tab, closeAllDiffTabs, getDiagnostics, getOpenEditors, getWorkspaceFolders,
getCurrentSelection, getLatestSelection, checkDocumentDirty, saveDocument, executeCode

• None are push-style; none fire for auto-mode in-project edits

Request: Push-style lifecycle events via MCP —

• editApplied { path, oldText, newText, range, tool }
• editPending { path, tool }
• sessionStarted / sessionEnded

Would let IDEs render live edit views, highlight changed lines, navigate edit history — without
filesystem polling. Happy to help design/test.