the exposed slot rename bug.

### Prerequisites

- [x] I am running the latest version of ComfyUI
- [x] I have custom nodes enabled

### What happened?

I changed the name of the exposed slot in the sub-view. When I then viewed the exposed slot in the parent view, the name was correct. However, after refreshing the page, the exposed slot name reverted to its default naming instead of the name I had changed it to.

### Steps to Reproduce

1. I performed the renaming of the exposed slot within the sub-view.

2. Returning to the parent view, I confirmed that the renaming had taken effect.

3. After refreshing the page, the name reverted to the default.

### Workflow

[test.json](https://github.com/user-attachments/files/32088051/test.json)

### How is this affecting you?

Visual/UI issue only

### ComfyUI Frontend Version

1.51.9

### Browser

Chrome/Chromium

### Console Errors

```javascript

```

### Logs

```shell

```

### Additional Context

_No response_

Start by loading the linked test.json workflow in ComfyUI Frontend 1.51.9, rename an exposed slot in the sub-view, return to the parent view, and refresh. Trace where the renamed value is persisted and restored; done means the custom exposed-slot name remains unchanged after a page refresh.

Written by the indexing model from the issue text.