Jeet schema-driven field-level permission configuration

Jeet’s local-first architecture synchronizes client-side state with a remote store through a schema-driven data engine. Developers often need to restrict read or write access to individual fields within the synchronized tree to protect sensitive data.

The current implementation does not expose a native permission boundary layer that allows field‑level access rules to be declared directly in the schema, requiring custom server‑side middleware or client‑side checks that can be bypassed.

What mechanisms, if any, exist to define field‑level permissions declaratively within the Jeet schema? How can the framework enforce these boundaries on the client‑side engine without relying on external middleware? Are there extension points or hooks that let developers inject permission validation before local mutations are applied?