Networking: note console VM standup (SheepShaver/OS9.0.4) + TAP bridge plan

Records that Router mode is NAT (won't reach the pod) and the console<->pod
link needs bridged TAP on both ends: console TCP/IP manual 200.0.0.1, pod
DOSBox-X switched from slirp to pcap on the same segment.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

emulator/NET-NOTES.md

@@ -278,6 +278,20 @@ Everything needed to PARSE a capture and BUILD a stand-in egg-sender is
 here except those two bytes-on-the-wire details, which the console-connect
 milestone resolves immediately.
 
+## Console VM standup (user, 2026-07-04): SheepShaver + OS 9.0.4 + old-world ROM
+
+Valid combo (old-world ROMs support the full 7.5.2–9.0.4 range); OS 9's
+Open Transport provides the MacTCP-API compat the app's Gestalt check
+wants, so Console 4.10 runs. Networking initially set to "Basilisk II
+Router" — NOTE that's **NAT** (assigns a 10.x IP, routes to host), fine
+for building/updating the VM but it CANNOT reach the pod at 200.0.0.113.
+For the console↔pod link both must be **bridged (TAP)** on one L2 segment:
+console SheepShaver TCP/IP = manual 200.0.0.1 / 255.255.255.0 on a TAP;
+pod DOSBox-X moves off `backend=slirp` to **`backend=pcap`** bound to the
+same TAP/bridge (200.0.0.113 already via WATTCP). Then the console's
+outbound TCP to 200.0.0.113:1501 reaches the pod and we capture the egg
+exchange (resolves the framing + endianness caveats above).
+
 ## Open questions / notes
 - Exact TCP listen port(s) — not in the source grep; get from NETNUB.EXE
   or a capture at milestone 3.