Review proposed changes to our union contracts before each negotiation round.

Triggers

Define what kicks off an iteration. The kernel today supports one trigger — the operator clicking Run iteration on the Overview tab. The planned shape adds:

• Cron schedules — recurring iterations (e.g. weekly Monday 09:00) that run unattended; results land in the inbox for review.
• Webhook ingest — kick off an iteration when an upstream system (Slack, PagerDuty, your CI) signals a new batch is ready.
• Cluster-driven — a new failure cluster of severity ≥ medium triggers an iteration targeted at that cluster automatically.

The supporting kernel work (a triggers table + a scheduler reading it + a webhook receiver) lands when the first customer asks for unattended cadence; for now, manual is the only path.