4 Commits

Include renames

Author	SHA1	Message	Date
mrhid6	21238fe707	feat(web): typed confirmations on destructive actions; toasts for API outcomes ... Destructive actions were confirmed by a second danger button rendered where the first one had been, so a double click on Remove deleted the thing without the operator ever reading which thing it was. Servers, monitors, secret keys and sign-in providers now go through ConfirmDialog with requireTyped, matching the secret-group delete that already worked this way. Notification channels and vulnerability alert rules get an untyped dialog: both are a name and a URL and are rebuilt in a minute, but neither had any confirmation at all, and both silently stop alerts that nobody misses until an incident goes unannounced. Mutations otherwise succeeded in silence, or reported into whatever inline banner the page happened to own. Two failure modes came of that: a modal that closed on error left the message nowhere to land, and a save that was rejected left the old values on screen looking exactly like a save that worked (/settings had no error path at all). Every mutation now reports through the existing toast context. Errors stay inline where the surface that raised them is still on screen and the message is a correction to make in it: form validation, the cron field, the tag rows, a rejected licence blob, and the workflow designer's autosave, which is a standing condition rather than an event. Everything else toasts. Ad-hoc feedback removed in favour of it: the "Sent!" button labels on the server maintenance tab, the settings "Saved!" flag, the channel test line, and the steps page's notice/error pair.	2026-08-10 14:26:02 +01:00
mrhid6	d559cccd44	feat: Updated server page	2026-08-07 16:21:17 +01:00
mrhid6	2de7ac116b	feat: filter the fleet by tag and target workflows by tag selector	2026-08-04 13:42:47 +01:00
mrhid6	fa1fd14ed1	feat: view and edit server tags	2026-08-04 13:38:42 +01:00