bvandeusenandClaude Opus 5.5 e6da0ff299 feat(backup): a backup holds settings and keys only, for recovery (#5822) ...

#5822 "Backup contents: settings and keys only". The operator's ruling
(System 180, 2026-10-15) overturns 2026-10-12's "Config + audit + alerts":
a backup is for system recovery and carries what would otherwise have to
be set up again, with no logs or history.

- contents.py: audit_events, alert_events, alert_states, metric_anomalies,
  metric_anomaly_spans and user_invites move to EXCLUDED.
- Alert state is no longer restored, and evaluation skips a rule with no
  state row. ensure_rule_states (alerts/service.py) gives every
  single-resource rule lacking one an inactive row; alert_reconcile runs
  it each minute.
- Docs, the Backups page and the CLI help say what a backup holds now.
  CI's image check also finds the audit log empty after a restore.
- tests/integration/test_backup_restore_fixes.py is removed: its case (an
  alert event naming a left-out Ansible run) no longer arises. The SET NULL
  fix-up is covered by a unit test on synthetic tables.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-15 10:39:55 -04:00

..

__init__.py

chore: rename project Roundtable → Steward

2026-04-25 16:20:14 -04:00

episodes.py

feat(email): delivery you can see: each alert's email in history, outgoing email on Settings -> System (#5509)

2026-10-09 16:12:40 -04:00

routes.py

feat(anomalies): a metric out of its normal is an anomaly to review (#5740)

2026-10-14 13:41:57 -04:00

service.py

feat(backup): a backup holds settings and keys only, for recovery (#5822)

2026-10-15 10:39:55 -04:00