FailedProxy/Varaverk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove point-in-time HOST2 status from the codebase

Browse Source 
Comments asserting a partner is down, being rebuilt or not yet installed are true on the day they are written and wrong afterwards, and nothing prompts anyone to revisit them. Behaviour is described generically; current state belongs in operator memory, not in tracked files.
This commit is contained in:
Gmer4Lfe
2026-08-17 15:20:25 -04:00
parent e8ee5b052b
commit 0447fa6f86
11 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Plugin/unraid/include/ai_memory_learn.php
+1 -1
View File
@@ -194,7 +194,7 @@ function vv_ai_mem_append(string $text): array {
// Takes one line back out of the learned slot. The counterpart to vv_ai_mem_append(), and the
// reason a decided proposal can be changed at all: without this, "accepted" was a one-way door
// and the only way out was editing mem_learned.md by hand. An accepted line joins every future
// prompt, and a fact that is true today — HOST2 is offline — becomes actively wrong the day it
// prompt, and a fact that is true today — a host is unreachable — becomes actively wrong the day it
// stops being true, with nothing to expire it.
//
// Matched on the line this file wrote: "- <text> (<date>)". A line the operator has since edited