# Verifier — Key Link Wiring Patterns (Step 5)

Key links are critical connections. If broken, the goal fails even with all artifacts present.

Use rcode-tools for key link verification against must_haves in PLAN frontmatter:

```bash
LINKS_RESULT=$(node ".rcode/bin/rcode-tools.cjs" verify key-links "$PLAN_PATH")
```

Parse JSON result: `{ all_verified, verified, total, links: [{from, to, via, verified, detail}] }`

For each link:
- `verified=true` → WIRED
- `verified=false` with "not found" in detail → NOT_WIRED
- `verified=false` with "Pattern not found" → PARTIAL

## Fallback Patterns

Use these if `must_haves.key_links` not defined in PLAN.

### Pattern: Component → API

```bash
grep -E "fetch\(['\"].*$api_path|axios\.(get|post).*$api_path" "$component" 2>/dev/null
grep -A 5 "fetch\|axios" "$component" | grep -E "await|\.then|setData|setState" 2>/dev/null
```

Status: WIRED (call + response handling) | PARTIAL (call, no response use) | NOT_WIRED (no call)

### Pattern: API → Database

```bash
grep -E "prisma\.$model|db\.$model|$model\.(find|create|update|delete)" "$route" 2>/dev/null
grep -E "return.*json.*\w+|res\.json\(\w+" "$route" 2>/dev/null
```

Status: WIRED (query + result returned) | PARTIAL (query, static return) | NOT_WIRED (no query)

### Pattern: Form → Handler

```bash
grep -E "onSubmit=\{|handleSubmit" "$component" 2>/dev/null
grep -A 10 "onSubmit.*=" "$component" | grep -E "fetch|axios|mutate|dispatch" 2>/dev/null
```

Status: WIRED (handler + API call) | STUB (only logs/preventDefault) | NOT_WIRED (no handler)

### Pattern: State → Render

```bash
grep -E "useState.*$state_var|\[$state_var," "$component" 2>/dev/null
grep -E "\{.*$state_var.*\}|\{$state_var\." "$component" 2>/dev/null
```

Status: WIRED (state displayed) | NOT_WIRED (state exists, not rendered)
