What
Pulling team or org memory now notices when a file's recorded content is the empty-file hash while the shared copy has real content, and rewrites the file when the local one is genuinely a stale empty file, judged by being 0 bytes and older than a threshold.
Details
- Fetched content is re-hashed and mismatches against the recorded hash are counted.
- Deletion handling runs the same empty-file check before telling you your local copy was kept.
- The sync result gained counts of hash mismatches and restored empty files.
- The concurrent-write log no longer claims that situation only occurs on a first pull.
Evidence
team_memory_multistore_concurrent_write_preserved
Strings lifted out of the shipped bundle, so the claim above can be checked against them.