admin a18b18e5de docs: correct inflight.go's DEFERS claim (F-A1) ...

The gate's behaviour is correct and unchanged. The comment said 'a caller that
cannot acquire DEFERS to its next cadence' — true of the restore-test caller,
NOT of the backup caller, and it did not say so. The controller recorded the
refusal as a tier failure and emailed the operator; fixed controller-side in
v0.179.0. Comment only, no behaviour change.

2026-07-28 08:50:23 +02:00

..

archive_completeness_test.go

F-CRIT-2: a failed backup must not look like a fresh one (v0.106.0)

2026-07-28 07:47:22 +02:00

backup_test.go

R-85 Phase 1: the restore-test spec is built PER RUN, not frozen at daemon start

2026-07-26 20:47:28 +02:00

doc.go

v0.6.0-rc1: slice 6 Phase A — backup + the self-restore-test (local target)

2026-06-09 13:49:39 +02:00

inflight.go

docs: correct inflight.go's DEFERS claim (F-A1)

2026-07-28 08:50:23 +02:00

prune_test.go

agent v0.51.0: local vzdump retention default (--prune-backups keep-last=3)

2026-06-30 19:44:07 +02:00

restoretest_state.go

R-85 Phase 2: tier rotation, persisted state, one heavy op at a time

2026-07-26 21:00:42 +02:00

rotation_test.go

R-85 Phase 2: tier rotation, persisted state, one heavy op at a time

2026-07-26 21:00:42 +02:00

runner_snapshot_test.go

agent v0.51.0: local vzdump retention default (--prune-backups keep-last=3)

2026-06-30 19:44:07 +02:00

runner.go

F-CRIT-2: a failed backup must not look like a fresh one (v0.106.0)

2026-07-28 07:47:22 +02:00

schedule_spec_test.go

R-85 Phase 1: the restore-test spec is built PER RUN, not frozen at daemon start

2026-07-26 20:47:28 +02:00

schedule.go

R-85 Phase 2: tier rotation, persisted state, one heavy op at a time

2026-07-26 21:00:42 +02:00

store.go

v0.6.0-rc1: slice 6 Phase A — backup + the self-restore-test (local target)

2026-06-09 13:49:39 +02:00