Pinned real Antigravity 1.3.0 Linux x64 startup proof
SHA256: 9fb60956af0a9d76220a4db91ca9ac88e2a2372ad68f985ab5fceace6b825b96

IPv6 enabled: initialized successfully, exit0, agentInfo.version1.3.0.
IPv6 disabled only within an isolated user/network namespace: SIGABRT (-6).
F1019 02:37:13.238198  126193 enforce_kernel_ipv6_support.cc:73] Check failed: loopback6_ok || !loopback4_ok This machine (fs-19) does not have an IPv6 loopback (::1) interface.  This configuration is obsolete.  You may temporarily set --enforce_kernel_ipv6_support=false to bypass this check, but code elsewhere in google3 may fail as result.  See http://go/ip-agnostic/topics/localhost for details.

Same real runtime through T3 installation validation, with fixture archive staging and a prior release:
main 1
{
  "phase": "failed",
  "message": "The downloaded Antigravity runtime could not start in this environment."
}
head 0
{
  "phase": "failed",
  "message": "Antigravity requires IPv6 socket support. Enable IPv6 in this environment. On WSL, remove ipv6.disable=1 from .wslconfig and run wsl --shutdown."
}

Before assertion fails because only the generic message is returned. Head assertion passes and verifies the previous release remains active after staging cleanup. All temporary source/test instrumentation was restored byte-for-byte.

Final uninstrumented diagnostic regressions:
note: You are running `vp test` as a Vite+ built-in command. If you meant to run the test npm script, use `vpr test` instead.

 RUN  v5.0.1 /home/ubuntu/wt/other-providers-07


 Test Files  1 passed (1)
      Tests  2 passed | 42 skipped (44)
   Start at  02:44:36
   Duration  3.27s (transform 60%, import 28%, tests 9%, setup 3%)