Gmer4Lfe
96d8a5e3f0
Make a file earn its deletion over consecutive runs, so a partial classification failure too small to trip the tracked-count gate cannot remove anything
2026-08-26 17:58:42 -04:00
Gmer4Lfe
0431e720de
A cap that aborts cannot drain a backlog bigger than itself, so make it a per-run budget and let the queue clear over consecutive nights
2026-08-26 17:55:21 -04:00
Gmer4Lfe
7f4921de49
Give the wizard an assistant scoped to the step you are actually stuck on, so a first-run question can say "this" and mean something
2026-08-26 17:31:52 -04:00
Gmer4Lfe
d4c19baa32
Folding the Scheduler dock into the shared chat left its scope behind, so the troubleshooter has been diagnosing without the log tail for whatever was open
2026-08-26 17:25:28 -04:00
Gmer4Lfe
d444fd8036
A path with an apostrophe broke the remote shell quoting and a big file outran the connect timeout, so intact backups were reported corrupt and absent
2026-08-25 21:30:57 -04:00
Gmer4Lfe
d42b1e2dda
ffprobe exit 0 with a chapter-track warning is not corruption; guard the delete path against a detector that is wrong at scale
2026-08-25 18:29:43 -04:00
Gmer4Lfe
9492dc4c39
dig names the resolver it could not reach in its error text, so a DNS timeout was scraped as the answer and restarted DDNS over nothing
2026-08-25 18:29:43 -04:00
Gmer4Lfe
172beca3c5
A state key is a file path, not a regex — a release tag like [Bluray-1080p] holds an invalid range, so grep bailed and the tempfile swap wiped every other entry
2026-08-25 18:29:43 -04:00
Gmer4Lfe
f0c1289519
Let the file own why the row cap is conditional; the README states that it is
2026-08-25 17:21:20 -04:00
Gmer4Lfe
128172d3a8
The row counts below four columns were the naive division, not what the board does
2026-08-25 17:21:20 -04:00
Gmer4Lfe
820e8325a6
Docs: the row-height cap is conditional now, and the board's narrow-screen behaviour was nowhere in the page help
2026-08-25 17:15:20 -04:00
Gmer4Lfe
74c6a0f5eb
Monitor: hold the System card to the Network card's height below eight columns, where the two stop sharing a row
2026-08-25 17:07:18 -04:00
Gmer4Lfe
d289a9101c
Monitor: cap the System card's Varaverk block so the host figures set the card's height, not the sum of both
2026-08-25 17:01:52 -04:00
Gmer4Lfe
9553ecb16a
The two functions the row-overflow hatch added were not in EXPORTS
2026-08-25 17:01:10 -04:00
Gmer4Lfe
fb104bf05a
Monitor: a rung taller than one screen sizes rows to content, since the page scrolls there anyway and the cap only clipped cards
2026-08-25 16:54:19 -04:00
Gmer4Lfe
f4adc31215
Close the last four headers, and say what the destructive tools refuse to do
2026-08-25 16:51:14 -04:00
Gmer4Lfe
c6254f2342
The dev checkers documented themselves under headings nothing else uses
2026-08-25 16:45:39 -04:00
Gmer4Lfe
d25b147a56
A CLI tool has runtime modes, not a request
2026-08-25 16:42:39 -04:00
Gmer4Lfe
1f9915f074
Fill the single missing section in three scripts that had everything else
2026-08-25 16:41:06 -04:00
Gmer4Lfe
c0e7a97a56
Document what the cert and auth sweeps will not do
2026-08-25 16:39:01 -04:00
Gmer4Lfe
68c835f33b
Document what the proxy and cert collectors guarantee
2026-08-25 16:37:25 -04:00
Gmer4Lfe
6b9fda76db
Say how the spawned tools are actually invoked
2026-08-25 16:34:02 -04:00
Gmer4Lfe
1be259b66d
Two AI includes documented themselves under names nothing else uses
2026-08-25 16:31:43 -04:00
Gmer4Lfe
2c3c88d067
Say what the include layer exports and what it reads from conf
2026-08-25 16:29:57 -04:00
Gmer4Lfe
3fc14d16bf
A worker that is spawned has arguments, not runtime modes
2026-08-25 16:25:55 -04:00
Gmer4Lfe
4cc50889d6
Document the api layer's operational models, and fix two headers that had gone stale against the code
2026-08-25 16:25:55 -04:00
Gmer4Lfe
63e68740b6
Put the header sections back in the order the other 116 scripts use
2026-08-25 16:19:19 -04:00
Gmer4Lfe
f2fddeb87d
The reboot path's container stops were unbounded, and stopped a different list than it restored
2026-08-24 20:22:55 -04:00
Gmer4Lfe
eda411c0be
Give the PHP layer somewhere to record what it swallowed
2026-08-24 18:51:36 -04:00
Gmer4Lfe
492757ce70
Walk appdata once for the space check, and refuse to export when it cannot be measured
2026-08-24 18:46:26 -04:00
Gmer4Lfe
b58282b3d6
Read a filesystem once where two probes were answering the same question
2026-08-24 18:46:26 -04:00
Gmer4Lfe
9da2760a42
A localStorage guard was covering the layout restore it wrapped
2026-08-24 18:42:34 -04:00
Gmer4Lfe
049f633667
Bound the watchdogs' docker calls — a hung daemon is what they exist to catch
2026-08-24 18:39:59 -04:00
Gmer4Lfe
84946ed0c6
clear_logs previewed on one size basis and cleared on another
2026-08-24 18:36:29 -04:00
Gmer4Lfe
514e13660c
Give the bash side the disk helpers it never had, reporting the same unit as vv_df
2026-08-24 18:36:29 -04:00
Gmer4Lfe
9333334b7b
Bound the two tailscale lookups that were missed when the others were
2026-08-24 18:33:40 -04:00
Gmer4Lfe
367d0203b8
Find guards wired onto a helper that can never return non-zero
2026-08-24 18:22:59 -04:00
Gmer4Lfe
37017882c7
Check the header standard now that it is written down rather than implied
2026-08-24 18:22:59 -04:00
Gmer4Lfe
f116a1584e
Offboard reported a stack cleanup that could not fail and, on one path, had not run
2026-08-24 18:22:59 -04:00
Gmer4Lfe
1a5bacce87
Point the webhook's dependency note at where the handler actually lives
2026-08-24 18:22:59 -04:00
Gmer4Lfe
f6e5f7dcd6
Drop the remote-metrics endpoint nothing called and api/monitor.php already served
2026-08-24 18:22:59 -04:00
Gmer4Lfe
0f0c407458
Arrange and folder saves reported failure on every success, and split a move across two writes
2026-08-24 18:22:59 -04:00
Gmer4Lfe
354992c9e7
Keep a script's arguments and trailing comment when it moves between orchestrators
2026-08-24 18:22:59 -04:00
Gmer4Lfe
28987240aa
Let a sync window take a whole share in one click
...
The window editor is path-first, which is exact but slow for the case that is nearly all of them.
The chips only offer whole shares; a subpath already in the window marks its share partial rather
than offering to widen it, and the path box stays the only way to express a subpath or a profile.
2026-08-23 17:16:24 -04:00
Gmer4Lfe
fbf2b92167
Drop containers that no longer exist from the conf lists, after three days absent
...
A removed container leaves its name behind in every list that named it, and those names go on
being acted upon — a watchdog waiting for a container docker has never heard of. Strikes rather
than a single miss, because a rebuild makes a container vanish for a moment; and the lists naming
containers on the REMOTE are excluded, since pruning those against local docker would empty them.
2026-08-23 16:54:53 -04:00
Gmer4Lfe
206a119a4b
Show each container's fallback tier on the Monitor board
...
The row's left border carries it rather than the status dot, which already means running or
stopped.
2026-08-23 16:38:58 -04:00
Gmer4Lfe
671e7ea5a4
Make fallback coverage something that can actually happen, and say so on the page
...
fallback.sh starts covered containers with docker start and never creates them, so a coverage list
the partner has never been sent is a promise nothing can keep — all twelve were missing. Adds the
push and remove paths, a readiness card that checks rather than infers, and the fallback state the
assistant needs to answer for it.
2026-08-23 16:38:58 -04:00
Gmer4Lfe
d5cf3db2ec
Close every orchestrator the same way, and make skipped work a visible outcome
...
A gated-off section left nothing failed, so the weekly could run for hours and report "all
complete" beside "0 shares synced"; skipped is now derived from what was expected rather than
self-reported, and the verdict degrades to PARTIAL instead of flattering.
2026-08-23 16:38:58 -04:00
Gmer4Lfe
dc8823724d
Let the GPU transform actually run when deploying to a partner
...
The detection pattern starts with --, so grep parsed it as an option and exited 2; the negation
made the early return always true and every XML was deployed untransformed, keeping the owner's
NVIDIA device UUID on hosts that have no such card.
2026-08-23 16:38:58 -04:00
Gmer4Lfe
a392108562
Warn before a transfer when a disk backing the remote share is nearly full
...
Online is not writable: check_remote_disks confirmed each backing disk was mounted and healthy but
never how full it was, and rsync answers a full destination by stalling rather than failing.
2026-08-23 10:15:54 -04:00
Gmer4Lfe