#717: orphan space folders gain Take over and deactivate #718

Merged

Cordy merged 8 commits from feat-717 into main

2026-09-24 04:32:06 +00:00

Cordy commented

2026-09-24 04:29:20 +00:00

Owner

Closes #717

An orphan row ("Folder in storage — no managing group found", from #715) has no spacestore record, so the existing lifecycle endpoints would 404 — which is why its menu offered only Details.

Fix (UI only): the orphan menu gains "Take over and deactivate" (danger item): it claims the folder through the normal POST /api/v1/spaces (record owned by the acting admin; the directory already exists, so the best-effort Mkdir is a no-op) and immediately runs the standard deactivate. On reload the row is a regular app-owned space — Reactivate or the type-the-name Delete (contents to Deleted files, name tombstoned) apply as usual. A tombstoned name surfaces the existing "reserved" refusal via the server message; IdP-verified managed rows stay Details-only.

Tests: web/test/qa717.test.js (orphan branch, claim-then-deactivate sequence, i18n ×4 for spcTakeOver).

Closes #717 An orphan row ("Folder in storage — no managing group found", from #715) has no spacestore record, so the existing lifecycle endpoints would 404 — which is why its menu offered only Details. **Fix (UI only):** the orphan menu gains **"Take over and deactivate"** (danger item): it claims the folder through the normal `POST /api/v1/spaces` (record owned by the acting admin; the directory already exists, so the best-effort Mkdir is a no-op) and immediately runs the standard deactivate. On reload the row is a regular app-owned space — Reactivate or the type-the-name Delete (contents to Deleted files, name tombstoned) apply as usual. A tombstoned name surfaces the existing "reserved" refusal via the server message; IdP-verified managed rows stay Details-only. **Tests:** `web/test/qa717.test.js` (orphan branch, claim-then-deactivate sequence, i18n ×4 for `spcTakeOver`).

Cordy added 8 commits

2026-09-24 04:29:21 +00:00

scout(#717 ): spcAct semantics, api() error behavior, current managed-guard in spcMenuEl

scout-717 / scout (push) Successful in 1s

Details

d68556d4c3

test(#717 ): RED - orphan rows offer take-over-and-deactivate

scout-717 / scout (push) Successful in 1s

Details

0fe9480a95

splice(#717 ): orphan take-over-and-deactivate menu action

scout-717 / scout (push) Successful in 1s

Details

874db5a0d0

one-shot(#717 ): RED gate, splice, web checks, self-cleaning commit

fix-717 / fix (push) Successful in 11s

Details

scout-717 / scout (push) Successful in 1s

Details

c8716ccc10

fix(#717 ): orphan space folders gain Take over and deactivate 09a3a69b34

An orphan row has no spacestore record, so lifecycle endpoints would 404. The menu action claims the folder through the normal create API (owner = acting admin) and immediately deactivates it; the standard Reactivate / type-the-name Delete lifecycle applies from there. IdP-verified managed rows stay Details-only. i18n x4.

chg(#717 ): changelog entry for v0.6.265 9102af2669

one-shot: apply v0.6.265 changelog entry, self-remove

chg-265 / chg (push) Successful in 6s

Details

5efac07452

docs: changelog for v0.6.265 (#717 orphan take-over)

ci / test-and-build (pull_request) Successful in 1m16s

Details

3f4fbf6ac9