Settings UI implementation record¶

Status: implemented for the seven agreed pages. This page records the delivered settings migration and the explicitly deferred scope; it is not a pending implementation checklist. See the product contract and theme tokens.

Delivered scope¶

Page	Content / detail entry points
Admin General	Workspaces, services, quota alerts, branding; SMTP draft dialog and explicit test.
Admin Browser	Workspace availability, direct transfers, server relay, ZIP thresholds.
Admin Manager	Measurements, administrative access, bucket tools; migration limits dialog.
Admin Portal	Access and creation, personal keys, logging/history, new-space defaults; CORS dialog.
Admin Authentication	Access-key login, security policy, compact provider lists; dedicated OIDC/LDAP pages.
Admin Key Rotation	Endpoint and key-category selections, previous-key handling, confirmation and real results.
User Portal Settings	Project/access summary, capabilities, new-space defaults; effective origin and draft inheritance.

[x] Explicit compact layout, themed switches and 4px shared badges.
[x] Shared controls, dialogs, dirty actions and close/navigation guards.
[x] Page-owned configuration scopes, fresh-read merge and conflict detection.
[x] Draft-only defaults and inheritance reset, numeric validation and failure retention.
[x] Deferred Portal project selection and stale-response protection.
[x] Retained API, secret, WebAuthn and authorization contracts.
[x] Removed PortalSettingsLayout aliases and obsolete settings card helpers.
[x] English-only Admin; FR/EN/DE user Portal and existing shared profile.

Targeted unit tests cover persistence, conflicts, dialogs, project switching, provider secrets and rotation confirmation. Authenticated Admin/Browser smoke checks live in e2e/agent-ui; settingsVisualQa.spec.ts exercises the Portal settings in three languages, both themes and desktop/mobile using API fixtures. Fixtures prove rendering and UI contracts, not successful Ceph operations. Temporary captures, auth state and reports are excluded from commits.

Verification on 2026-09-22 confirmed that the distinct compact-settings pass still matches this contract after the later interface-convergence work. Browser, Manager and Portal Admin settings still use the shared compact settings frame and draft controller; Portal user settings still use the shared compact project editor with permission, conflict and translation handling intact. The targeted Vitest regression set for these four surfaces and the shared draft flows passes 40 tests.

Portal settings coherence¶

[x] Storage Space settings: Identity, File history, External tools and Space management.
[x] Shared project override editor for Portal and the Admin RGW account Portal tab.
[x] Independent identity/icon saves, guarded dialog drafts, current values for read-only users.
[x] Draft-only inheritance reset preserving delegation, explicit field conflict reporting and fresh-read merges.
[x] Scoped responses and history drafts retained during identity/icon refreshes.
[x] English-only Admin and FR/EN/DE Portal; shared dimensions and themed controls.

The client cannot make the existing APIs atomic. Storage history retains the server's existing preservation of foreign lifecycle rules and compensation on partial S3 failure. It never retries an ambiguous update automatically. The Admin API interprets delegation-only requests as preserving the current override; an explicit empty reset together with delegation uses bucket_defaults: null.

The fixture scenarios exercise both editors and their dialog/viewport behavior. They do not constitute a successful real-Ceph validation. Temporary screenshots and authentication state remain excluded from commits.

The compact settings foundation now uses the denser desktop geometry: 28px controls, 12px normal-weight button text, 13px setting labels, 6px row padding and 12px section padding. Dialogs share the same scale, and short field units stay inline. Geometry is recorded in the visual scenarios alongside screenshots; touch targets remain 44px, including large screens with a coarse pointer. This density correction leaves the existing save boundaries, access rules, translations and nonmigrated forms unchanged.

Admin S3 endpoint inventory¶

The Admin S3 endpoint inventory is now a compact five-column table with contains/exact search and a provider filter over the complete returned list. Details use the existing three-tab endpoint page; no additional detail overlay or expandable row is introduced. Actions stay visible in the order Set as default, Edit/View, Delete, subject to their separate access rules. Filters survive editor round trips and refreshes. A metadata failure keeps configuration changes unavailable until a successful retry.

Its scoped presentation reuses shared table, badge, tag and compact button components without changing general table defaults. Endpoint creation, editing and consultation now also use compact settings sections and one guarded native form across the three tabs. Configuration and tags keep independent save baselines, including retry after a partial save. See Admin storage endpoint editor for composition, access boundaries and validation.

Admin authentication provider editors¶

OIDC and LDAP creation, editing and consultation now share compact sections, canonical fields and the SettingsWorkflowForm action/navigation contract. Identity, secret and switch presentation are factored into common provider components, including field-lock help and stored-secret status. The unused legacy input, label, helper and checkbox exports have been removed from SettingsLayout.

Failed loads require Retry before editing; failed or cancelled writes retain the draft. Pending saves and passkey verification freeze fields, repeated submissions and navigation. Provider payloads and global policy saves remain independent. See Admin authentication provider editors for the validation scope and remaining external-login boundary.

Admin RGW account editor¶

The five account tabs now use the compact workflow, with shared General sections, a single account action area and a common user/group association composition. Account and Portal settings retain independent saves and drafts; pending operations lock the enclosing tabs and navigation. Loading failures, permission failures and association catalogue failures have explicit retry. The advanced association dialog uses the shared draft controls and a switch. See Admin RGW account configuration for exact quota behavior, save boundaries and validation limits.

Ceph Admin RGW identity workflows¶

Account/User create workflows now use SettingsWorkflowForm; their edit configuration tabs use the same SettingsForm/controller contract. This centralizes native submission, pending locks, action geometry and draft navigation guards without changing RGW quota, capability, account-root or key payloads. Local validation stays synchronously retryable and only a real async operation enters the pending state. Browser QA covers create flows at desktop and mobile widths; the isolated endpoint lacks Ceph Admin credentials, so edit rendering and RGW mutations remain fixture-backed for this pass. See Ceph Admin RGW identity workflows.

Deferred scope¶

Other account tabs, bucket and workspace forms keep their existing default presentation. Audit them separately before adoption; reuse the canonical settings components without expanding permissions or changing storage semantics. Converting the rest of the application's boolean controls and global translation are separate decisions. Private S3 connection inventories retain their existing table/editor behavior and translation scope.

The current full-configuration API has no atomic concurrency lock. The client refuses conflicts present at its pre-save read; eliminating the residual race would require a separate server concurrency contract.

Table and listing convergence — completed¶

The six workspaces now share table typography, action/button geometry, badges, search/filter controls and pagination through the listing foundation. This supersedes the endpoint-only presentation described above; endpoint information limits remain specific to that inventory. Native and dialog tables adopt the same foundation, while Browser densities, bucket operation engines and grouped rules retain their documented geometry.

npm run listings:check prevents renewed local action/badge geometry and legacy table classes. The complete presentation inventory records routes, secondary tables, dedicated tests and the nine fixture families. The measured desktop rows stay equally dense or become shorter; actions remain on one line when space permits. API, permissions, translations, data and draft protections are unchanged. The remaining page/form refactors are still separate passes.