@vxil/cli 0.20.1 → 0.20.2

package/README.md

@@ -23,7 +23,7 @@ export default defineConfig({
   features: {
     auth: { enabled: true },
     cms: { enabled: true, draftPublish: true },
-    notifications: { enabled: true, provider: 'resend', fromEmail: 'noreply@example.app' },
+    notifications: { enabled: true, provider: 'resend', fromEmail: 'noreply@example.com' },
   },
   // (b) CMS schema-as-code — collections + fields, reconciled by `vxil push`
   cms: {

package/dist/_vxil-feature-configs-readmodels.d.ts

@@ -37,10 +37,12 @@ interface CdcRuleLike {
 export declare function validateCdcConfig(cdc: Record<string, CdcRuleLike> | undefined): string[];
 /** What a payload:'full' change-data rule must know about its target
  *  collection's read gates. `readRoleFields`: fields with a non-empty
- *  `readRoles`; `endUserAccess`: the collection's end-user access mode. */
+ *  `readRoles`; `endUserAccess`: the collection's end-user access mode;
+ *  `ownerField`: the end-user owner-scope field (null/absent = none). */
 export interface CdcCollectionGates {
     readRoleFields?: readonly string[];
     endUserAccess?: 'readwrite' | 'read' | 'none';
+    ownerField?: string | null;
 }
 /**
  * A `payload: 'full'` change-data rule inlines the stored row into a realtime
@@ -48,7 +50,9 @@ export interface CdcCollectionGates {
  * the read projection. So it must never target a collection whose reads are
  * gated: a field with `readRoles` (the frame would carry the gated value), or
  * an `endUserAccess` of 'read' / 'none' (the frame would bypass the
- * collection's end-user gate). Pure; one problem line per offending ENABLED
+ * collection's end-user gate), or an `ownerField` (end users read only their
+ * own rows, but the frame would carry every user's row to every subscriber —
+ * CDC-FULL-OWNER-SCOPED). Pure; one problem line per offending ENABLED
  * rule (an unknown collection is skipped). The safe shape is `payload: 'ids'`
  * and a re-read through the cms, where every gate applies.
  */