-- Automatic check cycle (see docs/USAGE.md): optionally repeats the
-- "clear queue -> scan floating IPs -> wait for all checks to finish ->
-- wait interval" scenario. Singleton row, kept apart from `settings` so that
-- a full-overwrite PUT /config/orchestrator never resets these fields.
-- State is persisted so the cycle survives a control-api restart.

CREATE TABLE auto_cycle (
  id                   INTEGER PRIMARY KEY CHECK (id = 1),
  enabled              INTEGER NOT NULL DEFAULT 0,
  interval_seconds     INTEGER NOT NULL DEFAULT 3600,
  max_run_seconds      INTEGER NOT NULL DEFAULT 0,
  phase                TEXT NOT NULL DEFAULT 'idle',
  run_started_at       TIMESTAMP,
  next_run_at          TIMESTAMP,
  last_run_started_at  TIMESTAMP,
  last_run_finished_at TIMESTAMP,
  last_outcome         TEXT NOT NULL DEFAULT '',
  last_error           TEXT NOT NULL DEFAULT '',
  last_scanned_free    INTEGER NOT NULL DEFAULT 0,
  runs_total           INTEGER NOT NULL DEFAULT 0,
  updated_at           TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP
);

INSERT INTO auto_cycle (id, enabled, interval_seconds, max_run_seconds, phase) VALUES (1, 0, 3600, 0, 'idle');