3 Commits

Include renames

Author	SHA1	Message	Date
jochen	96b0966ad8	Read a shrink against the item's own path, so a moved directory starts its size history again (hq issue 368) ... A reading now keeps the path it was measured at, and the peak is read only from readings at the item's path now. Before, an agent's home that moved to its own account was compared with the operator's home it left, and data-shrank was raised for data that was never lost. Existing readings take their item's path now, so a shrink that is real stays raised.	2026-10-10 17:42:46 +02:00
jochen	abf9125689	Measure each item its own way; never compare a partial size (hq ADR 0233) ... A walk over a large library every hour loads the array that protects it. An item now says how it is measured — a bounded daily walk, a dataset's counters, or its top level only — and a size that is a lower bound is kept as such and never read as a shrink.	2026-10-06 17:00:22 +02:00
jochen	52af210e47	Derive data protection from a module's declared data (hq ADR 0233) ... A module's data section says what it keeps and how precious it is; the backup holder's lines, binding stickiness, retirement on unassign and D13's conditions follow from it, so issue 273's empty replacement is said and an unassigned module's data is remembered, not forgotten.	2026-10-06 16:47:49 +02:00