Server admin 35: Acceptance #703

Closed
opened 2026-11-15 19:02:02 +00:00 by charles · 1 comment
Owner

Task 35 of the Server administration plan (docs/superpowers/plans/2026-11-15-serveradmin.md, section "### Task 35:"). The plan on the serveradmin branch is the source of truth; this copy is for reading.

Closes: —
Depends on: 22, 34

Files:

  • Create: docs/acceptance/serveradmin.md

  • Test: apps/fluxer/tests/serveradmin_acceptance.rs

  • End-to-end on the devserver serveradmin scenario, as the owner: open "Edit channel" from the channel menu, change name, topic and slowmode, save (the PATCH's changed fields asserted) → try to close while dirty (stays, flash) → add an override for Helpers, deny VIEW_CHANNEL to @everyone, save (whole array asserted) → "Sync with category" → drag #general below #random and into another category (one-element positions body asserted, order kept after the bulk event) → the scripted other client reorders (the sidebar follows) → duplicate and delete a channel → Roles: create, rename, colour, grant MANAGE_MESSAGES, drag above Helpers, save (PATCH then positions asserted), duplicate, delete → tick a role on a member from the user menu → nickname, timeout 10 minutes with a reason, remove timeout, kick, ban 1 day with 1 hour of history (bodies asserted) → Bans: details, revoke → Invites: revoke one, pause, enable → Overview: name, idle timeout, hide join messages, flexible names (features list asserted to differ by exactly one name) → Members page: search, role filter, page 2, indexing_first → transfer ownership with the scenario password, then delete a second community within 4.5 minutes without a second prompt, then after the token's expiry with a prompt and a wrong password first.

  • The same scenario as serveradmin_moderator: roles at or above the user's locked, permission switches the user lacks disabled with their reason, no Overview / Moderation / Invites tabs, no rows for members above the user, a forced request (through a test hook) answered MISSING_PERMISSIONS reverts and shows the original's text.

  • The recorded session of the run contains no password, code or sudo token.

  • docs/acceptance/serveradmin.md: Charles's live checklist (spec §2 items 1–12, each with steps against an Electron client on the same account, on a throwaway community), the open question and follow-up issues, known gaps (spec §13, §14), and the contents of sub-project 10 (spec §16).

  • Commit test: server administration acceptance.

Task 35 of the Server administration plan (`docs/superpowers/plans/2026-11-15-serveradmin.md`, section "### Task 35:"). The plan on the `serveradmin` branch is the source of truth; this copy is for reading. **Closes:** — **Depends on:** 22, 34 **Files:** - Create: `docs/acceptance/serveradmin.md` - Test: `apps/fluxer/tests/serveradmin_acceptance.rs` - [ ] End-to-end on the devserver `serveradmin` scenario, as the owner: open "Edit channel" from the channel menu, change name, topic and slowmode, save (the PATCH's changed fields asserted) → try to close while dirty (stays, flash) → add an override for Helpers, deny VIEW_CHANNEL to @everyone, save (whole array asserted) → "Sync with category" → drag #general below #random and into another category (one-element positions body asserted, order kept after the bulk event) → the scripted other client reorders (the sidebar follows) → duplicate and delete a channel → Roles: create, rename, colour, grant MANAGE_MESSAGES, drag above Helpers, save (PATCH then positions asserted), duplicate, delete → tick a role on a member from the user menu → nickname, timeout 10 minutes with a reason, remove timeout, kick, ban 1 day with 1 hour of history (bodies asserted) → Bans: details, revoke → Invites: revoke one, pause, enable → Overview: name, idle timeout, hide join messages, flexible names (features list asserted to differ by exactly one name) → Members page: search, role filter, page 2, `indexing_first` → transfer ownership with the scenario password, then delete a second community within 4.5 minutes without a second prompt, then after the token's expiry with a prompt and a wrong password first. - [ ] The same scenario as `serveradmin_moderator`: roles at or above the user's locked, permission switches the user lacks disabled with their reason, no Overview / Moderation / Invites tabs, no rows for members above the user, a forced request (through a test hook) answered `MISSING_PERMISSIONS` reverts and shows the original's text. - [ ] The recorded session of the run contains no password, code or sudo token. - [ ] `docs/acceptance/serveradmin.md`: Charles's live checklist (spec §2 items 1–12, each with steps against an Electron client on the same account, on a throwaway community), the open `question` and `follow-up` issues, known gaps (spec §13, §14), and the contents of sub-project 10 (spec §16). - [ ] Commit `test: server administration acceptance`.
Author
Owner

From the review of Task 22 (PR #741): add an assertion that a logout through the real Runtime drops the sudo token (only checked at the SudoTokens level and by reading so far).

From the review of Task 22 (PR #741): add an assertion that a logout through the real Runtime drops the sudo token (only checked at the SudoTokens level and by reading so far).
Sign in to join this conversation.
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
charles/fluxer-native#703
No description provided.