You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(folders): reach nested stragglers on retry and confine locking to workflows
Two follow-ons from the cascade reordering.
The delete subtree walk still collected active folders only. Since the
cascade now stamps folders before children, a failure during the child pass
leaves intermediate folders archived, and an active-only walk drops them —
so resources still live underneath were never reached on the retry and
stayed outside every later timestamp-matched restore. The walk now admits
folders that are active OR already carry this cascade's own timestamp, which
reaches the stragglers while still excluding folders archived independently
under a different stamp.
Locking was only half-confined to workflows. `assertFolderMutable` was gated
but the admin check and the `locked` write were not, so an admin could
persist `locked` on a knowledge-base or table folder — a column nothing reads
for those types — and a non-admin update that merely mentioned `locked` was
rejected on a type where locking does not exist. Locking is now a declared
capability on the resource config; the routes reject the field outright for
types that lack it, and the engine refuses to write it as a backstop for the
copilot tools that call it directly.
0 commit comments