### System details

Omarchy 4.0.0-1, Lenovo Ideapad 5

### What's wrong?

After upgrading to Omarchy Quattro, I migrated an eduroam WPA2-Enterprise connection to NetworkManager.

The NetworkManager connection itself works correctly. nmcli reports that the Wi-Fi device is connected to eduroam and that Internet connectivity is full. However, the Omarchy Quickshell network panel shows the same connection as 'NOT CONNECTED'. The panel displays the correct IP address, gateway, ping, packet loss, and traffic statistics, so it clearly detects the active interface at some level.

<img width="495" height="222" alt="Image" src="https://github.com/user-attachments/assets/c9f92a41-69af-45b7-a398-bac0c1c0ae02" />

Some nmcli information:

`$ nmcli general`
STATE      CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN     METERED
connected  full          enabled  enabled  missing  enabled  no (guessed)

`$ nmcli -f DEVICE,TYPE,STATE,CONNECTION device`
DEVICE  TYPE      STATE                   CONNECTION
wlo1    wifi      connected               eduroam
lo      loopback  connected (externally)  lo

`$ nmcli -t -f NAME,TYPE,DEVICE connection show --active`
eduroam:802-11-wireless:wlo1
lo:loopback:lo

`$ nmcli -f NAME,UUID,TYPE connection show | grep -i eduroam`
eduroam 27924dd4-0861-44f1-9871-df9ffde3ecc9 wifi

If I click the eduroam network row in the panel, it asks for an enterprise identity and password again.

<img width="489" height="183" alt="Image" src="https://github.com/user-attachments/assets/81214ab5-bd38-4fbb-8ae8-ee5e7cf50f51" />

Entering the same credentials there fails with Wrong password, disconnects the otherwise working connection, and I then have to reconnect through NetworkManager.

# Relevant panel behavior

The current network panel derives connected Wi-Fi state from the Quickshell WifiNetwork.connected property:

```
readonly property var connectedWifiNetwork: findConnectedWifiNetwork()

function findConnectedWifiNetwork() {
    var networks = wifiNetworkObjects || []
    for (var i = 0; i < networks.length; i++) {
        if (networks[i] && networks[i].connected) return networks[i]
    }
    return null
}
```
and then determines the overall state with:

```
readonly property string kind: {
    if (wiredDevice && wiredDevice.connected) return "ethernet"
    if (connectedWifiNetwork) return "wifi"
    return "disconnected"
}
```

In this case, connectedWifiNetwork appears to remain null even though NetworkManager reports wlo1 as connected to eduroam.

At the same time, the panel separately obtains active-interface information through omarchy-network-status --verbose, which explains why it can display the correct IP, gateway and traffic data despite showing NOT CONNECTED.

The row logic also relies on net.connected and net.known. When the enterprise network is not recognized as known/connected, clicking it opens the credential prompt instead of using the existing NetworkManager profile.
For enterprise Wi-Fi, the panel then runs its own enterprise-connect path rather than simply activating the existing NetworkManager connection.

# Expected behavior
An already-active WPA2-Enterprise NetworkManager connection should be shown as connected, and clicking it should not prompt for credentials or replace/reconfigure the working profile.