@agentconnect.md/cli 1.18.0-rc.15 → 1.18.0-rc.19

package/dist/index.js

@@ -7896,8 +7896,12 @@ const MemoryDreamingPolicy = object({
 	enabled: boolean(),
 	/** How many recent sessions to mine (default 20). */
 	sessionWindow: number().int().min(1).max(100).optional(),
-	/** Cron expression for scheduled dreams (same syntax as agent crons). */
+	/** Cron expression for scheduled dreams (same syntax as agent crons). A tick
+	*  that lands while a dream is already in flight is skipped, not queued. */
 	schedule: string().min(1).max(128).optional(),
+	/** IANA zone the `schedule` is evaluated in (as on agent crons). Absent ⇒ the
+	*  daemon host's local time. */
+	timezone: string().min(1).max(64).optional(),
 	/** Operator steering text applied through the whole dream pipeline. */
 	instructions: string().max(4096).optional(),
 	/** Also mine reusable procedures into candidate skills (never auto-installed). */
@@ -9423,6 +9427,20 @@ const DreamInfo = object({
 	trigger: DreamTrigger,
 	sessionIds: array(string().min(1)).max(100),
 	snapshotDigest: string().min(1).max(128),
+	/** The store's write counters when it was snapshotted, captured under the
+	*  memory-dir lock. Adoption compares them with the live counters to tell a
+	*  distill-only drift — which it may rebase over — from a tool/console write,
+	*  which must hard-fence to review. These come from the daemon's in-process
+	*  write ledger, NOT from the best-effort `.history` log, which can silently
+	*  drop an entry and so cannot authorize anything. */
+	snapshotWrites: object({
+		/** Opaque daemon-process/store generation. Counts are comparable only
+		*  within one generation — a restart resets them, which numeric
+		*  comparison alone cannot detect. */
+		generation: string().min(1).max(64),
+		total: number().int().nonnegative(),
+		nonDistill: number().int().nonnegative()
+	}).strict().optional(),
 	instructions: string().max(4096).optional(),
 	skills: array(DreamSkillInfo).max(16).optional(),
 	usage: object({