## Environment

- Omarchy: `4.0.4-1`
- Kernel: `7.2.5-3-omarchy x86_64`
- Hyprland: `0.56.2` (commit `efb5099`)
- CPU: 13th Gen Intel Core i7-1355U
- GPU: Intel Raptor Lake-P [Iris Xe Graphics]
- Chromium: `152.0.7977.82`
- Session: Wayland / Hyprland

## What happened

`default/hypr/apps/pip.lua` targets Google Meet's picture-in-picture overlay,
which Chrome titles `Meet - <name>` rather than "Picture-in-Picture":

```lua
-- Google Meet PiP uses the meeting title instead of "Picture-in-Picture".
o.window({ tag = "chromium-based-browser", title = "^Meet - .+" }, {
  tag = "-default-opacity",
  float = true,
  pin = true,
  size = { 600, 338 },
  keep_aspect_ratio = true,
  border_size = 0,
  opacity = "1 1",
  move = { "(monitor_w-window_w-40)", "(monitor_h-window_h-40)" },
})
```

The pattern `^Meet - .+` also matches the **real meeting window**, because a
normal browser window is titled `Meet - abc-defg-hij - Chromium` and the
trailing ` - Chromium` is absorbed by `.+`.

The meeting window is therefore forced to floating, pinned, and locked to
600x338. Because Hyprland refuses fullscreen on pinned windows, the meeting
cannot be maximized or fullscreened afterwards, and the usual bindings appear
to do nothing.

## Expected

Only the actual picture-in-picture overlay should be floated and pinned. The
meeting window itself should tile normally and remain maximizable.

## Steps to reproduce

No Google account required. The rule keys purely off the window title, so a
synthetic page with the same title reproduces it exactly:

```bash
cat > /tmp/meet-test.html <<'HTML'
<!doctype html><html><head><title>Meet - abc-defg-hij</title></head>
<body>rule test window</body></html>
HTML

chromium --new-window file:///tmp/meet-test.html
hyprctl clients -j | jq '.[] | select(.title|test("Meet - ")) | {title,floating,pinned,size}'
```

Result:

```json
{
  "title": "Meet - abc-defg-hij - Chromium",
  "floating": true,
  "pinned": true,
  "size": [600, 338]
}
```

Attempting to fullscreen it reports success but does nothing, since the window
is pinned:

```
$ hyprctl dispatch "hl.dsp.window.fullscreen({ address = '0x...', mode = 'fullscreen' })"
ok

before: float=true pinned=true fs=0 size=600x338
after:  float=true pinned=true fs=0 size=600x338
```

## Suggested fix

Only the PiP overlay drops the browser name from its title, so the trailing
browser suffix distinguishes the two. Narrowing the original match, or adding a
follow-up rule that re-tiles anything carrying that suffix, both work. I am
running the latter locally:

```lua
o.window({
  tag = "chromium-based-browser",
  title = "^Meet - .+ - (Chromium|Google Chrome|Brave|Microsoft.Edge|Vivaldi|Helium)$",
}, {
  tile = true,
})
```

With that in place the same reproduction gives:

```
floating=false  pinned=false  size=941x1054
fullscreen  -> fs=2  1920x1080
full width  -> fs=1  1920x1054
```

and the genuine PiP overlay still floats and pins as intended.

Note: a Meet window opened as an installed web app is unaffected, since its
class (for example `chrome-meet.google.com__-Default`) does not carry the
`chromium-based-browser` tag.