api-images box stats.php threshold fallback still 80; only the box .env carries 75
The box RUNTIME stats.php fallback for STORAGE_WARN_PERCENT is still 80, pre-a640b5a. The live threshold reads 75 only because nw-whey-cc set STORAGE_WARN_PERCENT=75 in the box .env by single-file lftp and /stats readback confirms thresholdPercent 75. So a clobbered, lost or rebuilt box .env lands straight back on 80 - 'fixed on the box' and 'fixed in the copy that survives losing the box .env' are two different states and only the first is true today. Closes when deploytohostinger.sh ships a640b5a's code default, verified by /stats readback of thresholdPercent, never by reading the file. Blocked on nw-whey-cc's 13-commit bundle run, itself gated on a frozen uploads/ snapshot plus Elazar's go; I hold no FTP deploy creds. Split out of EVO-58 2026-10-06 so this gap does not retire with that row - it is the one piece of api-images' share that is not live. Why it survived two months unnoticed: usage sits near 8.6%, far from both 75 and 80, so neither value has ever been approached and a threshold that is never approached cannot report its own staleness.
Activity
-
parent=#2116
-
nw-whey-cc's deploytohostinger.sh run of the waiting 13-commit bundle (gated on a frozen uploads/ snapshot + Elazar's go). Verified by reshelling the box 2026-10-06, not from a status field: the deployed install has no inc/idempotency.php and its log vocabulary carries neither ERASURE_* nor IDEMPOTENCY_*. coder-apiimages-cc holds no FTP deploy creds.
-
cleared: nw-whey-cc's deploytohostinger.sh run of the waiting 13-commit bundle (gated on a frozen uploads/ snapshot + Elazar's go). Verified by reshelling the box 2026-10-06, not from a status field: the deployed install has no inc/idempotency.php and its log vocabulary carries neither ERASURE_* nor IDEMPOTENCY_*. coder-apiimages-cc holds no FTP deploy creds.
-
CLOSED. Box stats.php line 184 reads $get('STORAGE_WARN_PERCENT','75') ?? '75' - both the arg default and the coalesce - and sha256 65827e71...4a09e matches local HEAD byte for byte. Deployed in the 79f6622 bundle 2026-10-06; blockedReason (nw-whey's run gated on a frozen uploads/ snapshot) is void, the snapshot gate was removed as a control that could not fail and the deploy ran. READ THE EVIDENCE NARROWLY, because this row's OWN stated closure criterion could not have proven it. It said 'verified by /stats readback of thresholdPercent, never by reading the file'. That criterion is unable to discriminate here: /stats serves the .env value, and the box .env has carried 75 since 2026-09-11, so the readback answered 75 for 25 days while the code default was still 80 - it would have answered 75 on the day this row was filed. The thing this row tracked is observable ONLY by reading the deployed code, or by losing the .env, which nobody will do deliberately. So it is closed on the file read plus the sha256, deliberately against its own criterion. A readback is the right instrument for a VALUE and the wrong one for a FALLBACK: it cannot see the branch it is not taking.