Remote tool calls now run a sync preflight and abort with sync_failed if files aren't caught up.
What's wrong with this entry?
The path that validates a remote tool call, asks for permission and then dispatches it now runs a file-sync preflight first. A hold aborts the call with an error carrying code sync_failed rather than contacting the host, and sync_failed was added to the outcome reporting for forwarded remote tools.
- The preflight returns go, go with a note (handed to a new callback the caller supplies), or hold.
- Results coming back can now carry sync information, applied on the receiving side when present.
- Nothing gates this, but the preflight returns go immediately when no sync engine is attached.
code: "sync_failed",
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.