Find the Postman collections nobody is monitoring

**Objective:** Audit Postman monitor coverage for collections whose name contains `{collection-name}` (default: all collections), and report what is unmonitored, paused or broken.

**Step 1: Load the collections**

Call `postman-get-collections`, using `name.contains` = `{collection-name}` when it is given. Keep each collection's name, collection-id, collection-uid, owner, forked-from-collection-id and updated-at. Treat collections with a forked-from-collection-id as forks and report them separately; forks are usually not monitored on purpose.

**Step 2: Load the monitors**

Call `postman-get-monitors` with no filters (or once per collection using `collection-uid` if the collection list is short). Keep monitor-id, name, active, collection-uid and environment-uid.

**Step 3: Load the environments**

Call `postman-get-environments` and keep environment-uid and name, so each monitor's environment can be named.

**Step 4: Cross-check**

* Unmonitored: a non-fork collection whose collection-uid appears on no monitor.
* Paused: a monitor with active = false.
* Orphaned: a monitor whose collection-uid matches no collection, or whose environment-uid is set but matches no environment.
* Thin coverage: a collection monitored only by paused monitors counts as unmonitored.

**Step 5: Report**

Four tables: Unmonitored collections (name, owner, last updated), Paused monitors (monitor name, collection, environment), Orphaned monitors (monitor name, what is missing), and Forks (name, parent collection-id). Finish with a one-line count of collections, monitors and gaps, and a short recommendation list ordered by most recently updated unmonitored collection first.

**Rules & Guidelines:**

* This is read-only. Do NOT call `postman-add-monitor`, `postman-update-monitor`, `postman-run-monitor` or any other add, update, run, fork, merge or publish tool.
* Match on UIDs, not on names. Two collections can share a name.
* The monitors list does not carry schedules or run results; do not claim a monitor is failing or how often it runs.

**Validation:**

* If no collections match, say so and stop.
* If there are no monitors at all, report every non-fork collection as unmonitored in one table and stop.