Interface StructuralLoadConfigurationInfo

One entry per Values slot, in file order. The pairing the schema requires — the i-th location positions the i-th value — is carried inside the entry rather than across two arrays, so a slot this reader could not resolve keeps its place with value absent and dropped naming why. A dropped slot that instead shifted its successors left would report a later load as applied at an earlier station, which reads as real data.

Locations as the file writes it, absent when the file omits it or writes it unusably. Kept beside entries for the malformed case where it is longer than Values: those extra rows belong to no slot and would otherwise be lost. Consumers pairing a load with its station read entries[i].location, never this list.

True when a bound of this reader — the depth cap, the node budget, or the cycle guard — dropped a slot in this configuration or anywhere beneath it. It separates "the file holds no more" from "we stopped reading", which a truncated tree otherwise reports identically to a genuinely small one.