feat(core): ARP after Java, measured with Java FILIUS

An ARP lookup asks, waits a round trip, asks once more and gives up after
another round trip; then host unreachable, observed at the sender itself or
sent back by the router (for ICMP only for an echo request). A waiting
sender wakes after what else happens at that time. A ping then waits a
round trip for its answer, counted from when it left. Swift asks twice at
once while events run and lets the packet wait without end when the
address exists anywhere in the network; the option swiftArp keeps that for
the Swift comparison, and three scenarios are compared with Swift until the
trace where ARP fails or a ping goes unanswered.

arpJava.test.ts compares ArpRun: both pings match; the two UDP stories wait
for Java's transport thread (next step). DNS without a server now matches
Java too.

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

packages/core/test/dnsJava.test.ts

@@ -53,17 +53,8 @@ function normalized(frames: readonly SeenFrame[]): SeenFrame[] {
   }));
 }
 
-/**
- * Stories the engine does not play like Java yet, with the reason; each must
- * still differ from Java (else it belongs to the others) and return the same.
- *
- * noServer: Java's transport thread sends while the resolver already waits,
- * and asks ARP twice, a round trip apart. The engine's ARP (Swift's) blocks
- * the call and asks again at once — rebuilt after Java in its own step.
- */
-const NOT_YET_LIKE_JAVA: Record<string, string> = {
-  noServer: "ARP: Java's second request comes a round trip after the first, while the resolver waits",
-};
+/** Stories the engine does not play like Java yet, with the reason; each must still differ from Java. */
+const NOT_YET_LIKE_JAVA: Record<string, string> = {};
 
 describe('DNS as Java FILIUS runs it', () => {
   const scenario = JSON.parse(readFileSync(join(scenarioDirectory, 'dns-lan.scenario.json'), 'utf8')) as Scenario;