Binary bundles and relocated files
Check decoded byte budgets, destination paths and references without losing source identity.
Why would an archive entry leave its designated import folder?
Check the resolved destination against the supplied root before accepting an entry.
Why can a contained-looking path still resolve outside the import root?
Resolve the supplied symbolic-link tree as well as the path’s lexical segments.
Why did two archive files overwrite one destination?
Group entries by the declared destination-path equivalence while retaining each source label.
Why does a bundle exceed its limit when each file seems small?
Measure actual decoded byte lengths and apply both member and total allowances.
Why did a retained relative attachment link point to the wrong file after migration?
Resolve against the old base, map the actual object, then create the reference for its new location.
Why did a migrated BLOB gain bytes after a text round trip?
Transfer the binary field as bytes and retain empty BLOB separately from NULL.