Put the AI toggles and findings on the pages they act on

The five AI_ASSIST_ switches and the findings they produce were reachable only
from the AI tab, which is a long way from the page a finding is about.

Nothing was synchronised because nothing needed to be: findings are one file per
finding, and every surface is a view over that store with actions going to the
same endpoint. Acting on the Watchdog tab shows on the AI tab because they are
not two copies. The strip reloads rather than editing its own row, which is the
only way they could have drifted apart.

Each strip shows one page's kinds. Actions are whatever the server offers for
that row, so Move appears on media findings without this card knowing what a
move is.
This commit is contained in:
Gmer4Lfe
2026-08-14 22:32:55 -04:00
parent a705aa36b7
commit 90774f1442
3 changed files with 96 additions and 0 deletions
+8
View File
@@ -253,6 +253,14 @@ $_vv_wd_installed = vv_wd_installed_containers();
// only from the Settings tab's catch-all, which is a long way to go for a setting named
// after the page you are already looking at.
vv_conf_ui_card('vv-cf-watchdog', 'watchdog', 'Watchdog settings');
// The same AI switches the AI tab carries, on the page they act on. One conf value behind both,
// written through the same guarded path, so the two cards cannot disagree — a toggle flipped here
// is flipped there because there is only one of it.
vv_conf_ui_card('vv-cf-wd-ai', 'AI Feature Toggles', 'AI features');
// Findings this page's watchdogs produced, actionable here rather than only on the AI tab.
vv_ai_findings_strip('vv-wd-fnd', ['watchdog_strike'], 'Watchdog findings');
?>
<script>
(function() {