fix(source): regenerate files_source.sh, which had gone stale

files_validation.sh exists in the tree but was missing from the generated
source-array, so eager loading never sourced it. Found while diffing the repo
against the live install, where the array had been regenerated in place and
carried the entry the committed one lacked.

Regenerated with generate_arrays.sh rather than copied back from the install, so
the committed array is what the generator actually produces.

containers/libreportal/frontend/components/apps/overview/js/overview-manager.js

@@ -748,9 +748,25 @@ class OverviewManager {
     const newer = a.newer_version
       ? `<span class="updater-badge updater-badge-unknown" title="You track ${esc(a.channel || '')} — ${esc(a.newer_version)} has been published. Change Version on the app's Advanced tab to move.">${esc(a.newer_version)} available</span>`
       : '';
+    // Two different actions, and the row shows whichever applies.
+    //
+    // `update` pulls a new image for the tag you already track — one click, low
+    // risk, primary styling.
+    //
+    // `upgrade` moves to a newer release LINE, which needs the pinned version
+    // changed and walks the releases one at a time. It used to live only inside
+    // the row detail, on the reasoning that it wants more care than a row button.
+    // But the care is already there: updater-page's upgrade() opens a confirmation
+    // spelling out the snapshot-per-step, the rollback behaviour and the likely
+    // duration, and nothing runs until that is accepted. Hiding the button bought
+    // no safety — it just left rows reading "CRITICAL · V1.159.0 AVAILABLE" with
+    // no way to act on them, which is exactly how it was reported. Secondary
+    // styling keeps the two visibly different.
     const updBtn = a.update_available
       ? `<button class="updater-btn updater-btn-primary" data-updater-action="update" data-app="${slug}">Update</button>`
-      : '';
+      : (a.newer_version
+        ? `<button class="updater-btn ov-upgrade-btn" data-updater-action="upgrade" data-app="${slug}" data-version="${esc(a.newer_version)}" title="Move to the ${esc(a.newer_version)} release line — you will be asked to confirm first">Upgrade to ${esc(a.newer_version)}</button>`
+        : '');
     // Only rows with something to apply are selectable. A checkbox on a row
     // that is already current would offer a choice with no outcome, and
     // "selected 6, updated 2" is a worse answer than not offering the 4.

scripts/source/files/arrays/files_source.sh

@@ -31,6 +31,7 @@ source_scripts=(
     "source/files/arrays/files_start.sh"
     "source/files/arrays/files_task.sh"
     "source/files/arrays/files_update.sh"
+    "source/files/arrays/files_validation.sh"
     "source/files/arrays/files_webui.sh"
     "source/files/arrays/function_manifest.sh"
     "source/files/generate_function_manifest.sh"