## Description

In the Shibumi network panel (`hancore.shibumi.network`), clicking the "Connect" button on a protected WiFi network that hasn't been saved before has no effect — the password prompt never appears. This affects WPA2, WPA3, and enterprise networks.

## Root Cause

The `runPrimary()` function in `NetworkPanel.qml` (line 147-165) checks `entry.network` to decide whether to open the password prompt:

```javascript
if (entry.network && !entry.known
    && (entry.securityKind === "psk"
      || entry.securityKind === "enterprise")) {
  openPassword(entry)
  return
}
```

However, the network data originates from the Quattro panel's `wifiRow()` function (`Model.js` line 264-278), which deliberately returns primitive snapshots without the live `WifiNetwork` QObject to avoid segfaults:

```javascript
function wifiRow(network) {
  return {
    connected: !!network.connected,
    known: !!network.known,
    ssid: network.name || "",
    signal: Math.round((network.signalStrength || 0) * 100),
    security: network.security
  }
}
```

The `mergedNetworks()` function in `Service.qml` (line 274) maps this as `source.network || null`, which is always `null`.

This means `entry.network` is always `null` for visible networks, so:
1. The password prompt never opens (the `entry.network` guard is always false)
2. `connect()` in Service.qml returns false immediately (`!entry.network || ready` at line 347)
3. `connectWithPassphrase()` and `connectEnterprise()` also fail the same check (lines 357, 365)

## Steps to Reproduce

1. Open the Shibumi network panel
2. Click on a protected WiFi network you haven't connected to before (e.g. WPA2 or WPA3)
3. Click "Connect"
4. Nothing happens — the password prompt should appear but doesn't

## Expected Behavior

The inline password prompt should appear, allowing the user to enter the WiFi passphrase.

## System Details

- Omarchy version: 4.0.0-1
- CPU: 11th Gen Intel Core i7-1185G7
- GPU: Intel Iris Xe Graphics
- Network: WPA3 (COMP_ENG1) and WPA2 networks affected

## Suggested Fix

The `entry.network` checks in `runPrimary()`, `connect()`, `connectWithPassphrase()`, and `connectEnterprise()` should be relaxed. Since the Quattro panel omits the live `WifiNetwork` object from row data, these functions should rely on other indicators (like `entry.visible` or `entry.ssid`) to determine availability, and resolve the network object internally via a lookup (similar to how the Quattro panel uses `networkForSsid()`).