feat: Add command to show existing profiles in the CLI

[Rockyy174]

No description provided.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• In executeAuthProfiles, the active profile marker is based on config.activeProfile while ordering in getOrderedProfileNames falls back to DEFAULT_PROFILE, which can lead to no profile being marked active when activeProfile is unset; consider using the same fallback logic for both ordering and marker calculation.
• executeAuthProfiles writes directly to console.log instead of using the existing output abstractions (e.g., printInfo/dependency injection as in other auth flows); aligning this with the existing pattern would make output behavior more consistent and easier to test or redirect.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In `executeAuthProfiles`, the active profile marker is based on `config.activeProfile` while ordering in `getOrderedProfileNames` falls back to `DEFAULT_PROFILE`, which can lead to no profile being marked active when `activeProfile` is unset; consider using the same fallback logic for both ordering and marker calculation.
- `executeAuthProfiles` writes directly to `console.log` instead of using the existing output abstractions (e.g., `printInfo`/dependency injection as in other auth flows); aligning this with the existing pattern would make output behavior more consistent and easier to test or redirect.

## Individual Comments

### Comment 1
<location path="cli/src/auth/profiles.ts" line_range="16-17" />
<code_context>
+  console.log("Saved CLI profiles:");
+
+  for (const profileName of profileNames) {
+    const profile = config.profiles[profileName] ?? {};
+    const isActive = profileName === config.activeProfile;
+    const marker = isActive ? "*" : "-";
+    const label = isActive ? `${profileName} (active)` : profileName;
</code_context>
<issue_to_address>
**issue:** Align active-profile detection here with the trimming logic used in `getOrderedProfileNames`.

`getOrderedProfileNames` normalizes the active profile with `config.activeProfile?.trim() || DEFAULT_PROFILE`, but here you compare `profileName === config.activeProfile` directly. If `config.activeProfile` has surrounding whitespace, the ordering will treat the trimmed name as active while this loop never does. Normalize once (e.g. `const activeProfile = config.activeProfile?.trim() || DEFAULT_PROFILE;`) and reuse it here when computing `isActive`.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}