feat: onboard command now checks if component is already onboarded

Three modes:
- Mode A (fully onboarded): ask user if they want to add repos or just
  regenerate examples.md — skips mapping update if examples only
- Mode B (partially onboarded): collect new repos, merge with existing
  component entry, regenerate examples for all repos
- Mode C (new): full onboard flow as before

Detects mode by checking component-repository-mappings.json before
asking any questions.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>

Author: vmrh21

workflows/cve-fixer/.claude/commands/onboard.md

@@ -8,14 +8,49 @@ to `ambient-code/workflows` containing both the mapping update and the guidance
 
 ## Process
 
-1. **Collect Component Information**
+1. **Determine Mode — Check Existing Mapping**
+
+   Before asking any questions, load `component-repository-mappings.json` and check
+   whether the component is already onboarded:
+
+   ```bash
+   # Find mapping file
+   if [ -f "component-repository-mappings.json" ]; then
+     MAPPING_FILE="component-repository-mappings.json"
+   elif [ -f "workflows/cve-fixer/component-repository-mappings.json" ]; then
+     MAPPING_FILE="workflows/cve-fixer/component-repository-mappings.json"
+   fi
+
+   # Ask component name first
+   # Then check if it exists in the mapping
+   EXISTING=$(jq -r --arg name "$COMPONENT_NAME" \
+     'if .components[$name] then "found" else "not_found" end' "$MAPPING_FILE" 2>/dev/null)
+   ```
+
+   **Three modes based on what exists:**
+
+   **Mode A — Component already fully onboarded** (`EXISTING == "found"` and user confirms repos are correct):
+   - Show existing repos from the mapping
+   - Ask: "Your repos are already mapped. Do you want to: (1) Add new repos (2) Just regenerate examples.md guidance files (3) Cancel?"
+   - If option 2: skip to Step 5 (Generate examples.md only) — no mapping change needed
+   - If option 1: continue to collect new repos to add
+
+   **Mode B — Component exists, adding repos** (selected option 1 above):
+   - Collect only the NEW repos to add
+   - Merge with existing repos in the mapping
+   - Regenerate examples.md for all repos
+
+   **Mode C — New component** (`EXISTING == "not_found"`):
+   - Full onboard flow — collect component name, repos, validate Jira, etc.
+
+1a. **Collect Component Information** (Modes B and C only)
 
    Ask the user for the following, one question at a time:
 
    a. **Jira component name** — must match exactly what appears in Jira (case-sensitive).
       Example: `"AI Evaluations"`, `"llm-d"`, `"AutoML"`
 
-   b. **Repos** — for each repo:
+   b. **Repos** — for each repo to add:
       - GitHub URL (e.g. `https://github.com/org/repo`)
       - Repo type: `upstream`, `midstream`, or `downstream`
       - Subcomponent name (optional — only if this component has multiple distinct
@@ -142,6 +177,8 @@ to `ambient-code/workflows` containing both the mapping update and the guidance
    - If no containers discovered, omit the field (can be added later)
    - Omit `subcomponent` if not needed
    - Show the entry to the user: "Does this look correct? (yes/no/edit)"
+   - **Mode A (examples only)**: skip this step entirely — no mapping changes
+   - **Mode B (adding repos)**: merge new repos into existing component entry
 
 5. **Generate `.cve-fix/examples.md` Guidance**
 
@@ -239,13 +276,17 @@ to `ambient-code/workflows` containing both the mapping update and the guidance
    fi
    ```
 
-7. **Apply All Changes**
+7. **Apply Changes (mode-dependent)**
 
    ```bash
    cd /tmp/workflows-onboard
    BRANCH_NAME="onboard/${COMPONENT_NAME_SLUG}"
    git checkout -b "$BRANCH_NAME"
 
+   # Mode A: examples.md only — skip mapping update entirely
+   # Mode B: merge new repos into existing component entry
+   # Mode C: add new component entry
+
    MAPPING_FILE="workflows/cve-fixer/component-repository-mappings.json"
 
    # Add component to mapping file