From 9f42b8163e37b045bcd6bd4aabc2f7fce88b8bd6 Mon Sep 17 00:00:00 2001 From: Ivo Oskamp Date: Thu, 1 Jan 2026 16:41:02 +0100 Subject: [PATCH] Auto-commit local changes before build (2026-01-01 16:41:02) --- docs/changelog.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/changelog.md b/docs/changelog.md index a95cec6..ed3fce0 100644 --- a/docs/changelog.md +++ b/docs/changelog.md @@ -105,6 +105,17 @@ - Updated report generation logic to handle single-customer, multi-customer, and all-customer scopes. - Prepared reporting output for use cases such as account management and operations-wide overviews. +--- + +## v20260101-03-run-checks-page-guide-text + +- Added a workflow guide to the Run Checks page explaining its purpose in daily operational triage. +- Emphasized that the main objective is to keep the Run Checks page as empty as possible. +- Clarified that every run must be marked as reviewed to demonstrate that backups are actively checked. +- Explicitly stated that after adding a ticket number or remark, the run must still be marked as reviewed. +- Explained the role of the resolved status within the Run Checks workflow. +- Placed the guide directly on the Run Checks page (no popup), aligned with the dashboard explanation style. + ================================================================================================================================================ ## v0.1.14