test: verify Playwright MCP server functionality after #770 merge

## Overview
Test and verify the vendored Playwright MCP server works correctly after PR #770 is merged.

## Test Plan

### 1. Installation Test
```bash
cd ~/ppv/pillars/dotfiles/mcp
./setup-playwright-mcp.sh
```
- [ ] Verify npm install completes successfully
- [ ] Verify no errors during setup
- [ ] Check that `mcp/servers/playwright-mcp/node_modules` exists

### 2. Server Startup Test
```bash
cd ~/ppv/pillars/dotfiles/mcp
./playwright-mcp-wrapper.sh
```
- [ ] Server starts without errors
- [ ] Ctrl+C cleanly shuts down

### 3. MCP Integration Test
- [ ] Verify playwright appears in `mcp/mcp.json`
- [ ] Test with Claude Code or other MCP client
- [ ] Verify tools are available through MCP protocol

### 4. Basic Functionality Test
Using an MCP client, test:
- [ ] Browser launch (headless mode)
- [ ] Page navigation
- [ ] Screenshot capture
- [ ] Basic page interaction

### 5. Error Handling Test
- [ ] Test server behavior when Playwright is not installed
- [ ] Test with missing dependencies
- [ ] Verify error messages are helpful

## Acceptance Criteria
- [ ] Server installs and starts successfully
- [ ] MCP clients can connect to the server
- [ ] Basic browser automation works through MCP
- [ ] Errors are handled gracefully with clear messages

## Notes
- This is a follow-up to #766 and PR #770
- Testing in feature branch is complex due to worktree setup
- Full testing should happen after merge to main

Start with mcp/setup-playwright-mcp.sh and mcp/playwright-mcp-wrapper.sh, then inspect mcp/mcp.json. Run the installation and startup commands from the issue, followed by the listed MCP client and browser checks. Done means installation, startup, client connectivity, basic automation, and graceful error handling all meet the acceptance criteria.

Written by the indexing model from the issue text.