feat: F4.6g2 the DNS server window, its records being /dns/hosts

Oracle DnsWindowRun uses Java's DNS server window as a person does and
asks a computer's resolver after each step. The core's DNS server is a
program its window changes: on and off (its socket on port 53),
recursive resolution, and records that are /dns/hosts, read on every
query as Java's server reads them (the reader moves from fls to the
core). The snapshot carries every installed DNS server with whether it
runs. The room takes the window's actions, sends its view and writes
the server back after the run; the editor shows Java's window with its
three tabs. Not taken from Java: a cell edit spilling into records of
another type, an add losing what another program wrote into the file,
an empty mail domain, a removal hitting the first record of the name.
A table cell no longer takes the room's value over what is being typed
(the web server's too).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

packages/protocol/src/dns.ts

@@ -0,0 +1,14 @@
+// What the DNS server's window shows, as the room keeps it and every client
+// shows it (plan §7.3), after GUIApplicationDNSServerWindow (measured with
+// tools/java-oracle's DnsWindowRun): its button, the box for recursive
+// resolution, and the rows of its three tables — name and address (A), mail
+// domain and mail server (MX), domain and name server (NS) — as /dns/hosts
+// holds them.
+
+export type DnsTable = 'A' | 'MX' | 'NS';
+
+export interface DnsServerView {
+  readonly active: boolean;
+  readonly recursive: boolean;
+  readonly rows: Readonly<Record<DnsTable, readonly (readonly [string, string])[]>>;
+}