fix(#579): the sweep-off warning is slotted, toggled, and its dead twin removed #599
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-579"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Recon turned #579's either/or into a sharper finding:
set-f-trashwarnis not a setting but the "deleted files accumulate without limit" notice, and it was doubly orphaned — never inSET_SLOTS(so it rendered on no page) and never toggled bysyncTrashAuto(so even slotted it would never have appeared). A second orphan rode along:sdTrashWarn, a ×4-translated description for a "warn people in the file browser" feature that was never built and is referenced nowhere.Per the decision (slot it):
SET_SLOTSgains["set-f-trashwarn", "adm-trash-ret"]— the warning travels with the auto-purge checkbox onto the Deleted-files admin page.syncTrashAutotoggles it: visible exactly while the sweep is off, the state it warns about.KNOWN_UNSLOTTEDallow-list is emptied (mechanism kept for the next orphan) — removing it first is what produced the red.sdTrashWarndeleted: dead key, mismatched text, in-mandate per the decision.Red witnessed twice: the slots guard failed on the orphan once un-allow-listed, and the new
web/test/trash-warn.test.js(liftssyncTrashAuto, fake$) failed on the missing toggle. Green: both, plus the full web suite and the extract gate.