NET-NOTES: modern .NET console milestone -- hands-free mission loop

The TeslaSuite console connected near-instantly over the new host
bridge, queued and ran a real 2-minute mission on the DOSBox pod, and
the mission exited on time. Wire-logged recycle: clean FIN/RST teardown
at mission end, console SYN-retrying 11s later, riding through dead-air
and connection-refused (pre-TCP_LISTEN) phases, reconnected 54s after
teardown with zero operator interaction. Modern console + net_loop.conf
pod = fully autonomous mission loop.

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

emulator/NET-NOTES.md

@@ -536,6 +536,21 @@ every send onto a second handle set to per-handle MODE_SENDTORX --
 frames then go out to the TAPs AND up to the host. Host
 connect/disconnect churns netnub (exit + ~60s relaunch) -- expected.
 
+## MODERN CONSOLE MILESTONE (2026-07-09 late): TeslaSuite .NET console runs the pod, fully hands-free
+
+With the host bridging recipe above, the modern .NET console connected
+"near instantly", queued and ran a real 2-minute BT mission on the
+DOSBox pod, and the mission exited ON TIME. Recycle test (wire-logged):
+mission-end teardown (netnub FINs then RSTs the session -- a clean
+close) -> console starts SYN-retrying 11s later -> rides through the
+dead-air phase AND a connection-refused phase (netnub's stack answers
+RST before BTL4OPT issues its TCP_LISTEN; the SBK upload sits in this
+window) -> SYN-ACK the moment the listener opens. **54 seconds from
+teardown to re-established session, zero operator interaction.**
+Modern console + net_loop.conf pod = a fully autonomous mission loop;
+the only operator action is queueing the next mission. (Console 4.10
+by contrast needs an app relaunch per mission.)
+
 ## Open questions / notes
 - Exact TCP listen port(s) — not in the source grep; get from NETNUB.EXE
   or a capture at milestone 3.