## What happened

`dip <port>` can kill processes that are not SSH port forwards — including the shell it was typed in.

## Cause

In `default/bash/fns/ssh-port-forwarding`, `dip()` runs:

```bash
pkill -f "ssh.*-L ${port}:localhost:${port}" && echo "Stopped forwarding port $port" || echo "No forwarding on port $port"
```

`pkill -f` matches the pattern against the **full command line of every process on the system**, not just `ssh` processes. The pattern is unanchored, so any process whose command line happens to contain that text is killed too.

This is easy to hit unintentionally: a shell running a script that mentions the port, an editor with the string in its arguments, or a terminal whose command line includes the forwarding spec will all match.

## What was expected

Only the SSH forward for that port is terminated.

## Steps to reproduce

```bash
# A process that is not ssh but whose command line contains the pattern
bash -c "exec -a 'notssh -L 9000:localhost:9000' sleep 300" &

dip 9000
# -> reports "Stopped forwarding port 9000" and kills the unrelated process
```

I hit this for real while testing: `dip` matched the shell running the test — whose command line contained the port string — and killed it.

## Fix

Anchor the pattern to an actual `ssh` process:

```bash
pkill -f "^([^ ]*/)?ssh .*-L ${port}:localhost:${port}"
```

`lip()` has the same unanchored pattern and will likewise list unrelated processes; the same anchor applies:

```bash
pgrep -af "^([^ ]*/)?ssh .*-L [0-9]+:localhost:[0-9]+"
```

Verified: with the anchor, a decoy process carrying the same text in its command line survives while the real forward is stopped.

## System

- Omarchy 4.0.1-1
- `/usr/share/omarchy/default/bash/fns/ssh-port-forwarding`, line 14