rcourtman 8cea433443 Fix Docker host custom display name not persisting in UI (related to #662) ...

The custom display name feature added in cd627f33c had a critical bug where
the backend successfully stored custom names but the frontend never received
them, making the feature appear non-functional.

Root cause:
- DockerHost.CustomDisplayName was stored in backend state (models.go:201)
- SetDockerHostCustomDisplayName() correctly updated the field
- BUT DockerHostFrontend struct was missing customDisplayName field
- AND ToFrontend() converter didn't copy CustomDisplayName
- Result: WebSocket state broadcasts stripped out the custom name

When users edited a Docker host display name:
- API returned 200 OK ✓
- Success notification appeared ✓
- Edit state cleared ✓
- But subsequent state broadcasts lacked customDisplayName ✗
- UI continued showing original name ✗

Fix:
- Add CustomDisplayName field to DockerHostFrontend (models_frontend.go:105)
- Copy d.CustomDisplayName in ToFrontend() converter (converters.go:204)
- Now custom display names properly propagate to frontend via WebSocket

The feature now works as originally intended - custom names persist across
agent reconnections and display correctly in the UI.

2025-11-08 10:28:20 +00:00

..

cluster.go

Fix settings security tab navigation

2025-10-11 23:29:47 +00:00

concurrency_test.go

Fix settings security tab navigation

2025-10-11 23:29:47 +00:00

converters.go

Fix Docker host custom display name not persisting in UI (related to #662)

2025-11-08 10:28:20 +00:00

models_frontend.go

Fix Docker host custom display name not persisting in UI (related to #662)

2025-11-08 10:28:20 +00:00

models.go

Fix Docker host display bug when multiple agents share API tokens (related to #658)

2025-11-07 13:46:35 +00:00

state_snapshot.go

Add per-node temperature monitoring and fix critical config update bug

2025-11-05 14:11:53 +00:00