a standalone server service, and using the api to log off, the service won't log off.

I'm running a standalone server service, and using the api to log off, the service won't log off.
---

#### Reproduction Steps

I run a standalone server service
`agent -server -bootstrap -ui -client=0.0.0.0 -bind=0.0.0.0`
Register the service with the following command
```
curl -X PUT \
http://172.27.0.2:8500/v1/agent/service/register \
-H 'Content-Type: application/json' \
-H 'X-Consul-Token: d08900e2-4886-6495-02e7-17464a308d98' \
-d '{
"Name": "matrix-register-jsonrpc-service",
"ID": "order-80-03",
"Address": "172.27.0.1",
"Port": 3000,
"Meta": {
"Protocol": "jsonrpc-http"
},
"Check": {
"DeregisterCriticalServiceAfter": "90m",
"HTTP": "http://172.27.0.1:3000",
"Interval": "10s",
"Timeout": "5s"
}
}'
```
Then log out of the service using the api to logout the service, it returns 200 Logout Successful, but I can still see the service still running in web-ui
```
PUT http://172.27.0.2:8500/v1/agent/service/deregister/order-80-03
X-Consul-Token. d08900e2-4886-6495-02e7-17464a308d98
```

### Consul info for both Client and Server

Client info

```
agent:
check_monitors = 0
check_ttls = 0
checks = 0
services = 0
build:
prerelease =
revision = 24bf2b62
version = 1.21.3
version_metadata =
consul:
acl = enabled
bootstrap = true
known_datacenters = 1
leader = true
leader_addr = 172.27.0.2:8300
server = true
raft:
applied_index = 363
commit_index = 363
fsm_pending = 0
last_contact = 0
last_log_index = 363
last_log_term = 4
last_snapshot_index = 0
last_snapshot_term = 0
latest_configuration = [{Suffrage:Voter ID:b638876f-b72b-d70f-91f0-d0761cbe06ec Address:172.27.0.2:8300}]
latest_configuration_index = 0
num_peers = 0
protocol_version = 3
protocol_version_max = 3
protocol_version_min = 0
snapshot_version_max = 1
snapshot_version_min = 0
state = Leader
term = 4
runtime:
arch = amd64
cpu_count = 16
goroutines = 188
max_procs = 16
os = linux
version = go1.23.10
serf_lan:
coordinate_resets = 0
encrypted = false
event_queue = 1
event_time = 4
failed = 0
health_score = 0
intent_queue = 0
left = 0
member_time = 1
members = 1
query_queue = 0
query_time = 1
serf_wan:
coordinate_resets = 0
encrypted = false
event_queue = 0
event_time = 1
failed = 0
health_score = 0
intent_queue = 0
left = 0
member_time = 1
members = 1
query_queue = 0
query_time = 1
```

```

```

Server info

```
Stand Alone in one
```

```
Server agent HCL config
```

### Operating system and Environment details

### Log Fragments

Start by reproducing the standalone Consul server setup with the service registration request, then call PUT /v1/agent/service/deregister/{service ID} and compare the agent state with the web UI. Done means the API response and the UI consistently show that order-80-03 is no longer registered; the issue names no source files or tests to inspect.

Written by the indexing model from the issue text.