Mutations — Centralized Tracking and Validation

[leoafarias]

Is your feature request related to a problem? Please describe.
There is no centralized way to track or validate DataModel mutations. Per-path subscriptions exist (even /), but there is no global mutation hook. This makes validation, persistence, undo/redo, and auditing difficult without wrapping every widget.

Describe the solution you'd like
A central mutation hook (observable and/or interceptable) that captures mutation metadata (source, timestamp, component) and supports validation or rejection before changes apply. Optional transaction support would help group related updates.

Describe alternatives you've considered
Listening on individual paths, wrapping widgets, or doing validation post-mutation. These are fragmented and don’t cover all mutation sources uniformly.

Additional context
Use case: collaboration UI where both user and LLM edits must be validated, tracked, and persisted.
Discussion: #609