/**
 * Scheduled dream-cycle sweep (Task 1944).
 *
 * Runs the existing seven deterministic dream-cycle phases against every
 * account on the install, once per account per cadence window (~24h), with no
 * operator action. Task 327 shipped the sweep operator-initiated only and named
 * this scheduling layer as its follow-up; this binary is that layer.
 *
 * It is self-contained like plugins/email/mcp/scripts/sent-copy-sweep.js and
 * plugins/scheduling/mcp/scripts/reconcile-bookings.js: the Pi has no other
 * periodic surface, so the always-running platform/ui server spawns it on an
 * interval (see platform/ui/server/index.ts, the dream-cycle-sweep loop next to
 * calendar-reconcile). A PID lock prevents overlapping runs. stdio is inherited
 * so its [dream-cycle-sweep] and the phase runner's [dream-cycle] lines land in
 * the brand journal.
 *
 * The per-account 24h throttle is read from graph state, not a bookkeeping
 * file: an account whose most-recent dream-cycle :Report is inside the window is
 * skipped. This makes the frequent server tick idempotent without a scheduler
 * entry (decideSweepAction, dream-cycle-sweep-decision.ts). The seven phases and
 * the :Report write are the existing memoryDreamRun orchestrator; this script
 * only enumerates, throttles, and calls it.
 *
 * Deterministic end to end: no LLM, no API, no channel, no agent turn, no Claude
 * credential. The noisy, opt-in, mailbox-dependent half is Task 1945.
 *
 *   PLATFORM_ROOT=... NEO4J_URI=... node dist/scripts/dream-cycle-sweep.js
 */
export {};
//# sourceMappingURL=dream-cycle-sweep.d.ts.map