docs: remove v7-specific content from v6 documentation

Removed:
- v7 Release Process section (workflows belong in v7 repo)
- LWC Migration Context section (v7-specific context)
- Branch naming pattern reference to v7

Kept contextual references (ADR-003, version comparison table) that
explain the architectural landscape from v6 perspective.

Related: W-21315032

Author: alexpmule

CLAUDE.md

@@ -431,7 +431,7 @@ echo "fix(api-console): resolve issue" | npx commitlint
 
 **Branch Naming**:
 - Component fixes: feature branches (e.g., `feat/W-12345678-fix-auth`)
-- api-console releases: `build/<build-number>` (v6) or `feat/<release-ticket>/<version>` (v7)
+- api-console releases: `build/<build-number>`
 
 **Note**: Some components use older branches:
 - `advanced-rest-client/authorization` → use `support/0.1` branch (NOT master)
@@ -467,19 +467,6 @@ npm run prepare:api-console
 
 **Useful Tool**: Use `/update-api-console-components` skill for complete release workflow automation
 
-### v7 Release Process
-
-**Schedule**: Every 4 weeks on Tuesdays
-**Repository**: `api-console-lwc`
-
-**Steps**:
-1. Checkout `api-console-lwc` develop branch
-2. Create branch: `feat/<release-ticket>/<version>`
-3. Create PR to **both** `develop` and `master` → wait for approval → merge
-4. Auto-published to npm
-5. Create GitHub release (e.g., [v0.2.83](https://github.com/anypoint-web-components/api-console-lwc/releases))
-   - List all tickets (fixes + enhancements) in release notes
-
 ### Related Teams & Contacts
 
 API Console is embedded in multiple products. Escalate to these teams when needed:
@@ -519,16 +506,6 @@ npm i
 npm ls @api-components/api-type-document  # Verify component version
 ```
 
-### LWC Migration Context
-
-**Why v7 exists**: Salesforce Lightning Locker Service (API v40+) blocks custom web components. v6 uses Aura wrapper forced to API v39 (Spring '17 release).
-
-**Problem**: API v39 passed 3-year support commitment (Spring '20). Uncertain how long it remains supported.
-
-**Solution**: Migrating to native LWC (`api-console-lwc`) to avoid Aura wrapper and API version constraints.
-
-**Status**: Not all components migrated yet, some tests missing. See [LWC migration docs](https://salesforce.quip.com/link-to-lwc-migration).
-
 ## Important Constraints
 
 ### DO: