v0.35.1
July 7, 2026
Second security pass: all remaining audit findings closed — tenant-validated event references on maps and strict limits on design and AI functions.
-
Security
Tenant-validated event references on maps
When saving a map, events referenced by edges must belong to your tenant (or be global) — a foreign reference is rejected with a clear error. Wiring and reconciliation no longer reveal the name or category of other tenants' events for "legacy" references.
-
Security
More robust map saving
The map design now validates shape and size of the content (node/edge types, label length, max 300 nodes and 600 edges as in import): a malformed payload gets a precise error instead of a generic server error.
-
Security
Limits on AI design functions
All AI design endpoints (data schema generation, flow generate/copilot, map copilot) now have explicit limits on request size, message length and history depth — oversized requests are rejected before ever reaching the AI provider, protecting costs and latency.
-
Security
Event integration snippet fixed
The curl example in the edge panel suggested API-key authentication that the events endpoint does not support; it now correctly documents the user token (JWT, Operator role or higher).