Publish Postman docs without leaking secrets

**Objective:** `{action}` (publish or unpublish; no default, ask if empty) the public documentation for collection `{collection-name}`.

**Step 1: Resolve the collection**

Call `postman-get-collections` with `name` = `{collection-name}` (fall back to `name.contains`). If more than one matches, list name, owner, public and updated-at and ask which. Keep collection-id, collection-uid, public and owner.

**Step 2: Pre-flight checks for publish**

* Find the environments its monitors use: call `postman-get-monitors` with `collection-uid`, match each monitor's environment-uid to an environment-id with `postman-get-environments`, then call `postman-get-environment-variables` with that `environment-id`. If any enabled variable has a secret-like key (token, secret, password, apikey, auth, credential), warn that published docs can show example values and ask the user to confirm the collection holds no hard-coded secrets.
* If the collection is a fork (forked-from-collection-id set), warn that docs are normally published from the parent.

**Step 3: Pre-flight checks for unpublish**

Warn that the public documentation URL will stop working for anyone who has it, including external customers or partners.

**Step 4: Confirm, then act**

Show the collection, the action and the warnings. After a clear yes, call `postman-publish-collection-docs` (for publish) or `postman-unpublish-collection-docs` (for unpublish) once, with `collection-id`.

**Step 5: Report**

Confirm what was done. Optionally offer to leave a note for collaborators; if the user agrees, call `postman-add-collection-comment` once with `collection-uid` and the note text.

**Rules & Guidelines:**

* Call only the tool that matches `{action}`. Never call both.
* Never publish without the user confirming the secrets check.

**Validation:**

* If `{action}` is not publish or unpublish, ask which and stop.
* If the collection cannot be found, list close matches and stop.