Dogfood: self-service spaces + live group resolution end-to-end #111
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Cordy/Cairn#111
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Collects the manual dogfood checks that shipped in v0.3.26–v0.3.28 but were only tracked in closed-issue comments (#94, #96, #64/#79) — now formally on the v0.6 closed-beta milestone.
Self-service spaces (#94, v0.3.27):
case-folder-1→ created toast; visible immediately as admin (backend dir exists).case-folder-1+case-folder-1-ro, owner attributecairnSpaceOwner, creator in the write group. If creation 502s with a Keycloak 403 onPOST /groupsin the pod log: extend thecairn-keycustodyrealm-management roles (group creation rights).Live group resolution (#96, v0.3.28):
cairn-admins→ admin surfaces appear/disappear without re-login.Read-only membership (#64, UI badge from v0.3.20):
Space trash (#95, v0.3.26):
Anything unexpected → new issue in this milestone.
Triage: tandem (hands-on dogfood). Create spaces, exercise live group resolution end-to-end (you + Manuel). Nothing for me to build first — this is real-usage testing; anything it surfaces gets raised as its own issue.
All features under test shipped in v0.3.2x (self-service spaces, live group resolution, read-only membership + "View only" badge, shared space trash) and Nikola has run through the checklist during dogfooding. Per the v0.7 approach, anything that regresses as the remaining UI/UX batch lands will resurface in continuous dogfooding and be raised as its own fix issue. Closing as done.