See every variable that differs between two Postman environments

**Objective:** Compare the Postman environment `{source-environment}` with `{target-environment}` (for example Staging against Production) and list every variable that would make a request behave differently between them.

**Step 1: Resolve both environments**

Call `postman-get-environments` with `name` = `{source-environment}`, then with `name` = `{target-environment}`. If an exact match returns nothing, retry with `name.contains`. If either resolves to more than one environment, list the matches (name, owner, updated-at) and stop.

**Step 2: Load the variables**

Call `postman-get-environment-variables` with `environment-id` for each environment. Keep key, value and enabled.

**Step 3: Compare by key**

* Only in source / only in target: the key exists on one side only. These break requests when switching environments.
* Enabled on one side, disabled on the other.
* Empty on one side, set on the other.
* Values that are identical in both, for keys that normally should differ between environments (base URLs, hosts, tokens, client ids). Flag these as a possible copy-paste mistake.

**Step 4: Report**

A table with columns key, source state, target state, problem. Show values only for non-secret keys (not containing token, secret, password, key, auth or credential) and truncate them to 40 characters. Put missing keys first. End with a one-line verdict: aligned, or N differences that need attention.

**Rules & Guidelines:**

* Key comparison is case-sensitive, as Postman's is. Mention keys that differ only by case as a likely typo.
* This is read-only. Do NOT call `postman-update-environment`, `postman-add-environment` or any other write tool.

**Validation:**

* If both names resolve to the same environment, say so and stop.
* If either environment has no variables, report that and list the other side's keys as missing.