docs(pw): align CLAUDE.md launch path + caveat pw SKILL.md MCP bullet (#978)

Two doc nits from #981 review: (1) CLAUDE.md's 'Not auto-registered' paragraph used
'integrations/<name>/src/index.ts' in one sentence and 'integrations/<name>-mcp' two
sentences later — <name> meant two different things; align both to <name>-mcp.
(2) skills/pw/SKILL.md 'What's Included' listed '2 MCP servers ... integrations' with no
caveat, unlike README's equivalent line — add '(optional — not auto-registered)'.

engineering-team/playwright-pro/CLAUDE.md

@@ -78,7 +78,7 @@ Leverage Claude Code's built-in capabilities:
 
 **Not auto-registered (issue #978).** The `pw-testrail` and `pw-browserstack`
 MCP servers are no longer declared in `.mcp.json`. They are launched with
-`npx tsx integrations/<name>/src/index.ts`, but the plugin ships no
+`npx tsx integrations/<name>-mcp/src/index.ts`, but the plugin ships no
 `node_modules` and nothing installs `@modelcontextprotocol/sdk`, so they failed
 to connect for **every** user (permanent red lines in `claude mcp list`),
 regardless of whether TestRail/BrowserStack was configured. Per this repo's

engineering-team/playwright-pro/skills/pw/SKILL.md

@@ -91,7 +91,7 @@ npx playwright test tests/auth/login.spec.ts --headed
 - **9 skills** with detailed step-by-step instructions
 - **3 specialized agents**: test-architect, test-debugger, migration-planner
 - **55 test templates**: auth, CRUD, checkout, search, forms, dashboard, settings, onboarding, notifications, API, accessibility
-- **2 MCP servers** (TypeScript): TestRail and BrowserStack integrations
+- **2 MCP servers** (TypeScript): TestRail and BrowserStack integrations *(optional — not auto-registered; see Integration Setup)*
 - **Smart hooks**: auto-validate test quality, auto-detect Playwright projects
 - **6 reference docs**: golden rules, locators, assertions, fixtures, pitfalls, flaky tests
 - **Migration guides**: Cypress and Selenium mapping tables