feat(frontend): work through the dashboard design audit

[TheMeinerLP]

Description

Targets main directly. Six commits, each self-contained, working through a design audit of the dashboard.

This also re-lands #11. That pull request was merged into feat/tailwind-dashboard-ui, but by then #10 had already been squash-merged into main, so its target had become a dead end and its content never reached main. Checked rather than assumed: main contained neither Reconnect in ConsoleView.vue nor bottom-right in helpers/toast.js. The commit rides along here unchanged, so nothing is lost and #11 needs no further action.

Once this merges, feat/tailwind-dashboard-ui and fix/frontend-broken-states are both stale and can be deleted.

What is in it

fix: tell the user what is wrong instead of showing nothing. The console rendered an empty white rectangle whenever the log stream failed, announced only by a toast that faded. It carries its own state now, with a reason and a Reconnect button. Toasts moved out of the top right corner, where they covered the logout button. The sign-in button was filled the same grey this interface gives a disabled control. Upload sat inside the file list looking like a directory row.

Two defects found while reading that code: nothing ever closed the log stream, so every visit to the Console tab left another EventSource running; and every .catch that formatted an error read error.response.status directly, which throws for a server that never answered, taking the handler with it, so the most common failure produced no message at all.

feat: give the working views their screen back. The avatar, description and organisation link sat in the page header, above the console, the settings form and everything else. 356px of chrome before the first line of content. They describe the repository, so the overview tab renders them now: Console 1123px to 935px, Dashboard 1404px to 1216px, Settings 3056px to 2868px. The snippet card's own second tab implementation is gone, as is the bare capital A the theme control used to announce its third mode with.

fix: stop claiming the request chart is grouped by day. The backend groups resolved requests by statistics.resolvedRequestsInterval, which defaults to MONTHLY, and AllResolvedResponse carries no hint of which interval produced it. The subtitle asserted a granularity it could not know, and named the wrong one on a default instance. My own error, from #10.

feat: size the console to the viewport and compact its filters. The panel was 36rem tall on every screen. It measures where it actually starts rather than subtracting a constant for the chrome above it, which would already be wrong after the header change above. Measured in a browser: 606px at 1440x900, 406px at 1440x700, 534px at 390x844. The six level checkboxes are toggle chips that wrap instead of overflowing, are buttons rather than labels, and signal their state through border style, marker fill and label weight, never colour alone.

refactor: style the settings form through the renderer API. The settings view restyled the JSONForms renderers of @dzikoysk/vue-vanilla by overriding their selectors from outside, reaching into markup this repository does not write. The library exposes a styles object for exactly this. The global block that reached into the library went from 24 @apply rules to 13, and each survivor carries a comment saying why it cannot move.

refactor: rebuild the token list out of components. TokensView.vue carried 53 @apply rules in a scoped stylesheet, every one of them targeting markup it renders itself. Pasting those declarations into class attributes would have been a step backwards, so the repeating pieces became components instead, the pattern StatTile.vue and ChartCard.vue already set. The stylesheet is gone, the file went from 313 to 246 lines, the three row actions carry accessible names and the destructive one is distinguishable at rest, 3y old · ∞ reads 3 years old · never expires, and a fake usage metric for a sparkline Ingot never measured is deleted.

Type of change

• fix - bug fix
• feat - new feature
• refactor - internal change without behaviour change

How was this tested?

Pixel comparison, view by view, against the state before each change, five views times two themes times two viewports:

View	Result
Overview	0, untouched
Settings	0 light, 7 pixels dark, antialiasing. The renderer-API refactor is invisible, which was its condition
Tokens	changed as intended
Console	changed as intended
Dashboard	live values plus the subtitle correction

Where a view did change, the difference was located band by band rather than accepted: when the toasts moved, settings differed in exactly two horizontal bands, y 12-75 and y 824-887, and nowhere else.

The console connection lifecycle was measured, not inferred: one request to /api/console/log on first mount, still one after leaving the tab, two after returning, three after pressing Reconnect. No stream left behind.

The token flows were driven end to end in a browser against the stub, because a refactor of that size cannot be reviewed by reading: search filtering, generating a token and seeing its secret once, editing a token and saving, adding a route, revoking with the confirmation cancelled, then revoking for real. All seven steps pass, no page errors.

Worth recording: the first three runs of that script reported failures which were all faults of the test, not the code. The route form has always submitted with Add rather than Save; the secret banner keeps the token name on screen, so asserting the row was gone matched the banner; and a text=/releases/... selector is read as a regular expression, whose leading slash makes invalid flags. The refactor had preserved every one of those behaviours exactly.

npm run eslint: 7 errors before this branch, 1 after. Five were stray semicolons in the console store, one a dead variable in the token view. ./gradlew build passes.

Checklist

• Commit messages follow the Conventional Commits convention documented in CLAUDE.md
• Tests cover the change, or the change is not testable and I explained why above
• ./gradlew build passes locally
• Documentation and configuration samples are updated if the change is user-facing
• Existing copyright headers are preserved; new files carry the appropriate header
• No credentials, tokens or personal data are included in the diff

The tests box stays unticked. The frontend has no test infrastructure and this branch does not add one. The verification above is reproducible but not committed, and the console connection lifecycle in particular deserves a real test.

Found along the way, not fixed here

StorageProvider.usage() returns -1 on both the filesystem and the S3 backend, because getFileSize returns -1 for a directory and no recursive walk exists. FixedQuota.canHold and PercentageQuota.canHold are its only consumers, so they compute maxSize - (-1): storage quota enforcement is effectively a no-op. That is a backend defect with nothing to do with this pull request and should get its own issue.

Still open from the audit

The Overview list itself. It comes from GET /api/maven/details/, which returns { "type": "DIRECTORY", "name": "releases" } per repository and nothing else. Of the four things worth showing there, visibility is already in memory on every Repository and would cost one field on that response with no leak risk, since private and hidden repositories are filtered out before the caller sees them; a per-repository request count is free for managers today from the payload the dashboard already fetches; size and last deployment are both new backend work, the first needing a cached value rather than a directory walk per page load.