Expand description
The barrier’s scan-diff (plan §2.1 step 2).
A full walk against the PERSISTED baseline — never a re-seeded bucket manifest. Deletion basis: a path is delete-eligible only if it is absent in THIS scan AND was absent in the PREVIOUS scan AND is present in our own baseline (two-consecutive-scans: the rename-vs-walk race guard — a directory renamed mid-walk can appear in neither pass of one readdir, and that must never read as mass deletion).
Structs§
Functions§
- classify
- is_
control_ path - Legacy citations under the reserved control namespace (boundary-verbs
plan D0.2). A workspace that legally published
files/.flint/...under a pre-D0 syncer has those paths in its baseline; the new scan skips them, so two consecutive scans would classify them absent and publish their DELETION. An upgrade must never delete data: they are carried forward frozen — never re-uploaded, never deleted by us. - scan
- Walk the workspace. Skips the state dir, symlinks (v1 non-goal, as the tier manifest’s), and anything unreadable (reported upstream by the barrier as a warning, not a wedge).