Correct Source registry Console control sizing and responsive layout

[gbaudrit]

Area

Console

Description

The Source registry Console introduced in #281 does not consistently apply the existing form and data-table layout patterns. On the registration detail page, boolean controls and their labels are oversized or detached, while the refresh-policy fields become compressed and their labels run into adjacent controls. On the registration list, status, activation, refresh, and management actions are packed into a single row without a clear responsive hierarchy.

This issue records the UX follow-up separately so that it does not block the functional Registry delivery in #281. It is limited to presentation and interaction layout; Registry contracts, policies, refresh behavior, trust evaluation, and import behavior are out of scope.

Expected behavior

• Boolean settings use the established Console checkbox or switch component with a consistent control size, label position, focus state, and clickable area.
• The registration form uses a responsive grid that keeps every label associated with its control and prevents labels or controls from colliding at supported desktop and mobile widths.
• Refresh-policy fields preserve readable spacing and ordering, including when periodic refresh is disabled.
• The registry list provides a clear visual hierarchy for identity, endpoint type, freshness, activation, and row actions, and remains usable without clipped or overlapping content.
• The official-registry marker and the Refresh now and Manage actions remain easy to identify.
• English and French rendering tests cover the corrected controls and layout structure.
• Desktop and mobile smoke tests confirm the form and list at representative viewport sizes, with keyboard focus and horizontal overflow checked explicitly.

Observed behavior

• Enabled, Allow HTTP, and Allow private network addresses render with inconsistent native checkbox sizes and label alignment.
• Refresh-policy labels and numeric inputs are laid out too tightly and visually collide across columns.
• The periodic-refresh control is visually disconnected from the fields it governs.
• Registry status and row actions are crowded in the list view, reducing scanability.

Reproduction steps

1. Check out the branch or preview for PR feat(console): manage source registries and discovery #281.
2. Start Agentstration.Web with the Development bootstrap profile and sign in as a Platform Administrator.
3. Open System > Source registries.
4. Review the official registry row at a desktop width.
5. Open Manage for the official registry and review the identity, connection, and refresh-policy sections.
6. Resize the viewport across desktop and mobile widths and observe the control sizing, label alignment, field wrapping, and row actions.

Environment

PR #281 (codex/249-registry-console), .NET 10, Development bootstrap profile, default local SQLite storage. Exact browser and operating-system versions from the supplied screenshots were not recorded.

Observed impact

Minor

Regression

No — these Registry Console pages are new in PR #281.

Relevant logs

No runtime error is required to reproduce the visual defects.

Attachments

Two screenshots supplied during review show the affected registry detail form and registry list. They should be attached to this issue in GitHub when available from the review client.

Preliminary checks

• I searched for an existing issue covering this behavior.
• I removed secrets, credentials, personal data, and sensitive content from this report.