Not switched on
Useful1 Signal3
Sync journal records can be marked halted, but nothing in this build sets it.
An optional halted field exists on sync journal entries with no caller passing it.
What's wrong with this entry?
Anonymous. No account, no email.
What
The per-turn journal record gained an optional halted field, included only when the publish routine is called with a new fourth argument. Nothing observed in this build passes it.
Evidence
...(o !== void 0 && { halted: o })
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.
-
v2.1.238
Sync state machine gains a moved-root case and a per-turn pull hook
Both mention directory
-
v2.1.238
Untracked-file survey extracted and shared
Both mention directory
-
v2.1.238
Sync internals reshaped around per-file credential state
Both mention directory