.last-branch

@@ -1 +1 @@
-v20260101-03-run-checks-page-guide-text
+v20260101-04-run-checks-guide-layout-fix

containers/backupchecks/src/templates/main/run_checks.html

@@ -1,5 +1,11 @@
 
-<div class="info-block">
+
+{% extends "layout/base.html" %}
+
+{% block content %}
+<div class="mb-3">
+  <div class="info-block" style="max-width: 100%; margin-bottom: 1rem;">
+
     <h3>Run Checks workflow</h3>
     <p>
         The Run Checks page is used for daily operational triage. It lists job runs that need attention so they can be reviewed,
@@ -21,10 +27,10 @@
         By consistently reviewing runs and documenting follow-up where needed, the Run Checks page provides both operational focus
         and auditable proof that backups are being checked.
     </p>
-</div>
-{% extends "layout/base.html" %}
 
-{% block content %}
+  </div>
+</div>
+
 <div class="d-flex align-items-center justify-content-between flex-wrap gap-2 mb-3">
   <h2 class="mb-0">Run Checks</h2>
   <div class="d-flex align-items-center gap-2">

docs/changelog.md

@@ -116,6 +116,15 @@
 - 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.
 
+---
+
+## v20260101-04-run-checks-guide-layout-fix
+
+- Moved the Run Checks workflow guide into the main page content so it aligns with the left edge of the table.
+- Reduced vertical spacing below the guide to remove excessive empty space before the Run Checks table.
+- Ensured the guide follows the same layout and alignment as the existing Run Checks page elements.
+- Applied layout-only changes without modifying any functional behavior.
+
 ================================================================================================================================================
 ## v0.1.14