the dashboard/server/:id page is very ugly. please use UI design best p…

[quarterback-ai-dev-environment]

Intent

the dashboard/server/:id page is very ugly. please use UI design best practices to rearrange the elements in a way that looks pleasant. Make sure to use DaisyUI components where possible. Please include screenshots in the PR so that the visual changes will be obvious.

Claims proven

• The dashboard server-detail page markup in web/templates/dashboard-server.html is restructured from its current single-card layout into a redesigned arrangement of its elements. (CAN)
• The redesigned dashboard server-detail page composes its elements out of DaisyUI component classes (e.g. card, badge, dropdown, btn, and any others appropriate to the new layout). (MUST)
• After the redesign, a manager viewing a server they belong to still sees the channel-configuration form: the reporting-channel select and its save control still render with the channel-region contract intact (id="channel-select", name="channel_id", options per text channel, and the hx-post to /dashboard/servers/{guildID}/channel). (MUST)
• After the redesign, a user who belongs to more than one guild still gets the server-switcher on the detail page: the rendered page contains a navigable link to each of the user's other servers at /dashboard/servers/{{GuildID}}. (MUST)
• After the redesign, a manager viewing the detail page still sees the manager badge distinguishing their elevated role. (MUST)
• After the redesign, a registered user still sees the unregister affordance and an unregistered user still sees the register affordance, each posting to its existing endpoint. (MUST)
• The redesign changes only the presentation of the dashboard server-detail page and does not alter the GuildPage handler's routing, data-loading, or access-control behavior. (MUST)
• The PR for this change carries before/after screenshots of the redesigned page when screenshot capture is feasible, and otherwise the code change alone (best-effort, per REQ-4's explicit fallback). (CAN)

Confidence: high

[trriplejay]

adding screenshots. original vs claude vs qb

Original:

qb:

claude:

personally feel like claude did the best job. qb still an improvement but does some things i dont like. this may not be an issue if qb can utilize an agents.md or use a particular skill to improve its output

[trriplejay]

went with the claude changes for now.