fix(server): a locked audit retention also fixes the audit step and the switch

The audit retention in force ignored the audit clean-up's steps: with the
audit step unticked nothing was deleted, yet Settings › Logs still showed the
age limit. It is now 0 without that step, and setting a limit (Settings › Logs
or CHRONOS_AUDIT_RETENTION_DAYS at start) ticks the step again, so a saved or
fixed retention always takes effect. While the variable fixes a limit above 0,
an edit that drops the step is 409 setting_locked like turning the schedule off.

The admin panel's Scheduled tab disables what the variable fixes (the row's
switch, the form's Enabled and audit step, the age limit) with the locked
tooltip, and points a setting_locked refusal at the field actually refused.

The Copies kept tooltips now say the backups folder keeps as many copies as
the backup schedule that keeps the most; the LastDone and Newest comments
state the real first-copy rule; Keep audit is documented last-writer-wins.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Alby96andClaude Opus 5.5 committed 2026-10-27 10:39:49 +01:00
1 parent 94a5466c9f
commit e6e69782ed
12 files changed
+125 -45

No files matched your search

+3 -3
View File
@@ -46,9 +46,9 @@ public interface IScheduleHost
/// A host's system schedule: <paramref name="SystemKey"/> identifies it across starts (<c>archive-scan</c>,
/// <c>index-backup</c>, <c>housekeeping</c>…); the rest is what it is seeded with and reset to. <paramref name="Name"/> is
/// stored as given; clients show system schedules by their key in the user's language. <paramref name="LastDone"/> is when
/// the host last did this work before the schedule existed (the newest index copy, made by the timer the schedule
/// replaced): seeded a whole period or more later, the row is due at once, so the upgrade's first start does the work
/// as that timer would have; otherwise, and without it, the first run is the recurrence's first occurrence.
/// the host last did this work before the schedule existed (the newest index copy), read only when the row is seeded: an
/// enabled row seeded at least a whole period of its recurrence after it is due at once; otherwise, and without it, its
/// first run is the recurrence's first occurrence.
/// </summary>
public sealed record SystemSchedule(
string SystemKey,