Tracing request responses and change notifications separately in a browser extension
A note on requesting writes through message-based RPC in separated extension contexts, then using change signals and query invalidation so other screens re-read the single source of truth
- Chrome's message APIs are transport; request validation, routing, and error responses are defined by the application
- Command responses and change notifications for other screens have different purposes and should stay separate