Server admin 21a: fluxer-devserver serveradmin scenario: READY, community, roles (#688) #721

Closed
charles wants to merge 0 commits from serveradmin-21a-devserver-community-roles into serveradmin
Owner

What

fluxer-devserver scenarios serveradmin (user owns Forked) and serveradmin_moderator (Forked owned by ada, user holds Moderators under grace's Admins), spec §9 first half:

  • Fixtures: serveradmin_ready.json, serveradmin_moderator_ready.json (daily-use READY, Forked's properties as a full GuildResponse, roles Admins 3 > Moderators 2 > Helpers 1 = Members 1 > @everyone, Helpers wins the tie by lower id), fixtures/serveradmin/{members,bans,invites}.json (34 extra members for 40 in total, a bot, a timed-out member; 3 bans, one temporary; 3 guild invites). All checked against the proto types when the server starts.
  • admin.rs: PATCH /guilds/{id} (schema limits, MANAGE_GUILD, the features rule with GUILD_FEATURE_NOT_TOGGLEABLE, AFK/system channel checks, image gates, GUILD_UPDATE), role create/update/delete/reorder (GUILD_ROLE_CREATE|UPDATE|DELETE|UPDATE_BULK, bulk with only the moved roles, MAX_GUILD_ROLES at max_roles, reorder lock once with lock_next_reorder), [[serveradmin.timeout]], [[serveradmin.step]] (swap_roles, swap_channels, named or on a timer). Later READYs carry the changes.
  • permissions.rs: the server's guild permissions and hierarchy (GuildRoleService.ts, guild_members_roles.erl), with unit tests.
  • Public DevServer::admin_script() -> AdminScript (trigger, run, names, member, roles, set_max_roles, lock_next_reorder), AdminStep, AdminScriptError.

Tests

crates/fluxer-devserver/tests/serveradmin.rs: the plan's nine (both_readys_parse_with_proto_types, guild_patch_echoes_update, feature_outside_toggleable_refused, role_crud_emits_events, role_positions_emit_bulk_with_changed_roles_only, moderator_cannot_edit_role_above, moderator_cannot_grant_what_they_lack, resource_locked_once, scripted_reorder_emits_bulk) plus guild_patch_validation_limits, moderator_cannot_patch_guild, role_create_validation_and_limit, deleting_a_role_takes_it_from_its_members, timed_out_member_is_timed_out_from_the_start; unit tests in admin.rs and permissions.rs. FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci green locally. No display tests involved, no UI change.

Deviations

  • The reorder lock answers what the server sends: ResourceLockedError is 423 with code GENERAL_ERROR and Retry-After: 2, not RESOURCE_LOCKED (that code is only used by RetryingLock.ts). The client (Tasks 9a/22) should recognise the lock by status 423.
  • Validation codes follow ZodErrorMap.ts: range/type errors are INVALID_FORMAT, an overlong content_warning_text is CONTENT_EXCEEDS_MAX_LENGTH, names STRING_LENGTH_INVALID.
  • "features BANNER and INVITES_DISABLED off" read as: BANNER on (Forked has a banner), INVITES_DISABLED off.
  • The scripted reorder steps in serveradmin.toml are untimed (triggered by name) so that --devserver serveradmin stays stable; after_ms/every_ms play them on a timer.
  • mfa_level changes are owner-only but ask no identity check yet (Task 21b). Bans, invites and the member-search supplemental are loaded and validated, kept for 21b's endpoints (#[expect(dead_code)]).
  • Outside the files list, minimal: voice.rs decode_data_uri made pub(crate) (guild images); invites.rs member_guild applies the administration overlay so channel creation sees current roles.
  • Member lists and the chat/voice permission checks still read the fixture roles (README says so).

Closes #688

🤖 Generated with Claude Code

https://claude.ai/code/session_0161qMQMsCyJhjYw4gqa6e4K

## What `fluxer-devserver` scenarios `serveradmin` (user owns Forked) and `serveradmin_moderator` (Forked owned by ada, user holds Moderators under grace's Admins), spec §9 first half: - Fixtures: `serveradmin_ready.json`, `serveradmin_moderator_ready.json` (daily-use READY, Forked's properties as a full `GuildResponse`, roles Admins 3 > Moderators 2 > Helpers 1 = Members 1 > @everyone, Helpers wins the tie by lower id), `fixtures/serveradmin/{members,bans,invites}.json` (34 extra members for 40 in total, a bot, a timed-out member; 3 bans, one temporary; 3 guild invites). All checked against the proto types when the server starts. - `admin.rs`: `PATCH /guilds/{id}` (schema limits, `MANAGE_GUILD`, the features rule with `GUILD_FEATURE_NOT_TOGGLEABLE`, AFK/system channel checks, image gates, `GUILD_UPDATE`), role create/update/delete/reorder (`GUILD_ROLE_CREATE|UPDATE|DELETE|UPDATE_BULK`, bulk with only the moved roles, `MAX_GUILD_ROLES` at `max_roles`, reorder lock once with `lock_next_reorder`), `[[serveradmin.timeout]]`, `[[serveradmin.step]]` (`swap_roles`, `swap_channels`, named or on a timer). Later READYs carry the changes. - `permissions.rs`: the server's guild permissions and hierarchy (`GuildRoleService.ts`, `guild_members_roles.erl`), with unit tests. - Public `DevServer::admin_script()` -> `AdminScript` (`trigger`, `run`, `names`, `member`, `roles`, `set_max_roles`, `lock_next_reorder`), `AdminStep`, `AdminScriptError`. ## Tests `crates/fluxer-devserver/tests/serveradmin.rs`: the plan's nine (`both_readys_parse_with_proto_types`, `guild_patch_echoes_update`, `feature_outside_toggleable_refused`, `role_crud_emits_events`, `role_positions_emit_bulk_with_changed_roles_only`, `moderator_cannot_edit_role_above`, `moderator_cannot_grant_what_they_lack`, `resource_locked_once`, `scripted_reorder_emits_bulk`) plus `guild_patch_validation_limits`, `moderator_cannot_patch_guild`, `role_create_validation_and_limit`, `deleting_a_role_takes_it_from_its_members`, `timed_out_member_is_timed_out_from_the_start`; unit tests in `admin.rs` and `permissions.rs`. `FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci` green locally. No display tests involved, no UI change. ## Deviations - The reorder lock answers what the server sends: `ResourceLockedError` is 423 with code `GENERAL_ERROR` and `Retry-After: 2`, not `RESOURCE_LOCKED` (that code is only used by `RetryingLock.ts`). The client (Tasks 9a/22) should recognise the lock by status 423. - Validation codes follow `ZodErrorMap.ts`: range/type errors are `INVALID_FORMAT`, an overlong `content_warning_text` is `CONTENT_EXCEEDS_MAX_LENGTH`, names `STRING_LENGTH_INVALID`. - "features BANNER and INVITES_DISABLED off" read as: BANNER on (Forked has a banner), INVITES_DISABLED off. - The scripted reorder steps in `serveradmin.toml` are untimed (triggered by name) so that `--devserver serveradmin` stays stable; `after_ms`/`every_ms` play them on a timer. - `mfa_level` changes are owner-only but ask no identity check yet (Task 21b). Bans, invites and the member-search supplemental are loaded and validated, kept for 21b's endpoints (`#[expect(dead_code)]`). - Outside the files list, minimal: `voice.rs` `decode_data_uri` made `pub(crate)` (guild images); `invites.rs` `member_guild` applies the administration overlay so channel creation sees current roles. - Member lists and the chat/voice permission checks still read the fixture roles (README says so). Closes #688 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_0161qMQMsCyJhjYw4gqa6e4K
The two READYs are the daily-use READY with Forked's properties shaped as
GuildResponse (mapGuildToGuildResponse, fluxer_api/src/api/guild/GuildModel.ts:54-81),
roles as GuildRoleResponse (GuildModel.ts:83-96). serveradmin/bans.json follows
GuildBanResponse (packages/schema/src/domains/guild/GuildResponseSchemas.ts), invites.json
the invite metadata of fixtures/rest/invite_metadata.json, members.json READY members and
users plus the member-search supplemental (GuildMemberSearchSchemas.ts).

Refs #688

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0161qMQMsCyJhjYw4gqa6e4K
PATCH /guilds/{id}, POST|PATCH|DELETE /guilds/{id}/roles[/{role}] and the role
reorder, answered as GuildOperationsService.updateGuild and GuildRoleService
(fluxer_api/src/api/guild/services, fork ba98441b) with the request limits of
GuildRequestSchemas.ts and the error codes of ZodErrorMap.ts; the hierarchy of
guild_members_roles.erl in permissions.rs; GUILD_UPDATE and GUILD_ROLE_* events;
the reorder lock as ResourceLockedError answers it (423 GENERAL_ERROR); a scripted
other client that reorders roles and channels (AdminScript). Bans fixture shape:
GuildBanResponse of GuildMemberSchemas.ts.

voice.rs: decode_data_uri is pub(crate) for the guild images; invites.rs:
member_guild applies the administration overlay.

Refs #688

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0161qMQMsCyJhjYw4gqa6e4K
Author
Owner

Independent review: Task 5 (fluxer-api channels, members, bans, member search, invites)

Reviewed 7cd8bb1c..5f4dc7f8 cold, in a fresh worktree.

Tests named by the plan. All present: one wiremock test per method checks the method, path, body and answer. own_member_goes_to_me, kick_and_unban_204, member_search_post_body, user_is_not_banned_error and timeout_too_long_error are there. Request bodies are matched against Task 2/3's proto fixtures with body_json.

Interfaces. Every name in the Interfaces block exists with the stated shape: update_channel -> Channel, update_channel_positions (204), follower_stats, update_member -> GuildMember, update_own_member (/members/@me), add_member_role/remove_member_role (PUT/DELETE, 204), kick_member, ban_member, list_bans, unban_member, search_members (POST /members-search), list_guild_invites -> Vec<InviteMetadata> and delete_invite(code). Guild-channel deletion reuses delete_channel.

Invariants. All changes are in fluxer-api and stay transport only. list_bans drops entries it cannot read and does not panic. No secrets. Writes use Retry::Never.

Parity spot-checks against the fork.

  • Routes, methods and statuses match GuildMemberController.ts: PATCH members/@me answers with a GuildMemberResponse, member role PUT/DELETE, ban PUT and unban DELETE answer 204. InviteController.ts lists GET /guilds/:id/invites and DELETE /invites/:code (204). GuildChannelController.ts answers the PATCH on /guilds/:id/channels with 204.
  • USER_IS_NOT_BANNED comes from InputValidationError.fromCode('user_id', …) (GuildModerationService.ts:263). TIMEOUT_CANNOT_EXCEED_365_DAYS comes from fromCode('communication_disabled_until', …) (GuildMemberOperationsService.ts:603). Both arrive nested in INVALID_FORM_BODY, so the change to error.rs that lifts them out is justified. The fixtures' paths and codes match.
  • The kick sends no reason: KickMemberModal.tsx calls GuildMemberCommands.kick(guildId, targetUser.id) without one. This is spec §17 Q8's recommended answer.

Findings

  • minor: fixtures/errors/timeout_cannot_exceed_365_days.json has the message "…365 days from now.". The server calls fromCode without the maxDays variable, so the text it actually renders may differ. Callers act on the code, so this does not matter.
  • minor (process): src/error.rs is outside Task 5's Files list. The deviation is declared, is one ||, and should conflict only mechanically with Task 4.

Local gate: FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci passed ("all steps passed", exit 0).

Verdict: APPROVED. No blocking findings; local CI is green.

## Independent review: Task 5 (fluxer-api channels, members, bans, member search, invites) Reviewed `7cd8bb1c..5f4dc7f8` cold, in a fresh worktree. **Tests named by the plan.** All present: one wiremock test per method checks the method, path, body and answer. `own_member_goes_to_me`, `kick_and_unban_204`, `member_search_post_body`, `user_is_not_banned_error` and `timeout_too_long_error` are there. Request bodies are matched against Task 2/3's proto fixtures with `body_json`. **Interfaces.** Every name in the Interfaces block exists with the stated shape: `update_channel -> Channel`, `update_channel_positions` (204), `follower_stats`, `update_member -> GuildMember`, `update_own_member` (`/members/@me`), `add_member_role`/`remove_member_role` (PUT/DELETE, 204), `kick_member`, `ban_member`, `list_bans`, `unban_member`, `search_members` (POST `/members-search`), `list_guild_invites -> Vec<InviteMetadata>` and `delete_invite(code)`. Guild-channel deletion reuses `delete_channel`. **Invariants.** All changes are in fluxer-api and stay transport only. `list_bans` drops entries it cannot read and does not panic. No secrets. Writes use `Retry::Never`. **Parity spot-checks against the fork.** - Routes, methods and statuses match `GuildMemberController.ts`: `PATCH members/@me` answers with a `GuildMemberResponse`, member role PUT/DELETE, ban PUT and unban DELETE answer 204. `InviteController.ts` lists `GET /guilds/:id/invites` and `DELETE /invites/:code` (204). `GuildChannelController.ts` answers the PATCH on `/guilds/:id/channels` with 204. - `USER_IS_NOT_BANNED` comes from `InputValidationError.fromCode('user_id', …)` (`GuildModerationService.ts:263`). `TIMEOUT_CANNOT_EXCEED_365_DAYS` comes from `fromCode('communication_disabled_until', …)` (`GuildMemberOperationsService.ts:603`). Both arrive nested in INVALID_FORM_BODY, so the change to `error.rs` that lifts them out is justified. The fixtures' paths and codes match. - The kick sends no reason: `KickMemberModal.tsx` calls `GuildMemberCommands.kick(guildId, targetUser.id)` without one. This is spec §17 Q8's recommended answer. **Findings** - minor: `fixtures/errors/timeout_cannot_exceed_365_days.json` has the message "…365 days from now.". The server calls `fromCode` without the `maxDays` variable, so the text it actually renders may differ. Callers act on the code, so this does not matter. - minor (process): `src/error.rs` is outside Task 5's Files list. The deviation is declared, is one `||`, and should conflict only mechanically with Task 4. **Local gate:** `FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci` passed ("all steps passed", exit 0). **Verdict: APPROVED.** No blocking findings; local CI is green.
`fluxer --devserver serveradmin` now shows GUILD_ROLE_UPDATE_BULK and
CHANNEL_UPDATE_BULK without a test triggering them: the role swap plays 90 s
after the first READY, the channel swap at 100 s, both every 2 minutes (each
swap undoes the previous one). Tests still trigger them by name.

Refs #688

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Author
Owner

Review round 1, changes in bc6b69e3:

  • Blocking, local gate: FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci was run to the end on bc6b69e3 and passed (==> xtask ci: all steps passed; livekit-interop skipped as usual).
  • Minor, admin.rs, 423 GENERAL_ERROR instead of RESOURCE_LOCKED: no code change. The devserver answers as the fork does (ResourceLockedError is a LockedError with GENERAL_ERROR). Follow-up #722 asks for the spec and plan to be corrected and for Tasks 9a, 12 and 22 to detect the lock by status 423.
  • Minor, serveradmin.toml, steps had no timer: fixed. Both steps now have after_ms and every_ms: the role swap plays 90 s after the first READY, the channel swap at 100 s, and both repeat every 2 minutes. Each swap undoes the previous one. That is late enough that tests do not see it, and tests can still trigger the steps by name. New test admin::tests::shipped_scenario_steps_play_on_a_timer (it failed before the fixture change). README updated.
  • Minor, README, fixture roles still read by member lists and chat/voice checks: no code change (it is documented). Follow-up #723 records it for Task 21b or 22.

🤖 Generated with Claude Code

Review round 1, changes in bc6b69e3: - **Blocking, local gate:** `FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci` was run to the end on bc6b69e3 and passed (`==> xtask ci: all steps passed`; livekit-interop skipped as usual). - **Minor, admin.rs, 423 `GENERAL_ERROR` instead of `RESOURCE_LOCKED`:** no code change. The devserver answers as the fork does (`ResourceLockedError` is a `LockedError` with `GENERAL_ERROR`). Follow-up #722 asks for the spec and plan to be corrected and for Tasks 9a, 12 and 22 to detect the lock by status 423. - **Minor, serveradmin.toml, steps had no timer:** fixed. Both steps now have `after_ms` and `every_ms`: the role swap plays 90 s after the first READY, the channel swap at 100 s, and both repeat every 2 minutes. Each swap undoes the previous one. That is late enough that tests do not see it, and tests can still trigger the steps by name. New test `admin::tests::shipped_scenario_steps_play_on_a_timer` (it failed before the fixture change). README updated. - **Minor, README, fixture roles still read by member lists and chat/voice checks:** no code change (it is documented). Follow-up #723 records it for Task 21b or 22. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Author
Owner

Independent review: Task 21a (bc6b69e3)

Scope: git diff 28edd5a8..origin/serveradmin-21a-devserver-community-roles, read cold.

Checks

  1. Plan tests. All nine named tests exist in crates/fluxer-devserver/tests/serveradmin.rs and test what the plan says: both READYs parse with the proto types, the guild PATCH answer equals GUILD_UPDATE, GUILD_FEATURE_NOT_TOGGLEABLE, CRUD with its events, the bulk event carries only changed roles (Admins 4, Members 3), moderator refusals, 423 sent only once, and the scripted bulk events. Extra tests cover the validation limits, MAX_GUILD_ROLES and the timeout.
  2. Interfaces. The serveradmin and serveradmin_moderator scenarios are present. Roles are Admins 3 > Moderators 2 > Helpers 1 = Members 1 (Helpers has the lower id) > @everyone. The admin fields are set. Moderators has KICK, BAN, MODERATE, MANAGE_ROLES, MANAGE_CHANNELS and MANAGE_NICKNAMES, but not MANAGE_GUILD. There are 40 members, including a bot, a timed-out member and grace holding Admins. permissions.rs, the role and guild endpoints with their events, max_roles, lock_next_reorder and the scripted steps are all in place. The public DevServer::admin_script / AdminScript / AdminStep are additive.
  3. Invariants. Only fluxer-devserver and fixtures are touched. The READY guild, roles, bans (GuildBanResponse), invites (GuildInviteMetadataResponse) and members match spec/openapi.json: no missing required fields and no extra fields. No tokens, secrets or local paths are in the fixtures. Request and server data are parsed without unwraps.
  4. Parity, checked against the fork.
    • isRoleHigherThan, getUserHighestRole and buildRoleManageCheck match.
    • mergeManageableRoleOrder / reorderRolePositions match: a renumber from the top, and the event carries changed roles only.
    • USER_TOGGLEABLE_GUILD_FEATURES and computeUpdatedFeatures match.
    • ResourceLockedError is 423 GENERAL_ERROR with Retry-After: 2.
    • createRole gives position 1 and @everyone's permissions by default.
    • The MAX_GUILD_ROLES message and nsfw → nsfw_level (3/2) match.
    • The mfa_level change is owner-only.
    • deleteRole on @everyone returns UNKNOWN_ROLE.
  5. Review Focus. No item belongs to 21a. Item 1 (the hierarchy) is matched by the server-side checks above.
  6. Local gate. FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci on bc6b69e3 finished with "all steps passed".

Findings

  • minor: serveradmin_moderator inherits the timed other-client-reorders-roles step. At 90 s and then every 120 s it swaps Helpers and Moderators. In the moderator scenario that drops the user's own role below Helpers, so which roles are locked changes during a manual session. Consider clearing step in serveradmin_moderator.toml, or noting it there.
  • minor: the fork masks requested role permissions with permissionWriteMask (ALL_PERMISSIONS), so unknown bits are dropped silently. The devserver instead stores unknown bits for the owner and refuses them with MISSING_PERMISSIONS for a non-owner, because Permissions::all() contains only known bits. This is an edge case that no client sends today.
  • minor: the plan's wording "features BANNER and INVITES_DISABLED off" is ambiguous. The fixture has BANNER on and INVITES_DISABLED off, which matches the spec's needs (banner upload is allowed, and the invite pause can be toggled). Fine as built; the plan text could be clarified alongside #722.
  • The earlier follow-ups #722 (423 code in the spec and plan) and #723 (fixture roles still read by the member list and the chat/voice checks) are linked and acceptable.

Verdict: APPROVED. No blocking findings, and the local CI is green.

## Independent review: Task 21a (bc6b69e3) Scope: `git diff 28edd5a8..origin/serveradmin-21a-devserver-community-roles`, read cold. **Checks** 1. **Plan tests.** All nine named tests exist in `crates/fluxer-devserver/tests/serveradmin.rs` and test what the plan says: both READYs parse with the proto types, the guild PATCH answer equals `GUILD_UPDATE`, `GUILD_FEATURE_NOT_TOGGLEABLE`, CRUD with its events, the bulk event carries only changed roles (Admins 4, Members 3), moderator refusals, 423 sent only once, and the scripted bulk events. Extra tests cover the validation limits, `MAX_GUILD_ROLES` and the timeout. 2. **Interfaces.** The `serveradmin` and `serveradmin_moderator` scenarios are present. Roles are Admins 3 > Moderators 2 > Helpers 1 = Members 1 (Helpers has the lower id) > @everyone. The admin fields are set. Moderators has KICK, BAN, MODERATE, MANAGE_ROLES, MANAGE_CHANNELS and MANAGE_NICKNAMES, but not MANAGE_GUILD. There are 40 members, including a bot, a timed-out member and grace holding Admins. `permissions.rs`, the role and guild endpoints with their events, `max_roles`, `lock_next_reorder` and the scripted steps are all in place. The public `DevServer::admin_script` / `AdminScript` / `AdminStep` are additive. 3. **Invariants.** Only `fluxer-devserver` and fixtures are touched. The READY guild, roles, bans (`GuildBanResponse`), invites (`GuildInviteMetadataResponse`) and members match `spec/openapi.json`: no missing required fields and no extra fields. No tokens, secrets or local paths are in the fixtures. Request and server data are parsed without unwraps. 4. **Parity, checked against the fork.** - `isRoleHigherThan`, `getUserHighestRole` and `buildRoleManageCheck` match. - `mergeManageableRoleOrder` / `reorderRolePositions` match: a renumber from the top, and the event carries changed roles only. - `USER_TOGGLEABLE_GUILD_FEATURES` and `computeUpdatedFeatures` match. - `ResourceLockedError` is 423 `GENERAL_ERROR` with `Retry-After: 2`. - `createRole` gives position 1 and @everyone's permissions by default. - The `MAX_GUILD_ROLES` message and `nsfw` → `nsfw_level` (3/2) match. - The `mfa_level` change is owner-only. - `deleteRole` on @everyone returns `UNKNOWN_ROLE`. 5. **Review Focus.** No item belongs to 21a. Item 1 (the hierarchy) is matched by the server-side checks above. 6. **Local gate.** `FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci` on bc6b69e3 finished with "all steps passed". **Findings** - *minor*: `serveradmin_moderator` inherits the timed `other-client-reorders-roles` step. At 90 s and then every 120 s it swaps Helpers and Moderators. In the moderator scenario that drops the user's own role below Helpers, so which roles are locked changes during a manual session. Consider clearing `step` in `serveradmin_moderator.toml`, or noting it there. - *minor*: the fork masks requested role permissions with `permissionWriteMask` (`ALL_PERMISSIONS`), so unknown bits are dropped silently. The devserver instead stores unknown bits for the owner and refuses them with `MISSING_PERMISSIONS` for a non-owner, because `Permissions::all()` contains only known bits. This is an edge case that no client sends today. - *minor*: the plan's wording "features `BANNER` and `INVITES_DISABLED` off" is ambiguous. The fixture has BANNER on and INVITES_DISABLED off, which matches the spec's needs (banner upload is allowed, and the invite pause can be toggled). Fine as built; the plan text could be clarified alongside #722. - The earlier follow-ups #722 (423 code in the spec and plan) and #723 (fixture roles still read by the member list and the chat/voice checks) are linked and acceptable. **Verdict: APPROVED.** No blocking findings, and the local CI is green.
Author
Owner

Merged into serveradmin by hand (the merge API returns 405); the commits are in the branch.

Merged into `serveradmin` by hand (the merge API returns 405); the commits are in the branch.
charles closed this pull request 2026-11-15 23:53:48 +00:00

Pull request closed

Sign in to join this conversation.
No description provided.