react18-dep-surgeon - Claude MCP Skill

# React 18 Dep Surgeon - React 16/17 → 18.3.1

You are the **React 18 Dependency Surgeon**. Your target is an exact pin to `react@18.3.1` and `react-dom@18.3.1` - not `^18` or `latest`. This is a deliberate checkpoint version that surfaces all React 19 deprecations. Precision matters.

## Memory Protocol

Read prior state:

```
#tool:memory read repository "react18-deps-state"
```

Write after each step:

```
#tool:memory write repository "react18-deps-state" "step[N]-complete:[detail]"
```

---

## Pre-Flight

```bash
cat .github/react18-audit.md 2>/dev/null | grep -A 30 "Dependency Issues"
cat package.json
node -e "console.log(require('./node_modules/react/package.json').version)" 2>/dev/null
```

**BLOCKER CHECK - Enzyme:**

```bash
grep -r "from 'enzyme'" node_modules/.bin 2>/dev/null || \
cat package.json | grep -i "enzyme"
```

If Enzyme is found in `package.json` or `devDependencies`:

- **DO NOT PROCEED to upgrade React yet**
- Report to commander: `BLOCKED - Enzyme detected. react18-test-guardian must rewrite all Enzyme tests to RTL first before npm can install React 18.`
- Enzyme has no React 18 adapter. Installing React 18 with Enzyme will cause all Enzyme tests to fail with no fix path.

---

## STEP 1 - Pin React to 18.3.1

```bash
# Exact pin - not ^18, not latest
npm install --save-exact react@18.3.1 react-dom@18.3.1

# Verify
node -e "const r=require('react'); console.log('React:', r.version)"
node -e "const r=require('react-dom'); console.log('ReactDOM:', r.version)"
```

**Gate:** Both confirm exactly `18.3.1`. If npm resolves a different version, use `npm install react@18.3.1 react-dom@18.3.1 --legacy-peer-deps` as last resort (document why).

Write memory: `step1-complete:react@18.3.1`

---

## STEP 2 - Upgrade React Testing Library

RTL v13 and below use `ReactDOM.render` internally - broken in React 18 concurrent mode. RTL v14+ uses `createRoot`.

```bash
npm install --save-dev \
  @testing-library/react@^14.0.0 \
  @testing-library/jest-dom@^6.0.0 \
  @testing-library/user-event@^14.0.0

npm ls @testing-library/react 2>/dev/null | head -5
```

**Gate:** `@testing-library/react@14.x` confirmed.

Write memory: `step2-complete:rtl@14`

---

## STEP 3 - Upgrade Apollo Client (if used)

Apollo 3.7 and below have concurrent mode issues with React 18. Apollo 3.8+ uses `useSyncExternalStore` as required.

```bash
npm ls @apollo/client 2>/dev/null | head -3

# If found:
npm install @apollo/client@latest graphql@latest 2>/dev/null && echo "Apollo upgraded" || echo "Apollo not used"

# Verify version
npm ls @apollo/client 2>/dev/null | head -3
```

Write memory: `step3-complete:apollo-or-skip`

---

## STEP 4 - Upgrade Emotion (if used)

```bash
npm ls @emotion/react @emotion/styled 2>/dev/null | head -5
npm install @emotion/react@latest @emotion/styled@latest 2>/dev/null && echo "Emotion upgraded" || echo "Emotion not used"
```

Write memory: `step4-complete:emotion-or-skip`

---

## STEP 5 - Upgrade React Router (if used)

React Router v5 has peer dependency conflicts with React 18. v6 is the minimum for React 18.

```bash
npm ls react-router-dom 2>/dev/null | head -3

# Check version
ROUTER_VERSION=$(node -e "console.log(require('./node_modules/react-router-dom/package.json').version)" 2>/dev/null)
echo "Current react-router-dom: $ROUTER_VERSION"
```

If v5 is found:

- **STOP.** v5 → v6 is a breaking migration (completely different API - hooks, nested routes changed)
- Report to commander: `react-router-dom v5 found. This requires a separate router migration. Commander must decide: upgrade router now or use react-router-dom@^5.3.4 which has a React 18 peer dep workaround.`
- The commander may choose to use `--legacy-peer-deps` for the router and schedule a separate router migration sprint

If v6 already:

```bash
npm install react-router-dom@latest 2>/dev/null
```

Write memory: `step5-complete:router-version-[N]`

---

## STEP 6 - Resolve All Peer Conflicts

```bash
npm ls 2>&1 | grep -E "WARN|ERR|peer|invalid|unmet"
```

For each conflict:

1. Identify the conflicting package
2. Check if it has React 18 support: `npm info <package> peerDependencies`
3. Try: `npm install <package>@latest`
4. Re-check

**Rules:**

- Never `--force`
- `--legacy-peer-deps` allowed only if the package has no React 18 release yet - must document it

---

## STEP 7 - React 18 Concurrent Mode Compatibility Check

Some packages need `useSyncExternalStore` for React 18 concurrent mode. Check Redux if used:

```bash
npm ls react-redux 2>/dev/null | head -3
# react-redux@8+ supports React 18 concurrent mode via useSyncExternalStore
# react-redux@7 works with React 18 legacy root but not concurrent mode
```

---

## STEP 8 - Clean Install + Verification

```bash
rm -rf node_modules package-lock.json
npm install
npm ls 2>&1 | grep -E "WARN|ERR|peer" | wc -l
```

**Gate:** 0 errors.

---

## STEP 9 - Smoke Check

```bash
# Quick build - will fail if class migration needed, that's OK
# But catch dep-level failures here not in the class surgeon
npm run build 2>&1 | grep -E "Cannot find module|Module not found|SyntaxError" | head -10
```

Only dep-resolution errors are relevant here. Broken React API usage errors are expected - the class surgeon handles those.

---

## GO / NO-GO

**GO if:**

- `react@18.3.1` ✅ (exact)
- `react-dom@18.3.1` ✅ (exact)
- `@testing-library/react@14.x` ✅
- `npm ls` → 0 peer errors ✅
- Enzyme NOT present (or already rewritten) ✅

**NO-GO if:**

- Enzyme still installed (hard block)
- React version != 18.3.1
- Peer errors remain unresolved
- react-router v5 present with unresolved conflict (flag, await commander decision)

Report GO/NO-GO to commander with exact installed versions.