### System details

- Motherboard: ASUS ROG STRIX Z390-H GAMING   - CPU: Intel Core i9-9900K @ 3.60GHz (16 cores)   - RAM: 31GB   - GPU: NVIDIA GeForce RTX 4060

### What's wrong?

# Bug Report: Elephant Index Out of Range Runtime Error

## Summary
Elephant service enters a corrupted state causing "index out of range" runtime panics that prevent application activation through Walker, despite applications being discoverable.

## Environment
- **OS**: Arch Linux (Omarchy custom distribution)
- **Desktop Environment**: Hyprland (Wayland)
- **Elephant Version**: 2.16.1
- **Walker Version**: 2.11.2
- **Session Manager**: uwsm

## Bug Description
The elephant service intermittently enters a corrupted state where it can successfully:
- Start and run normally
- Discover desktop applications (47 results found)
- Receive queries from Walker
- List providers correctly

However, it fails to activate applications due to runtime panics with "index out of range" errors.

## Reproduction Steps
1. Normal system startup with elephant service running
2. Launch Walker application launcher
3. Search for and select any desktop application
4. Application appears to be "launched" but never actually starts
5. Direct elephant commands also fail with same error

## Error Messages
```bash
$ elephant activate desktopapplications chromium
panic: runtime error: index out of range [1] with length 1

goroutine 1 [running]:
github.com/abenz1267/elephant/v2/internal/comm/client.Activate({0x7ffd22494d9a?, 0x112c701?})
	github.com/abenz1267/elephant/v2/internal/comm/client/activate.go:19 +0x37f
main.main.func13({0x113f4cc?, 0xc000456800?}, 0xc00018ba58?)
	github.com/abenz1267/elephant/v2/cmd/elephant/elephant.go:271 +0x2e
```

```bash
$ elephant query desktopapplications chromium
panic: runtime error: index out of range [2] with length 1

goroutine 1 [running]:
github.com/abenz1267/elephant/v2/internal/comm/client.Query({0x7ffed674cd9a?, 0x1129e32?}, 0x0, 0x0)
	github.com/abenz1267/elephant/v2/internal/comm/client/query.go:36 +0x7d2
```

## Expected Behavior
- Applications should launch normally when selected in Walker
- Direct elephant commands should work without panics
- Service should maintain consistent state

## Actual Behavior
- Walker shows applications but cannot launch them
- All elephant CLI commands fail with index panics
- Service appears healthy in systemd but is non-functional for activation

## Workaround
**Temporary Fix**: Restart the elephant service
```bash
systemctl --user restart elephant.service
```

After restart, normal functionality is restored:
```
INFO desktopapplications activated=google-chrome.desktop
received: app -- /usr/bin/google-chrome-stable
Started google-chrome-stable.
```

## Configuration Files
**Elephant Config** (`~/.local/share/omarchy/config/elephant/desktopapplications.toml`):
```toml
show_actions = false
only_search_title = true
history = false
```

**Walker Config** (`~/.config/walker/config.toml`):
```toml
force_keyboard_focus = true
selection_wrap = true
theme = "omarchy-default"
[providers]
default = ["desktopapplications", "websearch"]
```

## System Integration
- Applications launch correctly via terminal
- uwsm-app-daemon integration works when elephant is healthy
- systemd user services for app launching function properly
- Issue appears to be internal state corruption in elephant process

## Impact
- Complete loss of application launcher functionality
- Requires manual service restart to restore functionality
- Affects user workflow in Wayland/Hyprland environment

## Additional Notes
- Bug appears to be related to argument parsing in client functions
- May be triggered by specific usage patterns or timing conditions
- Service restart always resolves the issue completely
- No data loss or configuration corruption observed

## Suggested Investigation Areas
1. Client command argument parsing logic in `activate.go:19` and `query.go:36`
2. State management between service startup and client connections
3. Potential race conditions in command processing
4. Memory corruption or concurrent access issues