AX-1579 - Make MCP secret-persistence guidance shell-aware (#15)

## What
Replace the hardcoded `~/.zshrc` persistence instruction in the MCP
management template with shell-aware guidance.

## Why
The agent told users to persist MCP secret env vars by adding the
`export` to `~/.zshrc`, which only works for zsh. Users on
bash/fish/Linux/Windows added it to a file their shell never sources, so
the variable was silently lost on next launch and the IDE "ignored" the
config.

## Changes
- `plugins/jfrog/templates/jfrog-mcp-management.md`: secret-persistence
guidance now keys on the user's **shell, not the OS** — zsh →
`~/.zshrc`, bash → `~/.bashrc` (and macOS `~/.bash_profile`), fish →
`~/.config/fish/config.fish`, Windows → `setx` — and tells the agent to
detect the shell first.
- Bump plugin version `0.5.0` → `0.5.1`
(`plugins/jfrog/.cursor-plugin/plugin.json` +
`.cursor-plugin/marketplace.json`).

Author: YoniMelki

.cursor-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "JFrog Platform plugins for Cursor",
-    "version": "0.5.0",
+    "version": "0.5.1",
     "pluginRoot": "plugins"
   },
   "plugins": [

plugins/jfrog/.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "jfrog",
   "displayName": "JFrog Platform",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "JFrog Platform integration with MCP, security skills, supply-chain best practices, and JFrog Agent Guard governance for adding, removing, and listing MCP servers.",
   "author": {
     "name": "JFrog",

plugins/jfrog/templates/jfrog-mcp-management.md

@@ -165,11 +165,21 @@ Split Step 2 inputs by `isRequired`:
 For each input in Step 4:
 
 - **Secrets** (`isSecret=true`): use `${env:VAR_NAME}` in the config;
-  tell the user to export it via
-  `read -rs VAR_NAME && export VAR_NAME && echo exported`
-  (and add to `~/.zshrc` for persistence). They are picked up on next
-  launch (4a). NEVER take secrets in chat, echo them back, or
-  write raw values into config.
+  tell the user to export it for the current session via
+  `read -rs VAR_NAME && export VAR_NAME && echo exported`.
+  For persistence, the right startup file depends on the user's
+  **shell**, not their OS — macOS and Linux both commonly run zsh or
+  bash. Detect the shell (e.g. `echo "$SHELL"`) and add the export to
+  the file that shell loads on startup:
+  - **zsh** (the macOS default) → `~/.zshrc`
+  - **bash** → `~/.bashrc`; note macOS login shells read
+    `~/.bash_profile`, which usually sources `~/.bashrc`
+  - **fish** → `~/.config/fish/config.fish` (use `set -gx`)
+  - **Windows** → use `setx VAR_NAME "<value>"` (PowerShell/CMD)
+    instead of the `read`/`export` snippet
+  If unsure which file the shell sources, ask the user. Values are
+  picked up on next launch (4a). NEVER take secrets in chat, echo them
+  back, or write raw values into config.
 - **Non-secrets**: literal in `env` or `${env:VAR_NAME}` — ask if
   unclear.