@rail44.dev/goose

Add a unit test for the pure parser `parse_verify_profile` in `.claude/plugins/quacker-channel/src/cli.rs`. It's a private fn (around L167), so put the test in cli.rs's existing `#[cfg(test)] mod` (the module already holds the `acp dispatch goose` arg-parsing tests). Add a new `#[test] fn parse_verify_profile_*` — do NOT change `parse_verify_profile` itself or any other code.

The function: `parse_verify_profile(s: &str) -> Result<(String, String), String>` splits `s` on the **first** `=`; returns `Ok((name, command))` only when both sides are non-empty, else `Err`.

Cover exactly these cases (expected values verified against the impl):
- `parse_verify_profile("rust=just check")` → `Ok(("rust".to_string(), "just check".to_string()))`
- command containing `=` (splits on the FIRST `=`): `parse_verify_profile("web=pnpm run check --env=node")` → `Ok(("web".to_string(), "pnpm run check --env=node".to_string()))`
- empty name: `parse_verify_profile("=just check")` is `Err` (assert `.is_err()`)
- empty command: `parse_verify_profile("rust=")` is `Err`
- no `=` separator: `parse_verify_profile("rustjustcheck")` is `Err`

Constraints:
- Edit ONLY `.claude/plugins/quacker-channel/src/cli.rs`, and only ADD the one test fn inside the existing `#[cfg(test)] mod`. Change nothing else (no edits to `parse_verify_profile` or any other fn/test).
- Use plain `assert_eq!` / `assert!(... .is_err())`. Verify passes via `cargo nextest` (part of `just check`).