Change-gated schedules

Available in 0.1 (HTTP and file probes)

A plain cron schedule starts a run every time. For jobs like “look at this page”, “scan this registry” or “read this mailbox” most runs find nothing and still cost tokens.

A change gate adds a deterministic, model-free check in front of the run:

sources:
  - type: cron
    schedule: "0 * * * *"
    config:
      schedule: "0 * * * *"
      changeCheck:
        probe:
          type: http              # http | file | api | query | mcp-read
          url: https://status.example/api/summary
          jsonPointer: /version

API responses and queries are planned for 0.2.

• The probe result is hashed (or diffed) and compared with the digest of the previous run.
• Only if the digest differs does the run start and an event get emitted.
• The check result is written to the audit trail. The check itself costs no tokens.