Batch A: version restore, replaced files keep history (fail closed), trash protection, OIDC confirm, WebDAV quota, change-feed epoch (v0.6.343) #910
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "batch-a"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #902, #906, #908, #907, #903. Covers the change-feed part of #904; the rest of #904 is batch B.
Spec:
docs/superpowers/specs/2026-10-15-batch-a-design.md. Plan:docs/superpowers/plans/2026-10-15-batch-a.md. Every task went through TDD and a task review; the whole branch then had a final review and a docs accuracy review.What changes
version-not-saved: 503 +Retry-After: 30, or 507). This covers PUT, upload, public link, TUS, WOPI, MOVE, COPY, REST rename, restore and reports.trash-managed). A person's own permanent delete respects legal holds. The restore target in the sidecar is validated (NFC-tolerant).auth_timeis within 10 minutes counts as the confirmation. A silent SSO (acr"0") does not. New switch:auth.oidcAlwaysSignInAgain.908-2: a version, not a trash entry
A file replaced by MOVE or COPY keeps its old content as a version, not as a trash entry:
Failing before the fix (908-1, branch before Task 3)
Upgrade notes
See CHANGELOG v0.6.343:
Live checks
Spec §9, on both dogfoods after the merge. Results will be posted on the issues.