You'll notice
Useful2 Signal3
File sync can pin to the exact commit a cloud session started from, disabling itself if unreadable.
What's wrong with this entry?
Anonymous. No account, no email.
What
Per-turn file sync, which keeps your local checkout in step with a session, previously could only start from an uploaded bundle. It can now also start from a remote commit reference, pinning sync to that exact commit. If the checkout cannot read that commit, sync turns itself off for the session and says so.
Details
- The sync origin is now a tagged value with a
remote_refkind carrying the agreed tree and the remote commit; arming pins the treeish to that commit, or to nothing for bundle origins. - The inventory record stores which kind of origin was used, and the
tengu_dir_sync_inventorytelemetry event gained a matchingorigin_kindfield. The bundle scope is recorded only for bundle origins. - Two new failure notices ship with it; this path is only reached when a session actually has a remote-commit origin.
Evidence
File sync is off for this session: the commit the cloud session started from cannot be read in this checkout
Strings lifted out of the shipped bundle, so the claim above can be checked against them.