docs: update terminology to use inclusive language

Updated references per Salesforce Inclusive Product Language initiative:
- Use 'main branch' in narrative/documentation
- Clarify technical reality: '(master in api-console repo)'
- Commands remain functional with current branch names

Files updated:
- .claude/skills/update-api-console-components/SKILL.md
- CLAUDE.md (release process, branch references)
- docs/team/runbooks/api-console-v6-release.md

Approach: Use inclusive language while acknowledging current repo state.
Some component repos have both 'main' and 'master' branches but only one
is active. This approach works for all cases.

Related: W-21315032

Author: alexpmule

.claude/skills/update-api-console-components/SKILL.md

@@ -49,12 +49,12 @@ Ask user for:
 
 ## Steps
 
-### 1. Verify location and checkout master
+### 1. Verify location and checkout main branch
 
 ```bash
 cd ~/mulesoft/context/products/api-console/v6/api-console
 git status  # Verify we're in correct repo
-git checkout master
+git checkout master  # Main branch (currently named 'master' in api-console repo)
 git pull
 ```
 
@@ -228,7 +228,7 @@ After api-console PR is merged and new version is published to npm (automatic vi
 ```bash
 cd ~/mulesoft/context/products/api-console/wrapper
 git status  # Verify we're in correct repo
-git checkout master
+git checkout master  # Main branch (currently named 'master' in wrapper repo)
 ```
 
 #### 2. Configure GPG signing (CRITICAL)
@@ -515,7 +515,7 @@ npm ls @api-components/<component>
 - **Build number**: Optional, use semantic version instead (X.X.X)
 - **Components are separate repos**: Under `advanced-rest-client` GitHub org, NOT `mulesoft`
 - **AMF models**: Not affected by component updates (unless AMF version changes)
-- **CI/CD**: GitHub Actions automatically publishes to npm after merge to master
+- **CI/CD**: GitHub Actions automatically publishes to npm after merge to main branch
 - **Downstream consumers**: ACM, Exchange, API Designer will pick up new version on their next update cycle
 
 ## Related Documentation

CLAUDE.md

@@ -417,7 +417,7 @@ echo "fix(api-console): resolve issue" | npx commitlint
 1. Update `package.json` version
 2. Update `CHANGELOG.md`
 3. Commit with message: `chore: bump version to X.Y.Z`
-4. Push to `master` → triggers GitHub Action
+4. Push to main branch (master in api-console repo) → triggers GitHub Action
 5. GitHub Action publishes to npm if version changed
 
 **npm Package**: [`api-console`](https://www.npmjs.com/package/api-console)
@@ -438,15 +438,15 @@ echo "fix(api-console): resolve issue" | npx commitlint
 - api-console releases: `build/<build-number>`
 
 **Note**: Some components use older branches:
-- `advanced-rest-client/authorization` → use `support/0.1` branch (NOT master)
+- `advanced-rest-client/authorization` → use `support/0.1` branch (NOT main branch)
 
 ### v6 Release Process
 
 **Schedule**: Every 3 weeks on Fridays
 **Calendar**: [API Designer release calendar](https://salesforce.quip.com/link-to-calendar)
 
 **Steps**:
-1. Checkout `api-console` master branch
+1. Checkout `api-console` main branch (master in api-console repo)
 2. Create branch: `build/<build-number>`
 3. Check GUS build version for tickets with component+version comments
 4. Update components: `npm update <component-name>` for each fix
@@ -455,7 +455,7 @@ echo "fix(api-console): resolve issue" | npx commitlint
 6. Create PR → wait for approval → merge
 7. Auto-published to npm
 8. **Update anypoint-api-console wrapper**:
-   - Checkout `anypoint-api-console` master
+   - Checkout `anypoint-api-console` main branch (master in wrapper repo)
    - Update `builder/package.json` with new api-console version
    - Verify component versions: `npm ls @api-components/api-type-document`
    - **If component not updated**: Delete `package-lock.json` + `node_modules/` in `builder/`, run `npm i`, verify again

docs/team/runbooks/api-console-v6-release.md

@@ -55,11 +55,11 @@ For each ticket in "Pending Release":
 - Search in `mulesoft` org (console repo)
 - Search in `advanced-rest-client` org (individual components)
 
-### Step 2: Checkout Master and Create Branch
+### Step 2: Checkout Main Branch and Create Branch
 
 ```bash
 cd ~/mulesoft/context/products/api-console/v6/api-console
-git checkout master
+git checkout master  # Main branch (currently named 'master' in api-console repo)
 git pull
 ```
 
@@ -275,7 +275,7 @@ If not published yet, wait a few minutes and check GitHub Actions status.
 
 ```bash
 cd ~/mulesoft/context/products/api-console/v6/anypoint-api-console
-git checkout master
+git checkout master  # Main branch (currently named 'master' in wrapper repo)
 git pull
 ```
 
@@ -481,7 +481,7 @@ This entire workflow is automated via Claude Code skill:
 
 **What it does**:
 1. Prompts for component list + versions
-2. Checks out master + creates branch
+2. Checks out main branch + creates release branch
 3. Updates components + verifies
 4. Configures GPG signing
 5. Bumps version + commits