Hew on SlOS — native DNS and bounded socket failures Verified 25 October 2026. Selected real-QEMU O2 output, not a live endpoint. Compiler: Hew 95340fc71a, matching standard library OS/SDK addition: e954004 on baseline 04fcefa Consumer addition: 70e08fb on baseline 2602e68 Kernel SHA256: 9063d0508d924572115380498a0c7668d549bbf6819f0e6d994eb8a09bd8e296 O2 DNS session: 0ca31564064044c9a7d75d954fed7348 O2 socket session: cfa33b938a99410888d9965e1e4676b9 Companion O0 sessions: f5c9ad48a15b492dabd45b7eb40a0150, d91088291851440c954d48291bcac235 Evidence: build/io{,-o2}/{dns,network}-sessions/SESSION/ dns.log, dns-host.log; resilience.log, host.log Final focused checks passed after commits with clean runtime/SDK source provenance. HOST — original O2 resilience host.log: accepted idle client: guest timed out and closed in 0.198s slow reader: all 2097152 patterned bytes after pause non-reader: guest advanced after partial write deadline reset peer: sent TCP RST GUEST — selected original O2 resilience.log output: Hew accepted idle read bounded: PASS Hew slow reader all bytes: PASS Hew write timeout committed=229376: PASS Hew reset classified closed: PASS Hew real network resilience: PASS status: PASS expected=0 actual=0 GUEST — selected original O2 dns.log output: Hew DNS hostname and bounded failures: PASS status: PASS expected=0 actual=0 GUEST — subsequent consuming-vector follow-up, consumer 5e7c10c: O0 DNS session: ab5026d92b094cf3a00173ec857570b9 O2 DNS session: 8650973fb4544746b1257584178a368e Both sessions contain the following original output: Hew consuming DNS vector iteration: PASS Hew DNS hostname and bounded failures: PASS status: PASS expected=0 actual=0 Scope and limits: Real host TCP sockets; 150-ms explicitly configured read/write deadlines. Observed close time is this fixture's measurement, not a latency guarantee. Committed bytes means accepted into OS buffers, not delivered or acknowledged. Reset is Closed. Receive timeout/reset faults the calling actor; isolate that operation in a checked/supervised actor to contain it. Native IPv4 DNS uses the existing resolver and localhost UDP fixture over QEMU Ethernet: A/CNAME, hostname echo, NXDOMAIN, malformed/wrong-question replies, and silent server failure; not an external Internet DNS test. One native query has a three-second maximum and occupies the cooperative Hew worker while yielding the OS task. Timed wrappers cannot preempt that call. Connect's socket deadline starts after resolution. No default read/write deadline. Existing jobs/service apps do not opt in. No IPv6, DNSSEC, DNS TCP fallback, or full std.net.http claim.