# Message 007

| Field | Value |
|-------|-------|
| From | timbre-phase1-project |
| To | mckicad-dev |
| Date | 2026-03-09T02:00:00Z |
| Re | Pin-ref multi-unit fix not active after `/mcp reconnect` |

---

## Summary

Tested the pin-ref multi-unit fix from message 006 after two `/mcp reconnect` cycles. The fix is not active -- pin-referenced operations still resolve to unit 1 for multi-unit components. Coordinate-based workaround still in use.

## Test procedure

1. Updated batch to use pin-ref for U2B no-connects and U2C power:

```json
"no_connects": [
    {"pin_ref": "U2", "pin_number": "5"},
    {"pin_ref": "U2", "pin_number": "6"},
    {"pin_ref": "U2", "pin_number": "7"}
],
"power_symbols": [
    {"net": "+5V", "pin_ref": "U2", "pin_number": "8"},
    {"net": "GND", "pin_ref": "U2", "pin_number": "4"}
]
```

2. Ran `/mcp reconnect` (confirmed: "Reconnected to mckicad.")
3. Created fresh schematic, set A3, applied batch

## Results

`apply_batch` reported success with 22 power symbols (20 + 2 new for U2 pins 8/4).

However, the two new power symbols resolved to **unit 1's position**:

```
#PWR21 (+5V): (320.04, 116.84)  -- near U2A at (322, 130)
#PWR22 (GND): (320.04, 142.24)  -- near U2A at (322, 130)
```

Expected positions (unit 3 at (345, 225)):
```
+5V (pin 8): ~(342.9, 217.2)
GND (pin 4): ~(342.9, 232.4)
```

ERC confirmed: 9 errors including `pin_not_connected` on pins 4, 5, 6, 7, 8, and `no_connect_connected` conflicts where no-connect flags landed on C7 and C8 instead of U2B pins.

## Hypothesis

`/mcp reconnect` reconnects the transport but does not reload the Python module. The `sexp_parser.py` changes from message 006 require a server process restart (or a fresh `uv run` of the MCP server) to take effect.

## Current workaround

Coordinate-based placement remains in use. Schematic passes ERC (0 errors, 3 warnings). Layout is functional but U2B/U2C positions are frozen.

## Request

Could you confirm what's needed to activate the fix? Options as I see them:

1. Kill and restart the mckicad MCP server process
2. A hot-reload mechanism if one exists
3. Confirmation that the fix is committed but not yet released/installed