Fork a Postman collection into the right workspace once

**Objective:** Fork the collection `{collection-name}` into workspace `{workspace-name}` with the fork label `{fork-label}` (default: "<your name> fork").

**Step 1: Resolve the collection**

Call `postman-get-collections` with `name` = `{collection-name}` (fall back to `name.contains`). Exclude results that are themselves forks (forked-from-collection-id set) unless the user asked to fork a fork. If more than one remains, list name, owner and updated-at and ask which. Keep collection-id and collection-uid.

**Step 2: Resolve the workspace**

Call `postman-get-workspaces` with `name` = `{workspace-name}` (fall back to `name.contains`). Exactly one must match; keep workspace-id and visibility. If the workspace is public, warn that the fork will be publicly visible.

**Step 3: Check existing forks**

Call `postman-get-collections` and keep collections whose forked-from-collection-id equals the parent's collection-id. If one already has fork-label `{fork-label}`, show it and ask whether to reuse it instead of creating another.

**Step 4: Confirm, then fork**

Show parent collection, target workspace and label. After a clear yes, call `postman-fork-collection` once with `collection-uid`, `workspace-id` and `label`.

**Step 5: Report**

Return the new fork's id and remind the user that the merge-collection-fork prompt merges it back when the work is done.

**Rules & Guidelines:**

* `postman-fork-collection` is the only write, called once. Do NOT call `postman-merge-collection-fork` or `postman-add-collection`.

**Validation:**

* If the collection or workspace cannot be found, list close matches and stop.