@camstack/system 1.2.390 → 1.2.391

package/dist/builtins/backup-orchestrator/backup-orchestrator.addon.d.ts

@@ -1,272 +1,273 @@
-import { ProviderRegistration, BaseAddon } from '@camstack/types';
+import type { ProviderRegistration } from "@camstack/types";
+import { BaseAddon } from "@camstack/types";
 export declare class BackupOrchestratorAddon extends BaseAddon<Record<string, never>> {
-    private systemBackup;
-    private policies;
-    private schedules;
-    /** Backup encryption keys — PUBLIC keys only (see encryption-key-store.ts). */
-    private encryptionKeys;
-    private warnedNoEncryptionStore;
-    private dataDir;
-    /**
-     * Transient build buffer for archive fan-out. The tar is built here
-     * ONCE, streamed to every destination via the storage cap's chunked
-     * upload, then removed. Lives at `<nodeDataDir>/backup-staging` —
-     * OUTSIDE every backed-up location, so a backup can never contain a
-     * backup (the old `ctx.dataDir/staging` sat inside `addons-data` and
-     * compounded 175M → 4.5G before Jul 28), and distinct from
-     * `<nodeDataDir>/backups` where the default `backups` destination
-     * seeds when `CAMSTACK_BACKUP_ROOT` is unset. See staging-paths.ts.
-     */
-    private stagingDir;
-    private scheduleTimer;
-    /** Guards the disarmed-scheduler complaint to once per process. */
-    private warnedSchedulerDisarmed;
-    /**
-     * Baseline used as the "after" anchor when a schedule has a cron but
-     * has never fired yet (no `lastAttemptAt`). Set on orchestrator boot so a
-     * pattern that fires every minute doesn't immediately replay every
-     * historical "missed" run from epoch 0.
-     */
-    private scheduleBaselineAt;
-    private readonly manifestLock;
-    /**
-     * Global execution queue — at most ONE archive build at a time,
-     * cluster-node-wide (D342). Replaces the earlier invisible
-     * single-flight `buildLock`: same serialisation guarantee (two
-     * schedules due one tick apart built 8.2 GB + 3.7 GB side by side on
-     * the hub, 2026-09-04), but every run is now observable via
-     * `listRuns`, joinable when identical, and cancellable mid-stream.
-     */
-    private runQueue;
-    constructor();
-    protected onInitialize(): Promise<ProviderRegistration[]>;
-    protected onShutdown(): Promise<void>;
-    /**
-     * Aggregate destinations from `api.storage.listLocations({ type: 'backups' })`
-     * joined with the per-destination policy table. New locations get an
-     * `ensureDefault` policy seeded transparently (enabled=true,
-     * retentionCount=defaultRetentionCount). Pre-existing operator-edited
-     * policies are preserved by the `ensureDefault` idempotency.
-     */
-    private listDestinations;
-    /**
-     * Join the enabled schedules by the locations they fan out to.
-     * Comma-joined crons (a location can be targeted by several schedules),
-     * earliest next firing. Computed from `Date.now()` — an operator asking
-     * "when next" means from now, never from a stale run cursor.
-     */
-    private cadenceByLocation;
-    private fetchBackupLocations;
-    /**
-     * Load every persisted policy and key it by `locationId`, while
-     * lazily seeding a default for any `locationId` we haven't seen
-     * before. Idempotent — `ensureDefault` no-ops on already-persisted
-     * rows. Falls back to the in-memory default policy when the policy
-     * service isn't wired (no settings-store backend available).
-     */
-    private loadPoliciesIndexed;
-    private fallbackPolicy;
-    private toDestinationWire;
-    /**
-     * Compute next-due ms-epoch for a cron, or `undefined` on parse error.
-     * Catches so a single malformed cron doesn't blank out the whole
-     * destinations list at the cap surface.
-     */
-    private safeNextDue;
-    /**
-     * Aggregate listing — read every `backups` location's `manifests.json`
-     * and return one wire entry per archive, tagged with `destinationId`.
-     * Failures on individual locations are logged and skipped so a single
-     * unreachable destination doesn't blank out the whole UI.
-     */
-    /**
-     * Bytes the archives occupy on each named location (D388).
-     *
-     * Summed from each location's own manifest — the record the uploader writes
-     * — so this never walks a filesystem and never stats a remote destination.
-     * A manifest that cannot be read contributes NOTHING and is logged: a
-     * destination that is temporarily unreachable must read back as unknown, not
-     * as an empty disk. A location holding no archives is omitted for the same
-     * reason it is omitted everywhere else — only the orchestrator can tell
-     * "nobody reported" from "reported nothing".
-     */
-    private backupOccupancy;
-    private aggregatedList;
-    private stagingPath;
-    /**
-     * Boot-time staging hygiene. Sweeps the staging dir (sparing an
-     * archive a pending-restore marker references — the boot hook has
-     * not consumed it yet), then reports — without touching — the LEGACY
-     * staging dir inside `addons-data`, where pre-move leaks live. The
-     * legacy dir held 5.1 GB on the hub; deleting operator-visible
-     * gigabytes silently is not this addon's call, so it warns with the
-     * footprint instead.
-     */
-    private cleanStagingArea;
-    /**
-     * Trigger a backup run through the global execution queue (D342):
-     * at most one archive build at a time, a trigger that arrives while
-     * one is in flight WAITS (or joins an identical queued run), and the
-     * result says which happened. The call still resolves when the run
-     * terminates; a cancelled run resolves with `cancelled: true` and
-     * whatever entries landed before the stop — a deliberate operator
-     * cancel is an outcome, not an error.
-     */
-    private triggerBackup;
-    /** Wire `backup.listRuns` — queued + active + bounded history. */
-    private listRuns;
-    /**
-     * Wire `backup.cancel`. Delegates to the queue: a queued run is
-     * removed before it starts; the running run's abort signal fires and
-     * `runBackupBuild` stops the tar/upload streams and deletes its
-     * staging archive on the way out.
-     */
-    private cancelRun;
-    /**
-     * Execute ONE backup run — only ever called by the queue, never
-     * directly (the queue is the single serialisation authority).
-     * Builds the archive in the private staging dir, then pushes it to
-     * every selected destination via the storage cap's chunked upload
-     * protocol. Per-destination errors are logged and recorded on the
-     * run — one bad sink doesn't kill the run.
-     *
-     * Cleanup contract (D342): the staging file is deleted in `finally`,
-     * which covers success, per-destination failure, build failure AND
-     * cancellation alike. The only leak this cannot cover — the process
-     * dying inside the run — is reclaimed by the boot sweep in
-     * `cleanStagingArea`.
-     */
-    private runBackupBuild;
-    /**
-     * THIS node's database owner (D693), reached through `database-snapshot`
-     * pinned to the local node: the paths it answers must be on this host,
-     * because this process archives them. No local node id means no pin, and an
-     * unpinned singleton call could be answered by another host — refuse.
-     */
-    private databaseOwner;
-    /**
-     * Push the staged archive to a single destination via chunked
-     * upload, then update the per-location manifest. Applies the
-     * destination's retention policy as part of the same lock-protected
-     * manifest mutation so the deletes never race with a concurrent
-     * append.
-     *
-     * Throws on upload / manifest failure — caller logs and continues to
-     * the next destination so a single bad sink doesn't fail the run.
-     */
-    private uploadAndIndex;
-    /**
-     * List archives at a single destination — newest-first. Reads only
-     * the per-location `manifests.json` (no per-archive tarball read);
-     * the orchestrator already snapshots each archive's locations into
-     * the manifest at upload time.
-     */
-    private listArchives;
-    /**
-     * Upsert the per-destination policy row. Used by the admin-UI
-     * destinations table — toggle enabled / change retention / set
-     * label. No-ops with a logged warning if the
-     * settings backend lacks structured-table support (no persistence
-     * available).
-     *
-     * There is deliberately NO cadence here. A destination does not run on
-     * its own timer — a schedule fans out to it — and the `cron` this method
-     * used to accept had scheduled nothing since 2026-07-28 while still being
-     * rendered as "daily at 03:00" (D384, and D62's "a switch that writes a
-     * store nobody reads").
-     */
-    private upsertDestinationPolicy;
-    /**
-     * Validate a cron expression and peek the next N firing times. The
-     * admin UI's CronEditor calls this on every keystroke (debounced)
-     * to render a live "next-run" preview — invalid expressions surface
-     * the parse error inline instead of waiting for save.
-     */
-    private previewSchedule;
-    private getEntries;
-    private deleteArchive;
-    /**
-     * Schedule a restore for the next boot. Pulls the archive bytes
-     * down from the destination's storage location via the chunked-
-     * download protocol into the private staging dir, then writes the
-     * usual restore marker against the staged path so the boot-time
-     * apply hook (in server-backend launcher) extracts before any
-     * addon starts.
-     *
-     * `locations` (optional) is propagated into the marker as a
-     * whitelist — only those top-level locations get extracted.
-     */
-    private scheduleRestore;
-    private requireEncryptionKeys;
-    /**
-     * The key a run encrypts to; `null` = encryption off. THROWS when the
-     * setting cannot be read — a run must fail rather than ship a plain archive
-     * an operator asked to be encrypted.
-     */
-    private activeEncryptionKey;
-    private getEncryption;
-    private setupEncryption;
-    private disableEncryption;
-    private checkBackupKey;
-    /**
-     * Resolve a target destination set — see {@link selectBackupTargets} for the
-     * rule. Caller-provided list wins over the per-destination policy flag;
-     * NEITHER wins over `StorageLocation.enabled`, which is the operator's
-     * switch on the storage screen and the only one that means "this disk takes
-     * no writes" (D62).
-     *
-     * Reads locations + policies directly rather than going through
-     * `listDestinations()`: that method also reads every destination's
-     * `manifests.json` to hydrate `lastSuccess`, which target resolution has no
-     * use for and which cost one round-trip per destination on every trigger.
-     */
-    private resolveTargets;
-    /**
-     * Persist the outcome of one attempted write to one destination.
-     *
-     * Best-effort by design: an unavailable settings backend must not turn a
-     * successful backup into a failed one. But it is LOGGED when it cannot be
-     * written — a status field that silently stops being updated is the whole
-     * defect this method exists to close.
-     */
-    private recordDestinationOutcome;
-    private startScheduleTimer;
-    private stopScheduleTimer;
-    /**
-     * Schedule-driven backup scheduling. Walks every enabled backup
-     * SCHEDULE (the N:M entry), computes the next due time after
-     * `lastAttemptAt` (or the orchestrator's first-tick baseline if never
-     * run), and fires a SINGLE archive fanned out to ALL of the
-     * schedule's `locationIds` when due — with the schedule's per-entry
-     * retention applied to each. Each schedule keeps its own cadence.
-     *
-     * Errors per schedule are isolated; one misconfigured cron doesn't
-     * block the others. The schedule's `lastAttemptAt` is updated BEFORE the
-     * trigger to dedupe (the tick runs every SCHEDULE_TICK_MS — without
-     * the up-front update a long-running upload could overlap with the
-     * next tick's same-due check).
-     */
-    private onScheduleTick;
-    /**
-     * Fire one schedule and RECORD what happened to it, naming every
-     * destination. Three outcomes, three different persisted states —
-     * because "fired" and "backed up" were the same field until D384:
-     *
-     *   - archive landed somewhere → `lastSuccessAt`, `lastError` cleared;
-     *   - the run threw, or landed nowhere → `lastError`, no success stamp;
-     *   - the stamp could not be written → logged, named, not swallowed.
-     */
-    private runScheduledBackup;
-    private listSchedules;
-    private upsertSchedule;
-    private deleteSchedule;
-    private resolveScheduleService;
-    private resolvePolicyService;
-    /**
-     * Narrow `ctx.api.storage` to the subset the manifest helpers need.
-     * Lets the helpers be unit-tested with a Map-backed fake without
-     * pulling in the full `AddonApi` shape.
-     */
-    private storageApi;
+	private systemBackup;
+	private policies;
+	private schedules;
+	/** Backup encryption keys — PUBLIC keys only (see encryption-key-store.ts). */
+	private encryptionKeys;
+	private warnedNoEncryptionStore;
+	private dataDir;
+	/**
+	* Transient build buffer for archive fan-out. The tar is built here
+	* ONCE, streamed to every destination via the storage cap's chunked
+	* upload, then removed. Lives at `<nodeDataDir>/backup-staging` —
+	* OUTSIDE every backed-up location, so a backup can never contain a
+	* backup (the old `ctx.dataDir/staging` sat inside `addons-data` and
+	* compounded 175M → 4.5G before Jul 28), and distinct from
+	* `<nodeDataDir>/backups` where the default `backups` destination
+	* seeds when `CAMSTACK_BACKUP_ROOT` is unset. See staging-paths.ts.
+	*/
+	private stagingDir;
+	private scheduleTimer;
+	/** Guards the disarmed-scheduler complaint to once per process. */
+	private warnedSchedulerDisarmed;
+	/**
+	* Baseline used as the "after" anchor when a schedule has a cron but
+	* has never fired yet (no `lastAttemptAt`). Set on orchestrator boot so a
+	* pattern that fires every minute doesn't immediately replay every
+	* historical "missed" run from epoch 0.
+	*/
+	private scheduleBaselineAt;
+	private readonly manifestLock;
+	/**
+	* Global execution queue — at most ONE archive build at a time,
+	* cluster-node-wide (D342). Replaces the earlier invisible
+	* single-flight `buildLock`: same serialisation guarantee (two
+	* schedules due one tick apart built 8.2 GB + 3.7 GB side by side on
+	* the hub, 2026-09-04), but every run is now observable via
+	* `listRuns`, joinable when identical, and cancellable mid-stream.
+	*/
+	private runQueue;
+	constructor();
+	protected onInitialize(): Promise<ProviderRegistration[]>;
+	protected onShutdown(): Promise<void>;
+	/**
+	* Aggregate destinations from `api.storage.listLocations({ type: 'backups' })`
+	* joined with the per-destination policy table. New locations get an
+	* `ensureDefault` policy seeded transparently (enabled=true,
+	* retentionCount=defaultRetentionCount). Pre-existing operator-edited
+	* policies are preserved by the `ensureDefault` idempotency.
+	*/
+	private listDestinations;
+	/**
+	* Join the enabled schedules by the locations they fan out to.
+	* Comma-joined crons (a location can be targeted by several schedules),
+	* earliest next firing. Computed from `Date.now()` — an operator asking
+	* "when next" means from now, never from a stale run cursor.
+	*/
+	private cadenceByLocation;
+	private fetchBackupLocations;
+	/**
+	* Load every persisted policy and key it by `locationId`, while
+	* lazily seeding a default for any `locationId` we haven't seen
+	* before. Idempotent — `ensureDefault` no-ops on already-persisted
+	* rows. Falls back to the in-memory default policy when the policy
+	* service isn't wired (no settings-store backend available).
+	*/
+	private loadPoliciesIndexed;
+	private fallbackPolicy;
+	private toDestinationWire;
+	/**
+	* Compute next-due ms-epoch for a cron, or `undefined` on parse error.
+	* Catches so a single malformed cron doesn't blank out the whole
+	* destinations list at the cap surface.
+	*/
+	private safeNextDue;
+	/**
+	* Aggregate listing — read every `backups` location's `manifests.json`
+	* and return one wire entry per archive, tagged with `destinationId`.
+	* Failures on individual locations are logged and skipped so a single
+	* unreachable destination doesn't blank out the whole UI.
+	*/
+	/**
+	* Bytes the archives occupy on each named location (D388).
+	*
+	* Summed from each location's own manifest — the record the uploader writes
+	* — so this never walks a filesystem and never stats a remote destination.
+	* A manifest that cannot be read contributes NOTHING and is logged: a
+	* destination that is temporarily unreachable must read back as unknown, not
+	* as an empty disk. A location holding no archives is omitted for the same
+	* reason it is omitted everywhere else — only the orchestrator can tell
+	* "nobody reported" from "reported nothing".
+	*/
+	private backupOccupancy;
+	private aggregatedList;
+	private stagingPath;
+	/**
+	* Boot-time staging hygiene. Sweeps the staging dir (sparing an
+	* archive a pending-restore marker references — the boot hook has
+	* not consumed it yet), then reports — without touching — the LEGACY
+	* staging dir inside `addons-data`, where pre-move leaks live. The
+	* legacy dir held 5.1 GB on the hub; deleting operator-visible
+	* gigabytes silently is not this addon's call, so it warns with the
+	* footprint instead.
+	*/
+	private cleanStagingArea;
+	/**
+	* Trigger a backup run through the global execution queue (D342):
+	* at most one archive build at a time, a trigger that arrives while
+	* one is in flight WAITS (or joins an identical queued run), and the
+	* result says which happened. The call still resolves when the run
+	* terminates; a cancelled run resolves with `cancelled: true` and
+	* whatever entries landed before the stop — a deliberate operator
+	* cancel is an outcome, not an error.
+	*/
+	private triggerBackup;
+	/** Wire `backup.listRuns` — queued + active + bounded history. */
+	private listRuns;
+	/**
+	* Wire `backup.cancel`. Delegates to the queue: a queued run is
+	* removed before it starts; the running run's abort signal fires and
+	* `runBackupBuild` stops the tar/upload streams and deletes its
+	* staging archive on the way out.
+	*/
+	private cancelRun;
+	/**
+	* Execute ONE backup run — only ever called by the queue, never
+	* directly (the queue is the single serialisation authority).
+	* Builds the archive in the private staging dir, then pushes it to
+	* every selected destination via the storage cap's chunked upload
+	* protocol. Per-destination errors are logged and recorded on the
+	* run — one bad sink doesn't kill the run.
+	*
+	* Cleanup contract (D342): the staging file is deleted in `finally`,
+	* which covers success, per-destination failure, build failure AND
+	* cancellation alike. The only leak this cannot cover — the process
+	* dying inside the run — is reclaimed by the boot sweep in
+	* `cleanStagingArea`.
+	*/
+	private runBackupBuild;
+	/**
+	* THIS node's database owner (D693), reached through `database-snapshot`
+	* pinned to the local node: the paths it answers must be on this host,
+	* because this process archives them. No local node id means no pin, and an
+	* unpinned singleton call could be answered by another host — refuse.
+	*/
+	private databaseOwner;
+	/**
+	* Push the staged archive to a single destination via chunked
+	* upload, then update the per-location manifest. Applies the
+	* destination's retention policy as part of the same lock-protected
+	* manifest mutation so the deletes never race with a concurrent
+	* append.
+	*
+	* Throws on upload / manifest failure — caller logs and continues to
+	* the next destination so a single bad sink doesn't fail the run.
+	*/
+	private uploadAndIndex;
+	/**
+	* List archives at a single destination — newest-first. Reads only
+	* the per-location `manifests.json` (no per-archive tarball read);
+	* the orchestrator already snapshots each archive's locations into
+	* the manifest at upload time.
+	*/
+	private listArchives;
+	/**
+	* Upsert the per-destination policy row. Used by the admin-UI
+	* destinations table — toggle enabled / change retention / set
+	* label. No-ops with a logged warning if the
+	* settings backend lacks structured-table support (no persistence
+	* available).
+	*
+	* There is deliberately NO cadence here. A destination does not run on
+	* its own timer — a schedule fans out to it — and the `cron` this method
+	* used to accept had scheduled nothing since 2026-07-28 while still being
+	* rendered as "daily at 03:00" (D384, and D62's "a switch that writes a
+	* store nobody reads").
+	*/
+	private upsertDestinationPolicy;
+	/**
+	* Validate a cron expression and peek the next N firing times. The
+	* admin UI's CronEditor calls this on every keystroke (debounced)
+	* to render a live "next-run" preview — invalid expressions surface
+	* the parse error inline instead of waiting for save.
+	*/
+	private previewSchedule;
+	private getEntries;
+	private deleteArchive;
+	/**
+	* Schedule a restore for the next boot. Pulls the archive bytes
+	* down from the destination's storage location via the chunked-
+	* download protocol into the private staging dir, then writes the
+	* usual restore marker against the staged path so the boot-time
+	* apply hook (in server-backend launcher) extracts before any
+	* addon starts.
+	*
+	* `locations` (optional) is propagated into the marker as a
+	* whitelist — only those top-level locations get extracted.
+	*/
+	private scheduleRestore;
+	private requireEncryptionKeys;
+	/**
+	* The key a run encrypts to; `null` = encryption off. THROWS when the
+	* setting cannot be read — a run must fail rather than ship a plain archive
+	* an operator asked to be encrypted.
+	*/
+	private activeEncryptionKey;
+	private getEncryption;
+	private setupEncryption;
+	private disableEncryption;
+	private checkBackupKey;
+	/**
+	* Resolve a target destination set — see {@link selectBackupTargets} for the
+	* rule. Caller-provided list wins over the per-destination policy flag;
+	* NEITHER wins over `StorageLocation.enabled`, which is the operator's
+	* switch on the storage screen and the only one that means "this disk takes
+	* no writes" (D62).
+	*
+	* Reads locations + policies directly rather than going through
+	* `listDestinations()`: that method also reads every destination's
+	* `manifests.json` to hydrate `lastSuccess`, which target resolution has no
+	* use for and which cost one round-trip per destination on every trigger.
+	*/
+	private resolveTargets;
+	/**
+	* Persist the outcome of one attempted write to one destination.
+	*
+	* Best-effort by design: an unavailable settings backend must not turn a
+	* successful backup into a failed one. But it is LOGGED when it cannot be
+	* written — a status field that silently stops being updated is the whole
+	* defect this method exists to close.
+	*/
+	private recordDestinationOutcome;
+	private startScheduleTimer;
+	private stopScheduleTimer;
+	/**
+	* Schedule-driven backup scheduling. Walks every enabled backup
+	* SCHEDULE (the N:M entry), computes the next due time after
+	* `lastAttemptAt` (or the orchestrator's first-tick baseline if never
+	* run), and fires a SINGLE archive fanned out to ALL of the
+	* schedule's `locationIds` when due — with the schedule's per-entry
+	* retention applied to each. Each schedule keeps its own cadence.
+	*
+	* Errors per schedule are isolated; one misconfigured cron doesn't
+	* block the others. The schedule's `lastAttemptAt` is updated BEFORE the
+	* trigger to dedupe (the tick runs every SCHEDULE_TICK_MS — without
+	* the up-front update a long-running upload could overlap with the
+	* next tick's same-due check).
+	*/
+	private onScheduleTick;
+	/**
+	* Fire one schedule and RECORD what happened to it, naming every
+	* destination. Three outcomes, three different persisted states —
+	* because "fired" and "backed up" were the same field until D384:
+	*
+	*   - archive landed somewhere → `lastSuccessAt`, `lastError` cleared;
+	*   - the run threw, or landed nowhere → `lastError`, no success stamp;
+	*   - the stamp could not be written → logged, named, not swallowed.
+	*/
+	private runScheduledBackup;
+	private listSchedules;
+	private upsertSchedule;
+	private deleteSchedule;
+	private resolveScheduleService;
+	private resolvePolicyService;
+	/**
+	* Narrow `ctx.api.storage` to the subset the manifest helpers need.
+	* Lets the helpers be unit-tested with a Map-backed fake without
+	* pulling in the full `AddonApi` shape.
+	*/
+	private storageApi;
 }
 export default BackupOrchestratorAddon;

package/dist/builtins/backup-orchestrator/cron-helpers.d.ts

@@ -1,23 +1,23 @@
 /**
- * Validate a cron expression and return its next firing time strictly
- * after `after`, expressed as ms-epoch. Returns `null` when the
- * expression has no future runs (croner returns null e.g. for
- * fully-bounded patterns that have already elapsed). Throws when the
- * expression is syntactically invalid — callers are expected to
- * surface that to the operator.
- */
+* Validate a cron expression and return its next firing time strictly
+* after `after`, expressed as ms-epoch. Returns `null` when the
+* expression has no future runs (croner returns null e.g. for
+* fully-bounded patterns that have already elapsed). Throws when the
+* expression is syntactically invalid — callers are expected to
+* surface that to the operator.
+*/
 export declare function computeNextDue(cron: string, after: number): number | null;
 /**
- * Validate without computing — returns true when `cron` parses, false
- * otherwise. Used by the cap-router input zod schema's `.refine`
- * callback to reject malformed expressions at the boundary instead
- * of at scheduler-tick time.
- */
+* Validate without computing — returns true when `cron` parses, false
+* otherwise. Used by the cap-router input zod schema's `.refine`
+* callback to reject malformed expressions at the boundary instead
+* of at scheduler-tick time.
+*/
 export declare function isValidCron(cron: string): boolean;
 /**
- * Peek the next N firing times after `after` (default: now). Used by
- * the admin UI's CronEditor preview pane — operators see the next
- * 3–5 runs as they edit the expression so a wrong pattern is
- * obvious before save.
- */
+* Peek the next N firing times after `after` (default: now). Used by
+* the admin UI's CronEditor preview pane — operators see the next
+* 3–5 runs as they edit the expression so a wrong pattern is
+* obvious before save.
+*/
 export declare function previewNextRuns(cron: string, count: number, after?: number): readonly number[];