v0.6.391: show the locks an administrator's action carries or ends (#1073) #1081

Merged
Cordy merged 28 commits from lk1073 into main 2026-11-03 04:51:46 +00:00
Owner

Closes #1073.

  • Lock rows in four dialogs: Transfer, Delete unread files, Delete space and Delete group with the space now say how many files are locked for editing, by whom (up to 3 names, then "and N more"), whether an editor is open, and whether the locks move with the files or end. The counts come from a read-only lock census (?locks=1 on the estate and space-state answers), never cached.
  • After the action: locksCarried / locksBroken / locksReleased in the answers, status lines and audit notes (0 included when a lock store is wired). Holders get one grouped bell per action with a padlock and no link. A space delete sends the "deleted" bells only after its tombstone is written.
  • Transfer: carries the acting administrator's own lock, and only on the transfer path. Lock releases match paths by segment in NFC.
  • Administration › Locks:
    • The admin answer no longer carries token or session.
    • The kind labels are fixed (WebDAV, Office, Manual, Folder).
    • Break uses the new DELETE /api/v1/admin/locks?path=<stored path>, which does a record-level drop. Before, Break answered 404 for locks in other people's homes.
  • Administration › Spaces › Delete opens the Delete space dialog.
  • German/Italian: legal-hold wording ("rechtliche Sperre", "blocco legale"); "Space" instead of "Bereich" in Delete group.
  • Docs: CHANGELOG v0.6.391, chart appVersion, handbook pages, ARCHITECTURE.md.

Reviewed per wave (W1-W3) plus a final review with adversarial probes; all findings fixed or in the backlog.

Closes #1073. - **Lock rows in four dialogs:** Transfer, Delete unread files, Delete space and Delete group with the space now say how many files are locked for editing, by whom (up to 3 names, then "and N more"), whether an editor is open, and whether the locks move with the files or end. The counts come from a read-only lock census (`?locks=1` on the estate and space-state answers), never cached. - **After the action:** `locksCarried` / `locksBroken` / `locksReleased` in the answers, status lines and audit notes (0 included when a lock store is wired). Holders get one grouped bell per action with a padlock and no link. A space delete sends the "deleted" bells only after its tombstone is written. - **Transfer:** carries the acting administrator's own lock, and only on the transfer path. Lock releases match paths by segment in NFC. - **Administration › Locks:** - The admin answer no longer carries `token` or `session`. - The kind labels are fixed (WebDAV, Office, Manual, Folder). - Break uses the new `DELETE /api/v1/admin/locks?path=<stored path>`, which does a record-level drop. Before, Break answered 404 for locks in other people's homes. - **Administration › Spaces › Delete** opens the Delete space dialog. - **German/Italian:** legal-hold wording ("rechtliche Sperre", "blocco legale"); "Space" instead of "Bereich" in Delete group. - **Docs:** CHANGELOG v0.6.391, chart appVersion, handbook pages, ARCHITECTURE.md. Reviewed per wave (W1-W3) plus a final review with adversarial probes; all findings fixed or in the backlog.
S1: PruneBeforeMove keeps the locks the person acting passes (owner
transfer only); PruneUnder and PruneHolderUnder release them, so a member
administrator removing themselves or an administrator lowering a grant
made to themselves loses the locks they can no longer write.
N1: nLockGoneN formats {n} with fmtCount.
N2: adminLockBreak looks up the path as sent before its NFC form.
N3: adminLockBreak and lockRemove remove the record read
(Store.UnlockRecord), so a lock re-taken in between stays (404).
Docs: ARCHITECTURE, CHANGELOG v0.6.391, admin-policy.
Merge main (v0.6.390) into lk1073
All checks were successful
ci / test-and-build (pull_request) Successful in 1h11m40s
5761869cc9
Cordy merged commit 68afa4d5e5 into main 2026-11-03 04:51:46 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#1081
No description provided.