list-connections

1> **Plugin check**: Run `node "${PLUGIN_ROOT}/scripts/check-version.js"` - if it outputs a message, show it to the user before proceeding.
2 
3**📋 Shared instructions: [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md)** — read first for cross-cutting concerns (Windows CLI compatibility, memory bank, etc.).
4 
5# List Connections
6 
7**App root:** before any project read or command, execute
8[app-working-directory.md](${PLUGIN_ROOT}/shared/references/app-working-directory.md).
9Reuse the resolved absolute `working_dir` for every shell call and
10file tool, including auth retries and the environment read used for portal URLs.
11Forwarded owner context is required for child calls; do not fall back to the
12launch directory. Reapply the guard and arguments in each fresh call.
13 
14Finds or creates a Power Platform connection with the Power Apps CLI. Returns the **Connection ID** or **Connection Reference** that callers feed into `pa app add data-source`.
15 
16## Workflow
17 
181. Get Connection → 2. Present Results
19 
20---
21 
22### Step 1 — Get Connection
23 
24**Telemetry checkpoint: `resolve_power_platform_connection`**
25 
26Use one of the supported paths below.
27 
28If the caller already provided a connection ID, validate the connector/API ID from context and return it as-is for `--connection-id`.
29 
30Preserve any supplied connection reference as well; do not create a replacement.
31Creation requires current approval for the selected environment and connector.
32…