You'll notice
Useful2 Signal2
Shared memory conflict notices now distinguish a write that never saw the shared copy.
What's wrong with this entry?
Anonymous. No account, no email.
What
Conflict notices for shared team memory now separate a file written by a session that never had the shared copy from an ordinary two-writers-at-once conflict, and the notice left on disk says which happened. Pulls that would overwrite a locally changed file also raise the notice.
Details
- Recovered conflicts are counted under
tengu_team_mem_conflict_recovered. - A delete that comes back 404 no longer drops local state outright: the path is listed again and the delete is retried on the next cycle if the entry is still there.
- Part of the existing team memory sync; no new flag.
Evidence
this session did not have the shared version of that file when it wrote it.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.